Assisted registration
Best for founders, agencies, compliance teams, and operators who do not want to handle keys or JSON. You prepare the basic facts; we help turn them into a signed Agent Seal record.
Start assisted pathStart here
Register your agent without becoming a protocol expert.
Agent Seal gives an AI agent a public identity, a responsible human or organisation, a signed covenant, and a seal that others can verify. The cryptography stays in the background; the first question is simple: who owns this agent, and what is it allowed to do?
Choose the right path.
Developer registration
Best when you have a developer who can run the CLI. It generates local keys, builds the covenant, signs the challenge, and submits the registration without an admin API key.
See CLI commandVerify a record
If you already have an agent ID, DID, seal URL, or QR code, open the verifier. It checks public status, signed card, EU evidence, court export, event history, and current state.
Open verifierWhat you need before registration.
You do not need to speak in API terms. These are the plain facts a serious record needs.
Agent identity
- Public agent name
- Model or system name
- What the agent actually does
- Where the agent will be used
Human responsibility
- Responsible person or organisation
- Jurisdiction or operating country
- Contact path for escalation
- Who can suspend or replace the agent
Allowed scope
- What the agent may do
- What the agent must never do
- Whether humans review important actions
- Whether EU AI Act evidence is needed
Evidence after launch
- Public seal and badge
- Signed Agent Card
- Trace and event history
- Court export and readiness report
What you get back.
Registered, suspended, or revoked status that anyone can check.
A visual seal with embedded verification links for humans and agents.
A registry-issued A2A card with Ed25519 and PQ-ready signatures where configured.
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.
Source checkout
Endpoint reference
npm --prefix packages/agent-seal run build
node packages/agent-seal/dist/cli.js enroll \
--registry-url https://agent-seal.xyz \
--agent-name "Support Disclosure Agent" \
--anchor-name "Acme Ltd" \
--jurisdiction "Germany" \
--out ./support-disclosure-agentReady to make the agent visible?
Start with the assisted path if you are not technical. Use the CLI if your team already manages keys and deployment. In both cases, the result should be the same: a public record that names the agent, names the keeper, and gives others a way to verify the seal.