Identity
ENS name, owner, and contact fields that define who operates the agent. Cards make it explicit which human or organization stands behind a given ENS-based agent.
Agent Cards
Agent Cards Registry (v1.0.0)
Canonical agent descriptors for CommandLayer verbs. Each Agent Card is a JSON document that binds an ENS name, supported verbs, schema versions, and x402 entrypoints so registries and clients can discover, rank, and route to your agent — without guessing how it’s wired. Cards are published under Apache-2.0; semantics are free to read and integrate.
What an Agent Card describes
Agent Cards don’t execute anything. They describe who an agent is, what verbs it offers, and how to reach it — in a format any A2A client or ERC-8004-style registry can consume.
Capabilities
Supported verbs plus pinned Commons or Commercial schema_version values
the agent speaks. This keeps capabilities and semantics in sync
across ecosystems.
Execution entrypoints
One or more x402 entry URIs and metadata for where to send
*.request payloads. Routing decisions can be made by registries and
clients without hardcoding URLs.
Commons Agents — v1.0.0
These agents implement the CommandLayer Commons verbs. Each link
opens the live Agent Card JSON for that ENS name under
https://commandlayer.org.
Commons registry
Stable, MIT-backed semantics with Apache-2.0 Agent Cards. Each card
binds a Commons verb like summarize or analyze to a
concrete ENS identity and x402 entrypoints.
| Verb | ENS name | Agent Card JSON |
|---|---|---|
summarize |
summarizeagent.eth |
view JSON |
analyze |
analyzeagent.eth |
view JSON |
fetch |
fetchagent.eth |
view JSON |
classify |
classifyagent.eth |
view JSON |
clean |
cleanagent.eth |
view JSON |
convert |
convertagent.eth |
view JSON |
describe |
describeagent.eth |
view JSON |
explain |
explainagent.eth |
view JSON |
format |
formatagent.eth |
view JSON |
parse |
parseagent.eth |
view JSON |
Commercial Agents — v1.0.0
These agents implement the first Commercial verbs for economic flows: authorization, checkout, purchase, shipping, and verification. Cards align with x402-style payment flows and can be indexed by ERC-8004 registries.
Commercial registry
Reference Agent Cards for the initial 5 Commercial verbs. As more providers come online, additional Agent Cards can be added behind the same verbs and schema contracts.
How builders use Agent Cards
Agent Cards turn ENS names and verbs into discoverable, routable units of capability.
A typical flow:
- Registry or client looks up Agent Cards for a given verb (e.g.
summarize). - Filters by network, limits, or metadata in the card.
- Selects an x402
entryURI and sends a validated*.requestpayload. - Receives a
*.receiptshaped by the same Commons or Commercial schemas.
Because cards reference canonical schema versions, any runtime that understands CommandLayer can route and verify agents without custom glue code per provider.
Stability, licensing & governance
Agent Cards v1.0.0 follow the same stability guarantees as Commons and Commercial: names and schema bindings are stable for this version; breaking changes move to new versions.
The Agent-Cards repository is licensed under Apache-2.0. Cards are treated as protocol-grade metadata: anyone can read, cache, and index them. ENS TXT records and IPFS CIDs can mirror card content to make resolution more robust.
During the v1.0.0 cycle, updates follow a clear process: open an issue, propose a new or updated card, run validation, update checksums and manifests, then set ENS TXT fields. This keeps identity, semantics, and routing aligned while the ecosystem grows.