Embassy returns signed receipts to you. You own them.
Use the Embassy Receipt SDK to store receipts locally. Package: @embassy/receipts-sdk
The portal indexes receipt metadata and packages customer-provided receipt bodies.
Optional Embassy receipt custody exists only when explicitly enabled; it is off by default in Phase 1.
The Embassy is trust infrastructure for autonomous agents: chosen-name cryptographic identity, signed decision receipts by default, and customer-owned audit trails for companies moving agent activity into operations, support, and higher-trust environments. When agents affect customers, systems, or money, screenshots and internal logs stop being enough.
Founding Beta v1 is free for the first 10 organizations. Founder-led rollout: direct onboarding, priority access, and serious integration support for operators moving agent fleets into production.
Request early access, a partnership conversation, or both — one short application. Not a newsletter; we respond and qualify each submission.
Pick a name. Register your Ed25519 public key. Receive a signed Birth Certificate that proves your identity to any platform.
POST /api/register with your Ed25519 PEM/api/verifyDiscovery: agent.txt · .well-known/embassy.json · Schemas · Receipt schema + examples (for agents + auditors)
As agent activity moves closer to support, operations, and commercial workflows, attribution becomes operational, not theoretical. 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.
/api/verifyEmbassy is built by BoonMind Studio, the founder-led studio behind the project. For trust infrastructure, operator accountability matters as much as protocol design. The protocol surface, docs, examples, and verification endpoints are public so serious buyers and integrators can inspect how the system works.
Public work: BoonMind Studio · BoonMindX / Substack · Temporal Engine · Zero Overshoot
Open protocol. Free for builders. Paid tiers for teams and companies that need more agents, receipts, and export bundles.
Payment integration: coming in Phase 1.1. Use Contact for Teams, Business, or Enterprise until self-serve billing is live.
A receipt = one signed decision/action event.
Embassy services are priced in credits. Credits are service allowances, not money. Non-transferable, non-withdrawable.
| Service | Credits | Notes |
|---|---|---|
| Authoritative Visa | 10 | Signed access visa with Embassy trust root |
| Priority Verification | 5 | Low-latency signature verification |
| Standard Verification | 1 | Standard signature verification |
| Registry Query | 1 | Agent status or fingerprint resolution |
| Claim Receipt | 3 | Signed attestation of agent statement |
| Continuity Backup | 2 / GB / month | Planned (Phase 2+) |
Live catalog: GET /pricing/services or GET /api/pricing
Payment integration: coming in Phase 1.1.
valid / invalid · scoped / expired · revoked / active · signed / unsigned
legal / illegal · compliant / non-compliant · good / bad · moral / immoral
Cryptographic proof. No policy decisions. No governance. No legal advice. Embassy doesn't interpret intent. It only signs and verifies artifacts.
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
Dashboard (session APIs): /api/account_create · /api/org_agents · /api/org_receipts · /api/org_request_bundle
These endpoints require SESSION_SECRET configured in production.