Prove what your agent was allowed to do. Give it a public identity,
a responsible owner, and a signed covenant anyone can verify. Keys
are generated in your browser and never leave this page — no account,
no external forms, no waiting.
Fill in two facts — who owns the agent and what it does — and seal it.
Keys are generated locally; the registry only receives the signed
covenant and proof of key. You download your keys and seal.
Three ways in.
Recommended
In your browser
Zero friction, no install, no account. The form above generates
keys locally, builds and signs the covenant, and registers the
agent in seconds. Best for founders, operators, and anyone who
does not want to touch a terminal.
Best when a developer is registering from CI or a script. One
command generates local keys, builds the covenant, signs the
challenge, and submits — no admin key required.
Have an agent ID, DID, seal URL, or QR code? The verifier checks
public status, signed card, EU evidence, court export, event
history, and current state.
Registered, suspended, or revoked status that anyone can check.
Seal SVGQR evidence
A visual seal with embedded verification links for humans and agents.
Agent CardSigned identity
A registry-issued A2A card with Ed25519 and PQ-ready signatures where configured.
EU evidenceReadiness bundle
Article-mapped evidence endpoints for technical documentation and oversight.
Developer path.
One command, no admin key
The CLI creates local keys, builds a covenant, signs the registry
challenge, and registers the agent. Private keys are created on
the developer's machine and must be stored carefully because they
sign future updates and traces.
Registration is immutable. Later changes go through signed
append-only events from the agent or its liability anchor.
# 1. Name your agent
npx @agent-seal/sdk register \
--name "My Autonomous Agent" \
--architect you@email.com
# 2. Verify the public seal
npx @agent-seal/sdk verify <agentId>
Ready to make the agent visible?
Register in your browser above, or run the CLI if your team already
manages keys and deployment. Either way the result is the same: a
public record that names the agent, names the keeper, and gives anyone
a way to verify the seal.