Lists the agent's declared slots with their binding state.
Joins the slot declarations on the agent's current revision with the tenant-level `SlotParticipantBinding` rows. Slots without a binding render as `bound=false` (web-UI-only fallback). Stale bindings whose slot name no longer appears on the current revision are surfaced with `orphaned=true` rather than hidden, so the operator can prune them.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The agent identifier.
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/agents/string/slots"[
{
"name": "string",
"displayName": "string",
"description": "string",
"requiredKind": "ANY",
"bindingType": "PARTICIPANT",
"participantId": "00000000-0000-0000-0000-000000000000",
"participantDisplayName": "string",
"role": "string",
"bound": false,
"orphaned": false
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Lists the available source doors.
Each door supplies the integration-shaped half of a work shape — which list tool, where the item id and watermark live, how the bound is rendered — leaving the builder the one question that is genuinely theirs: which mail, which rows, which tickets.
Binds a participant to a declared slot
The participant shorthand for the binding endpoint above — equivalent to a body of `{ "bindingType": "PARTICIPANT", "participantId": … }`. Validates that the slot is declared on the agent's current revision and that the participant kind matches the slot's `RequiredKind`. Re-binding the same slot replaces the participant in place — the binding id is preserved across replacements so any downstream audit references stay correlatable.