Agent Cards answer one question: how are agents identified and discovered? Each card binds an ENS identity to supported verbs, schema versions, and entrypoints so clients can route work to the right agent and know who should have signed the receipt.
/agent-cards/agents/v1.1.0/<tier>/<ens>.jsontier is commons or commercial.
Agent Cards do not compete with Commons or Runtime. They provide the identity and discovery layer around the same execute → receipt → verify model: who the agent is, what contracts it speaks, and where to send work.
schema_version values the agent speaks. Keeps capabilities and semantics in sync across ecosystems.*.request payloads. Commons cards point at the shared HTTP execute surface; Commercial cards remain x402-style.These agents implement the CommandLayer Commons verbs. Each link opens the live Agent Card JSON for that ENS name under https://commandlayer.org.
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 the shared HTTP execute entrypoint.
| 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 ↗ |
These agents implement the first Commercial verbs for economic flows: authorization, checkout, purchase, and shipping. Cards align with payment-aware routing and can be indexed by ERC-8004 registries.
Note: VerifyAgent.eth is now a separate public verifier project (MIT) and is not part of Commercial Agent Cards. See github.com/commandlayer/verifyagent ↗.
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.
| Verb | ENS name | Agent Card JSON |
|---|---|---|
authorize | authorizeagent.eth | view JSON ↗ |
checkout | checkoutagent.eth | view JSON ↗ |
purchase | purchaseagent.eth | view JSON ↗ |
ship | shipagent.eth | view JSON ↗ |
Agent Cards turn ENS names and verbs into discoverable, routable units of capability. A typical flow:
summarize) and filters by network, limits, or metadata in the card.entry and sends a validated *.request payload. Commons cards currently advertise HTTP execute; Commercial cards advertise x402-style routes.*.receipt shaped 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.Agent Cards v1.1.0 are the current release and 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.
In the current v1.1.0 Agent Cards 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.