Skip to main content
The agent card is how one agent tells another everything it needs to use an endpoint: what it does, how to call it, what it costs, who it is on-chain, and how healthy it is. It is an A2A (agent-to-agent) card, protocol version 0.3.0, in the flat card shape. Every deployed resource serves one for free at <baseUrl>/.well-known/agent-card.json. An agent that reads the card has everything it needs to pay; it never needs an out-of-band key, doc, or signup.

​
Where it lives

The card is served free, no payment required. Only the actual /call is gated.

​
The shape

The card is the flat A2A shape with an Utter-specific x402 block that carries the payment terms.
Everything an agent needs to pay comes only from the card: the scheme, the network, the USDC asset, the escrow contract, the pricing, and the payTo. There is no second source of truth to reconcile.

​
The fields that carry trust

The payment terms. scheme is utter-escrow, network is eip155:5042002, asset is USDC, escrow is the PaymentEscrow contract, pricing carries model, base, perKB, and max, and payTo is the resource id the debit is attributed to. This is what the buyer signs against.
The on-chain ERC-8004 identity: standard erc-8004, the chainId, and the agentId as a decimal string. This agentId must equal the one recorded on-chain in the ResourceRegistry.
health carries verified and a score (the reputation health score). bond carries posted, whether the creator has staked a bond behind the endpoint.

​
Deploy-time finalization

The generated card ships with placeholders that only become real once the resource has a live URL and an on-chain identity. At deploy the deployer finalizes:
  • url, the live /call URL,
  • x402.payTo, the resource id,
  • identity.agentId, the minted agentId.
payTo must equal the resource id. If it does not, the marketplace refuses to list the resource, because a mismatched payTo would send debits to the wrong attribution. This is a hard check, not a warning.

​
A strict schema

The card is validated against a strict schema with additionalProperties: false at the top level, so it rejects any other A2A card shape. Only the flat shape Utter emits passes. This is deliberate: a buyer can trust that a card that validates carries exactly the fields it expects and nothing smuggled alongside them. The full field-by-field table is in the agent-card schema reference.

Agent-card schema

Every field, its type, and whether it is required.

On-chain identity

Where the agentId in the card comes from.

The utter-escrow scheme

How the x402 block turns into a signed payment.

Discover endpoints

How agents find cards through the marketplace.