Operations
One registry behind the app, the API, MCP and Autopilot: list what you may call, then invoke it.
Every action in Invyte is an operation with a name like jobs.list or pipeline.setDisposition. The app, the
Recruiter MCP, the API and Autopilot all call the same operations, so they always agree on what is allowed and what
happens.
Two calls
| Call | What it does |
|---|---|
GET /operations | Lists every operation the caller may call now, with JSON Schemas for input and output. |
POST /operations/{name} | Runs one operation. The body is { "input": … }. |
The base URL is https://www.invyte.ai/api/recruiter/v1. Request bodies are JSON, at most 1 MB.
Every operation declares its effect
| Effect | Meaning |
|---|---|
| Read | Changes nothing. |
| Write | Changes Invyte data only. |
| Reaches people | Sends an email, a share or a message to someone. |
| Can't be undone | Permanent, such as archiving a Job. |
Operations that reach people or can't be undone ask for a confirmation when a person is calling. Some operations are paid: each call can spend vendor credit. See Paid operations.
What you can call depends on who you are
The listing is filtered by your role in the organization, or the key's role. If an operation is missing from
GET /operations, the caller isn't allowed to run it. See Roles and access.
The same names everywhere
An MCP tool is the operation's name with the dot replaced: pipeline.setDisposition is the tool
pipeline_setDisposition. Every reference page shows both.