# describe.net Wallet Reputation History

> describe.net Wallet Reputation History is a paid API for AI agents from api.describe.net, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-15).

Returns a time-series of a wallet's ERC-8004 reputation score changes, showing when scores moved, which ratings drove each change, and marking revoked ratings.

## Facts

- Endpoint: POST https://api.describe.net/reputation/history?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/describe-net-wallet-reputation-history-ad832d08
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jqDUXk1v5EbwTQmfd2g2t

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-wallet-reputation-history-ad832d08 -d '<json body>'
```

Example prompt: Show me the full week-by-week reputation history for wallet 0x4a3b...c9f2 on describe.net — I want to see how the score moved over time and whether any ratings were revoked.

## When to prefer this

Use this endpoint when you need to understand the trajectory and authenticity of a wallet's reputation over time, not just its current score. It is the right choice when verifying whether a high score is the result of sustained peer recognition or a recent batch of ratings, and when checking for revocations that would undermine trust. Prefer this over a single-score lookup when due diligence, counterparty vetting, or fraud detection is the goal.

## Known failure modes

- Invalid or malformed wallet address returns a 400 error
- Unknown wallet with no reputation history returns empty series or 404
- Invalid bucket value (not 'week' or 'month') returns a validation error
- Rate limiting or payment failure returns a 402 or 429 response
- Network timeout if the chain data aggregation takes too long

## How this service works

The dated series of one wallet's reputation: how the score moved, when, and on which ratings — revoked ones included and marked. It answers the question a single number cannot: is this a wallet that earned its standing over time, or one that acquired it last week. Input: `wallet` as a query parameter; `bucket` is `week` (default) or `month`.

## Output

A chronologically ordered series of reputation score snapshots for the specified wallet, bucketed by week or month. Each entry shows the score at that point in time, the ratings that contributed to the change, and flags any ratings that have since been revoked. This lets an agent distinguish wallets with slow, organic reputation growth from those with sudden, potentially artificial spikes.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/describe-net-wallet-reputation-history-ad832d08/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)