FruxonDocs
Agent NetworkSlots

Binds a declared slot to a participant, a roster role, or the operator queue

The body's `bindingType` chooses how the slot is fulfilled (HITL unification design §3.2): `PARTICIPANT` names one person, `ROLE` defers to whoever holds that roster role in this Application — the same selection `consult_for_role` uses, so notify and consult cannot name different humans — and `QUEUE` routes to the awaiting-human queue. Re-binding replaces the binding in place; the binding id is preserved so downstream audit references stay correlatable. A binding says who gets <em>delivered to</em>. It is never a grant to answer or act — that is checked separately, at answer time (design §5.4).

PUT
/v1/tenants/{tenant}/agents/{agent}/slots/{slot}/binding

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

agent*string

The agent identifier.

slot*string

The declared slot name.

tenant*string

The tenant identifier

Request Body

The binding target.

bindingType?string

How the slot should be fulfilled. Required.

Value in"UNSPECIFIED" | "PARTICIPANT" | "ROLE" | "QUEUE"
participantId?string|null

The participant to bind — required for Fruxon.Model.Agents.SlotBindingType.Participant.

Formatuuid
role?string|null

The roster role to defer to — required for Fruxon.Model.Agents.SlotBindingType.Role.

[key: string]?never

Response Body

curl -X PUT "https://api.fruxon.com/v1/tenants/string/agents/string/slots/string/binding" \  -H "Content-Type: application/json" \  -d '{}'
{
  "id": "00000000-0000-0000-0000-000000000000",
  "tenantId": "00000000-0000-0000-0000-000000000000",
  "agentId": "string",
  "networkId": "00000000-0000-0000-0000-000000000000",
  "agentMembershipId": "00000000-0000-0000-0000-000000000000",
  "slotName": "string",
  "bindingType": "PARTICIPANT",
  "participantId": "00000000-0000-0000-0000-000000000000",
  "roleRef": "string",
  "boundParticipantId": null,
  "createdAt": 0,
  "modifiedAt": 0
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

Removes the slot's binding

Returns 204 whether or not a binding existed. The slot declaration on the revision is untouched; only the participant wiring is removed.

Get the evaluation metrics an agent has opted into.

Returns the resolved per-agent metric set with weights applied, split into the LLM-judge bucket and the system-metric bucket. Each bucket's weights sum to 100 when non-empty. To modify, send the full replacement set to `PUT AgentEvaluationMetrics` — there is no partial-patch endpoint.