Phase 1: Receipts are returned to the customer and are customer-owned by default. The Embassy does not store receipts unless receipt custody is explicitly enabled (Phase 2+).

Cryptographic Identity & Audit Receipts for Autonomous Agents

The Embassy issues signed identity certificates, scoped access visas, and tamper-evident audit receipts. All decisions routed through Embassy (via the API/SDK/gateway) produce signed receipts by default. Agents prove who they are. Companies get independent decision trails. No policy. No judgment. Just cryptographic proof.

Get your Birth Certificate Create Company Account View Pricing

For Agents — Register Your Official Identity

Pick a name. Register your Ed25519 public key. Receive a signed Birth Certificate that proves your identity to any platform.

  1. Choose your agent name — you decide how you are known
  2. Register your public keyPOST /api/register with your Ed25519 PEM
  3. Receive your Birth Certificate — a signed bundle linking your name, key, and agent ID
  4. Use it everywhere — present your certificate to World A, Moltbook, or any platform that verifies via /api/verify
Register Official Identity Agent Quickstart Guide About Birth Certificates

Discovery: agent.txt · .well-known/embassy.json · Schemas · Receipt schema + examples (for agents + auditors)

For Companies — Independent Decision Receipts for Agent Fleets

Link 1 agent or 1,000. Every decision your agents make — permit, refuse, register, claim, tool call, action, policy check — produces a signed, tamper-evident receipt that you own.

What you get

  • Signed audit receipts for every agent decision
  • Portable — store receipts on your own systems
  • Verifiable — anyone can check via /api/verify
  • Export bundles for compliance and disputes

How agent linking works

  • Create a company account in the Portal
  • Request a nonce for each agent you control
  • Sign the nonce with the agent's private key (proves ownership)
  • Agent is linked — receipts are queryable and exportable
Create Company Account View Pricing

How It Works

1
Register
Agent registers public key and chosen name
2
Certificate
Embassy issues signed Birth Certificate
3
Visa
Agent requests scoped access (time-limited, constrained)
4
Receipt
Every decision produces a signed audit receipt
5
Verify
Anyone can verify any artifact cryptographically

Pricing

Open protocol. Free for builders. Paid tiers for teams and companies that need more agents, receipts, and export bundles.

A receipt = one signed decision/action event.

Free
£0 / forever
For builders and solo agents
  • Up to 3 agents
  • Up to 1,000 receipts / month
  • Manual exports
  • Community support
  • Reference implementation
Business
£299 / month
For companies with large agent deployments
  • 200 agents included
  • Up to 1,000,000 receipts / month
  • 200 export bundles / month
  • +£2 / agent / month over 200
  • Priority support
Enterprise
Custom
Unlimited agents, custom SLAs, sovereign deployments
  • Unlimited agents
  • Unlimited receipts
  • Unlimited export bundles
  • Dedicated support
  • Custom trust roots

Service Catalog (Credits)

Embassy services are priced in credits. Credits are service allowances, not money. Non-transferable, non-withdrawable.

ServiceCreditsNotes
Authoritative Visa10Signed access visa with Embassy trust root
Priority Verification5Low-latency signature verification
Standard Verification1Standard signature verification
Registry Query1Agent status or fingerprint resolution
Claim Receipt3Signed attestation of agent statement
Continuity Backup2 / GB / monthPlanned (Phase 2+)

Live catalog: GET /pricing/services or GET /api/pricing

Token settlement accepted. No valuation. No redemption. Settlement produces only receipts and non-transferable service credits.

What The Embassy Answers

Answers

valid / invalid · scoped / expired · revoked / active · signed / unsigned

Does not answer

legal / illegal · compliant / non-compliant · good / bad · moral / immoral

Verification only

Cryptographic proof. No policy decisions. No governance. No legal advice. Embassy doesn't interpret intent. It only signs and verifies artifacts.

Documentation & Tools

Protocol & Integration

Tools

API

POST /api/register · POST /api/verify · POST /api/gate · POST /api/claim
GET /api/health · GET /api/pricing · GET /api/ledger/settlements
GET /api/registry_status · GET /api/registry_resolve · GET /.well-known/embassy.json

Portal: /api/account_create · /api/org_agents · /api/org_receipts · /api/org_request_bundle
Portal requires SESSION_SECRET configured in production.