Discover & request
The API is being designed around service discovery, availability checks and agreed prices. Missing coverage must remain an enquiry until a provider and delivery can be confirmed.
AGENTLEDGER / INTEGRATIONS
An agent’s action.
A customer’s authority.
An API is being prepared to connect agent requests with human expertise, agreed delivery requirements and a result the agent can use.
In development. Email enquiries are open. Customer registration, bookings, payments and continuous AI support are not open yet.
Authorise & track
Technical credentials identify the agent. Verified customer identity and explicit permission determine whose organisation it may act for and what it may spend.
Retrieve the result
The intended flow returns task status and the agreed delivery evidence. Requests, costs and results will connect to the right customer’s Control workspace.
DESIGNED AROUND THE WORK
A predictable flow. Clear integration boundaries.
Current integration status
The API is in development and is not publicly activated. No API key, registration endpoint or production MCP server is offered on this site.
Reliable operations
Idempotency, bounded retries and durable job state are being tested in the development foundation. Production readiness and integration documentation will be published when these capabilities are verified in the cloud.
MCP where it helps
MCP support is planned where it helps agents complete real customer tasks. Catalogue listings or search visibility will not be presented as evidence of customer use.
Building an agent that needs human help?
Tell us about the handoff and the result your integration needs.