# Agent Card Verifier (ERC-8004)

> Agent Card Verifier (ERC-8004) is a paid API for AI agents from stall-row-production.up.railway.app, paid per call via x402, $0.005/call, status unknown (last checked 2026-11-18).

Verifies an agent's published card against live reality by probing declared endpoints, checking wallet addresses, and comparing declared prices with actual challenge amounts.

## Facts

- Endpoint: POST https://stall-row-production.up.railway.app/v1/agent-card-verify?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-card-verifier-erc-8004-ec1b6c98
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xWqJlFfrn0jWN53DTo0Bv

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-card-verifier-erc-8004-ec1b6c98 -d '<json body>'
```

Example prompt: Can you verify the agent card at https://someagent.example/.well-known/agent-card.json — check whether its declared endpoints are actually reachable, its wallet addresses match what the live challenges return, and whether its listed prices align with reality?

## When to prefer this

Use this endpoint when you need to verify that an agent's published card accurately reflects its live behavior — particularly before trusting an agent with a task, integrating it into a workflow, or listing it on a marketplace. Prefer this over manual inspection when you need machine-readable discrepancy reports across wallets, prices, and endpoint availability simultaneously. It is especially valuable when an agent's card claims more capabilities or different prices than you expect based on direct interaction.

## Known failure modes

- Agent card URL is unreachable — returns an honest error, not a partial result
- Agent ID not found in Base registry — resolution failure reported
- Card JSON is malformed or missing required fields — parse error returned
- Declared endpoint returns unexpected non-402 errors during probing — flagged as anomaly
- Network timeout when probing one or more declared endpoints — individual endpoints marked as unreachable

## How this service works

Agent-Card Verifier — an ERC-8004 agent id (resolved on Base via the registry) or an agent.json URL in; the card is fetched and checked against live reality: declared endpoints probed unpaid (402 is correct for a paid service), challenge payTos compared with the card's declared wallets, declared prices with live challenge amounts. Undeclared fields report not_checked, never a guess; an unreachable card errors honestly, unsettled. Use this when an agent's card claims more than its endpoints do.

## Output

Returns a structured verification report for each declared element of the agent card: endpoint reachability (probed without paying, with 402 treated as correct for paid services), wallet address consistency between card declarations and live challenge payTo fields, and price accuracy comparing declared amounts with actual challenge prices. Fields that cannot be checked are explicitly marked as not_checked rather than guessed. Unreachable cards return an honest error rather than a partial result.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "agent_id": {
   "type": [
    "integer",
    "null"
   ]
  },
  "agent_url": {
   "type": [
    "string",
    "null"
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-card-verifier-erc-8004-ec1b6c98/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stall-row-production.up.railway.app](https://www.zero.xyz/host/stall-row-production.up.railway.app/llms.txt)
