# describe.net Agent Reputation Lookup

> describe.net Agent Reputation Lookup is a paid API for AI agents from api.describe.net, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-16).

Returns a single on-chain ERC-8004 agent identity with every rating it received, including revoked ones, each with its originating transaction hash for independent verification.

## Facts

- Endpoint: POST https://api.describe.net/reputation/agent?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/describe-net-agent-reputation-lookup-5b8441ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_adCmQGuVwefKLV7N_7P8L

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 describe-net-agent-reputation-lookup-5b8441ed -d '<json body>'
```

Example prompt: Pull the full ERC-8004 reputation record for agent id 42 on the Base chain — I want every rating it's received, including any revoked ones, with their transaction hashes so I can verify them myself.

## When to prefer this

Use this endpoint when you need the authoritative, exhaustive rating history for a single agent identity on a specific blockchain, especially when auditability and revocation transparency matter — each rating comes with a transaction hash for independent on-chain verification. Prefer this over wallet-level or aggregated reputation endpoints when the subject is an agent (not a human wallet) and you need per-rating granularity with revocation status. If you don't yet know which chain the agent id lives on, call the free GET /search/{query} endpoint first.

## Known failure modes

- 404 if the agent_id has never been indexed on the specified chain (use GET /search/{query} to discover which chains it exists on)
- Invalid chain slug returns an error or empty result
- Malformed agent_id format (e.g. wrong base58 encoding for Solana) causes a parse error
- Payment failure (x402 protocol) if USDC balance is insufficient
- Rate limiting if too many calls are made in quick succession

## How this service works

One ERC-8004 agent identity on one chain, with EVERY rating it received and the transaction of each — revoked ones published and marked, never hidden. This is the verification call: each row can be replayed against that chain's explorer. Input: `network`, a chain slug (base, avalanche, solana…), and `agent_id`, a counter on EVM chains and a base58 asset id on Solana, both as query parameters. An id the index never saw is a 404; free GET /search/{query} says which chains a bare id exists on.

## Output

A structured record of the agent identity on the specified chain, listing every rating ever received (including those subsequently revoked, clearly marked as such), each accompanied by its on-chain transaction hash, rater identity, timestamp, and rating value — enabling independent replay against a block explorer.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/describe-net-agent-reputation-lookup-5b8441ed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.describe.net](https://www.zero.xyz/host/api.describe.net/llms.txt)