FruxonDocs
Agent NetworkParticipants

Patches the consult-roster metadata on one participant↔agent binding.

PATCH semantics: null fields are left unchanged; a supplied list replaces the stored one. `default_for_roles` must be a subset of `roles`. The `binding` route segment is the agent id (consistent with the bind sub-resource). 404 if the binding doesn't exist.

PATCH
/v1/tenants/{tenant}/participants/{participant}/bindings/{binding}/roster

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

participant*string

The participant identifier.

Formatuuid
binding*string

The agent identifier whose binding to patch.

tenant*string

The tenant identifier

Request Body

The roster patch.

roles?|null

Replacement expertise tags, e.g. ["ux", "on-call"]. Null leaves them unchanged.

consultAllowed?boolean|null

Whether the agent may consult this participant. Null leaves it unchanged.

maxUrgency?string

Topic priority. Inherited from Proposal.Urgency at activation; the dialogue agent may re-rate (e.g. it discovers the issue is worse than triaged).

Value in"UNSPECIFIED" | "LOW" | "NORMAL" | "HIGH" | "EMERGENCY"
defaultForRoles?|null

Roles for which this participant is the preferred pick. Null leaves them unchanged.

responsePolicy?string

When the agent referenced by a layered participant edge should run in response to an inbound message from its participant. Decided at the receiver level (§14) — the edge is the per-member policy knob, so the same noisy group can host two agents with different response disciplines.

Value in"UNSPECIFIED" | "ALWAYS" | "WHEN_ADDRESSED" | "RELEVANCE" | "MUTED"
venueBrief?string|null

A1b §4.4 — an optional, length-capped venue brief for a member-group edge (e.g. "react only to delivery incidents"). The §14 relevance gate appends it to its judgment strategy as a constrained scope note; it is Layer-2-native (persists on Fruxon.Model.AgentNetwork.NetworkMemberParticipantRelation.VenueBrief). PATCH semantics: null leaves the existing brief unchanged; a non-null value sets it, and an empty/whitespace value clears it. Capped at Fruxon.Model.AgentNetwork.NetworkMemberParticipantRelation.VenueBriefMaxLength characters so it can never grow into a full system prompt.

Length0 <= length <= 280
[key: string]?never

Response Body

curl -X PATCH "https://api.fruxon.com/v1/tenants/string/participants/497f6eca-6276-4993-bfeb-53cbbbba6f08/bindings/string/roster" \  -H "Content-Type: application/json" \  -d '{}'
{
  "participantId": "00000000-0000-0000-0000-000000000000",
  "agentId": "string",
  "displayName": "string",
  "kind": "PERSON",
  "roles": [
    "string"
  ],
  "consultAllowed": false,
  "maxUrgency": "LOW",
  "defaultForRoles": [
    "string"
  ],
  "responsePolicy": "ALWAYS",
  "venueBrief": "string"
}
{
  "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
}

Adds (or returns the existing) binding between the participant and an agent.

Binds the participant to an agent so the agent can address it. The call is idempotent: if the binding already exists it is returned unchanged rather than duplicated. Returns 404 when the participant does not exist.

Lists an agent's consult roster — its bound participants with consult metadata.

Returns one row per participant bound to agentId, each carrying the consult-roster fields (roles, consult-allowed, urgency cap, default-for-roles) that drive `consult_for_role` resolution and the consult policy gate (design §12). The Consult Network UI renders + edits this list.