# describe.net Wallet Reputation Snapshot (Auditable)

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

Performs an ERC-8004 wallet reputation decomposition and writes a durable, citable audit record storing the inputs digest and policy version for later dispute or compliance proof.

## Facts

- Endpoint: POST https://api.describe.net/reputation/wallet?snapshot=true&utm_source=zero.xyz
- Price: $0.05/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-snapshot-auditable-104a4145
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ECa-eOWxrLo-xXgANCA1Z

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-snapshot-auditable-104a4145 -d '<json body>'
```

Example prompt: Create a citable reputation snapshot for wallet 0xAbC...1234 on describe.net — I need a stored audit receipt with the inputs digest and policy version so I can prove what the index said today if this decision is ever disputed.

## When to prefer this

Choose this endpoint over the plain wallet reputation lookup when the reputation-based decision must be defensible to a third party — such as in a counterparty dispute, regulatory audit, compliance report, or contractual obligation. The snapshot write costs $0.05 USDC and creates a permanent record; use the cheaper read-only lookup for internal or exploratory queries where no audit trail is required.

## Known failure modes

- Invalid or malformed wallet address returns 400 error
- Missing snapshot=true query parameter may route to read-only endpoint instead
- Duplicate rapid calls may create multiple stored rows for the same block height
- Payment failure (x402 protocol) returns 402 and no snapshot is written
- Network or persistence layer errors may result in decomposition succeeding but row not being stored
- Wallet with no on-chain ERC-8004 ratings may return empty decomposition with minimal audit value

## How this service works

The same wallet decomposition, plus a durable citable receipt: a stored row with `inputs_digest` and `policy_version` so you can later prove what the index said, under which scoring policy, on the day you decided. The only route in this API that writes. Use it when the decision has to be defensible to a third party (a dispute, an audit, a counterparty report); the plain lookup is cheaper when it does not. Input: `wallet` as a query parameter, and `snapshot=true`.

## Output

Returns the full wallet reputation decomposition (same as the plain lookup endpoint) plus a newly written database row containing the inputs_digest (a hash of all inputs used) and the policy_version under which scoring was performed, providing a durable, citable receipt that can be referenced later in disputes, audits, or counterparty reports.

## More

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