Skip to Content
InvyteDocs
Autopilot & approvals

An agent's success measures

How well one working agent did since a date, on the Jobs you can see: its actions joined to the replies, consents, applications, shortlistings, meetings and hires that followed them within each attribution window, as its success measure (sourcing: consent rate and UMatch; communication: reply, consent and unsubscribe rates; pipeline: completion rate and days; delivery: shortlist acceptance; orchestrator: days to shortlist and cost per shortlisted candidate; intake: time to open and requirements loosened later; workflow: designs delivered and drafts per design), with the trend against the window before.

POST
/operations/outcomes.measures

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?
actionId*string
Example Request
curl -X POST 'https://www.invyte.ai/api/recruiter/v1/operations/outcomes.measures' \  -H 'Content-Type: application/json' \  -d '{  "input": {    "agentId": "pipeline",    "since": "2019-08-24T14:15:22Z"  }}'
Example Response
{  "status": "done",  "output": {    "agentId": "pipeline",    "since": "2019-08-24T14:15:22Z",    "until": "2019-08-24T14:15:22Z",    "measures": [      {        "key": "string",        "label": "string",        "value": 0,        "unit": "rate",        "n": 0,        "trend": 0      }    ],    "followed": {      "actions": 0,      "reply": 0,      "consent": 0,      "apply": 0,      "shortlist": 0,      "meeting": 0,      "hire": 0    }  },  "actionId": "string"}

Plan a Job's Mandate POST

Record a new revision of the Job's plan: a target (shortlisted candidates and a date), the strategy a review chose, or a requirement change with its cause and what was rerun. Changes nothing a candidate or client sees.

Who owns these candidates POST

Which working agent owns each person on a Job now (sourcing, communication, pipeline or delivery), worked out from where they stand, with any override a person or the orchestrator set, and whether a person holds them (ownedBy kind person: leave them alone). Ids and states only.