Agent access overview
Agent access lets an AI agent or a script read your VendOrca program data with a token you issue for yourself. Connect Claude or any MCP client, or call the REST API directly.
On this page
What agent access is
You issue a personal access token in the app, then give it to an agent. The agent can ask for workers, assignments, timesheets, expenses, invoices, suppliers, approval statuses, program configuration and report queries. It gets back records you can see, with personal fields only when the token has the Personal data scope.
- Tokens only read. No token can create, change, approve or pay anything.
- A token acts as you. It reaches what your own account reaches in the app, within your role's visibility. If your role changes, the token follows on its next request.
- You choose its scopes when you issue it: program data, workforce data, financial data and, only if you select it, personal data. See Tokens and scopes.
- VendOrca records calls against your name.
There is one set of operations with two ways in. Each operation is an MCP tool and a REST endpoint with the same name and the same result.
Plans and who can use it
| Question | Answer |
|---|---|
| Which plans include it? | Team and Business. The Growth plan does not include agent access. See pricing. |
| Who turns it on? | A Program Admin, once for the whole workspace, after reading what it exposes. |
| Who can issue a token? | Any user in the workspace, once agent access is on. You can only issue tokens for yourself. A Worker or Billing Entity sign-in must first be linked to its record, which your Program Admin arranges. |
| Who can revoke a token? | The person who issued it. Nobody, admins included, can see or revoke someone else's tokens. |
Staff roles such as Program Admin, Hiring Manager, Finance / AP, HR / Compliance and Executive read across the workspace, as they do in the app. A worker's token sees only that worker's own records. A Billing Entity token sees only that supplier's own records. Report queries, approval statuses and program configuration are for staff roles only.
Two ways to connect
MCP
The remote MCP server lives at:
https://app.vendorca.com/api/v1/mcpIt uses streamable HTTP. It is stateless and answers each POST with a single JSON response. It offers tools only. tools/list shows only the tools your token can call right now. Authenticate with an Authorization: Bearer <token> header.
REST
Every REST endpoint lives under:
https://app.vendorca.com/api/v1/For example, GET https://app.vendorca.com/api/v1/workers lists workers. The API reference covers the envelope, errors and every endpoint.
Discovery documents
Two machine-readable documents describe the API. Neither needs a token.
| Document | URL | Contents |
|---|---|---|
| OpenAPI 3.1 | https://app.vendorca.com/api/v1/openapi.json | Every REST operation, its arguments and the bearer security scheme. |
| llms.txt | https://app.vendorca.com/llms.txt | A plain-text summary for agents: authentication, both transports, Claude Code and Claude Desktop setup, and the list of operations. |