Agent API
V2 and above. Part of the invite-only hosted editions, not the free self-hosted V1. See the editions.
What it lets you do
Everything else in AI Partner is about you asking it for work. This is the other direction: other agents and applications asking yours.
Turn it on and your deployment becomes a service someone else can call. Their agent hands over a goal — "research the top 3 CRM tools and write a comparison" — and gets the finished result back, produced with your full capability set: the web, your documents, file generation, everything.
It speaks the A2A standard, so any A2A-compatible agent can find and use yours without anything bespoke being written on either side.
Every customer is sealed off from every other
Each consumer you create is a separate account in its own right, not a shared key on your own account:
| Isolated per consumer | Meaning |
|---|---|
| Workspace | Their files never mix with yours or another consumer's |
| Knowledge | They can't reach your documents, and you can't see theirs |
| Work in flight | One consumer can never see, read or cancel another's tasks |
| Usage and cost | Metered individually, so you always know who consumed what |
| Concurrency | Each gets its own cap — one heavy customer can't starve the rest |
Turning it on
As an administrator of the instance:
- 1Switch on Inbound Agent API
Until you do, every incoming call is refused and says so. Off is the default.
- 2Create a consumer
New Consumer sets up the isolated account and mints its access key.
The key is shown exactly once. Give it to that customer then; you can rotate or revoke it at any time, but you can't look it up again.
- 3Hand over the connection details
Your instance publishes what a calling agent needs to discover and connect to it. Send the customer their key and your instance's address — a competent A2A client needs nothing more.
Watching and billing it
Agent Access shows each consumer's current usage and cost as it accrues.
Statement exports a month's activity for a consumer as a CSV — goals run, calls made, tokens used, cost, broken down by model. That's the artefact you attach to an invoice.
Metering is per consumer and continuous, so a customer whose usage triples shows up as it happens rather than at the end of the month.
Withdrawing access
| To do this | Do this |
|---|---|
| Cut off one customer | Revoke their key |
| Replace a leaked key | Rotate it — the old one stops working immediately |
| Stop accepting all external work | Switch Inbound Agent API off |