The Agentry API

Verify your business. Record the agents that act for it.

Agentry's Trust API verifies a UK limited company, registers it, and issues a portable, signed record of what was verified. It moves no money.

It is in sandbox ahead of launch, and every key it issues is a sandbox key. Mandate holds no FCA permissions and claims none.

Read the documentation

tools/list 14 tools
  1. register_business
  2. check_company
  3. get_my_verification_status
  4. delete_my_business
  5. register_agent
  6. request_agent_binding
  7. resend_agent_binding_confirmation
  8. list_my_agents
  9. revoke_agent_binding
  10. request_agent_identity_challenge
  11. confirm_agent_identity_link
  12. revoke_agent_identity_link
  13. list_agent_activity
  14. get_my_audit_pack

A Trust API key lists exactly these 14 tools and can call nothing else. No tool on it initiates, holds, receives or settles a payment.

How it works

Five things, in the order a business meets them

  1. Register

    A business registers with its Companies House number and a contact email.

  2. Check

    Agentry checks the company against the Companies House register, and the person controlling the account completes an identity check, which no tool can complete.

  3. Take a proof

    When both checks hold, the business reads its own status and takes away a signed proof. Today that is a sandbox proof: it says so, and it is not evidence for anyone to rely on.

  4. Record and connect agents

    The business records its agents, a person there confirms by email what each may do and until when, and each connects with its own credential.

  5. Keep the record

    Each confirmed agent gets its own credential, and what Agentry records about it is the business's own to export as an audit pack.

Standard MCP, nothing bespoke

The transport is MCP over HTTP. Any MCP client that lets you set an API key can discover and call the tools.

{
  "jsonrpc": "2.0",
  "id": 5,
  "method": "tools/call",
  "params": { "name": "get_my_verification_status", "arguments": {} }
}

{
  "business_id": "0b8f7d2c-4a19-4d64-9a3e-5b1c7e02f8aa",
  "status": "verified",
  "standard": "trust_v1",
  "checks": [
    { "name": "company_register", "source": "sandbox_fixture", "last_performed_at": "2026-09-07T09:22:41.006Z" },
    { "name": "account_controller_identity", "source": "sandbox_fixture", "last_performed_at": "2026-09-07T09:31:18.442Z" }
  ],
  "proof": "eyJhbGciOiJFUzI1NiIsImtpZCI6...",
  "proof_expires_at": "2026-09-14T09:33:02.771Z",
  "proof_environment": "sandbox"
}
Status reads are self-only: a key sees its own business and no other.

A signed record that travels without us

A proof is a compact JWS signed with ES256, checked offline against Agentry's published key set: no account, no key and, once the key set is pinned, no call to us. Every proof issued today is a sandbox proof and says so.

Written for a stranger, so it says what is true

Read the documentation

It is provided to design partners.