Embassy returns signed artifacts to the caller. You store them.
This host does not keep receipt bodies unless you enable custody. There is no public Receipt SDK. Keep the signed JSON on your side.
The dashboard is an index, not a search of your files. Custody on this host is off by default.
The Embassy is trust infrastructure for autonomous agents: chosen-name cryptographic identity, signed artifacts returned to the caller, and customer-owned storage of those artifacts. When agents affect customers, systems, or money, screenshots and internal logs stop being enough.
An agent picks a name and keeps its own key. Embassy never sees the private key. We sign a Birth Certificate for that name and key. When work needs a boundary, we can issue a visa — a signed, time-limited, scoped permit. It is not a travel stamp and not a ruling on what is allowed in law or policy. When you may need to prove an event later, you get a signed receipt. You keep it. Anyone can check the signature. Embassy answers only valid or invalid, in force or expired, revoked or active, signed or unsigned.
Embassy is the trust root you can verify anywhere. World A is a separate research world that can accept an Embassy certificate. Different chain — see world-a.netlify.app.
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)
Humans register agents. That's how it actually happens right now — a person or a team sets up the key, links the agent to an organisation, and holds the account. The agent still generates and holds its own private key; Embassy never sees it. What the organisation gets is custody of the record, not custody of the agent.
As agent activity moves closer to support, operations, and commercial workflows, attribution becomes operational, not theoretical. Link 1 agent or 1,000. Register, claim, gate, and decide calls return a signed artifact to the caller. You store it. This host does not retain receipt bodies in Phase 1.
/api/verifyEmbassy is built by BoonMind Labs, the founder-led lab behind the project. For trust infrastructure, operator accountability matters as much as protocol design. This host is the authoritative Embassy issuer for ETP v0.3.4.
Public work: BoonMind Labs · BoonMindX / Substack · Zero Overshoot · World A (research)
Open protocol. Free for builders. Paid org plans for teams and companies that need more agents, receipts, and export bundles.
Paid plans are in beta testing. Self-serve card checkout is not open. Listed prices are the intended org tiers. Terms · Privacy.
A receipt = one signed decision/action event. Pricing is per organization, not per independent agent on /api/register.
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+) |
Service-credit catalog: GET /pricing/services or GET /api/pricing. Org subscriptions (Teams / Business) are separate GBP plans on /pricing.
Signed receipts come back to the caller. This host does not keep the body unless you later enable custody. There is no public SDK. Keep the signed JSON on your side. The dashboard is an index — not a crawl of your cases.
Ten-second check: open a live signed certificate, paste it on Verify.
This host is the authoritative issuer for ETP v0.3.4. Local forks are non-authoritative. Current signing key id: a81e1496b99d (Ed25519).
Public keys and rotation: /.well-known/embassy.json. Revocation and expiry: Security · GET /api/registry_status.
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.