Skip to Content
InvyteDocs

Set how an agent acts

Set how one of Invyte's working agents acts where their role reaches: per effect (write, outside, destructive) off, suggest (drafts only), ask (waits for a person's approval) or auto (commits and reports). The most specific place wins: Job, then Client, then organization. A mode never grants anything the role does not; destructive effects never go past ask. Admins only.

POST
/operations/access.setAgentModes

Authorization

bearer
headerAuthorizationBearer <API key or OAuth token>

An organization API key (ink_live_…, ADR-0124), or the OAuth access token a person's AI client gets from the Recruiter MCP sign-in. Only the Authorization header is accepted.

Header Parameters

Idempotency-Key?string

Makes a write safe to repeat: the same key and input return the first result. Required for agents' writes and for anything a person confirms.

Match^[A-Za-z0-9._:-]+$
Length8 <= length <= 128

Request Body

application/json
  1. body
input*
confirmation?string

The id from a confirm or awaiting_approval Outcome, sent with the same input and key to go ahead.

Response Body

Done. A replay of the same key and input omits output.

application/json
  1. response
status*unknown
output?
replay?
actionId*string
Example Request
curl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/access.setAgentModes' \  -H 'Content-Type: application/json' \  -d '{  "input": {    "agt": "pipeline",    "scope": "organization",    "modes": {}  }}'
Example Response
{  "status": "done",  "output": {    "assignmentId": "string",    "agt": "pipeline",    "modes": {      "write": "off",      "outside": "off",      "destructive": "off"    }  },  "replay": {    "assignmentId": "string"  },  "actionId": "string"}