GET /v1/reputation/{address}
API Reference
GET /v1/reputation/{address}
Look up the cached reputation profile for any wallet address.
GET
GET /v1/reputation/{address}
Request
Headers
Path parameters
Query parameters
When
chain is provided, the chains array and agents array are filtered to that chain.
Response (paid plans)
Paid plans receive the full response:operator_score is only present when the address has operator data (i.e., owns registered agents). reputation is only present on paid tier when the address has agent feedback data.
Response (Free tier)
Free tier receives a redacted response; score, grade, and entity type only. Dimensions, confidence, payment activity, reputation, identity details, and evidence are omitted.Top-level score
When the address is an operator (owns agents), the top-levelscore reflects the operator score; a tail-risk weighted average across all agents on all chains. When the address has no agents, the top-level score is the highest per-chain address score.
Per-chain scores and classification are in the chains array. On paid plans, this also includes identity, activity, and evidence.
Data semantics
Thedata_semantics field describes what kind of transaction data was used to compute the score. The current value is candidate_payment_activity_with_verified_subset, meaning the score is based on candidate payment transactions with a verified subset where available.
Score status values
Unknown address (404)
If the address has not been indexed:POST /v1/assess to score any address on-the-fly, including unknown ones.
Verification level
Theverification_level field indicates how far the operator behind this address has progressed through identity verification.
This endpoint is read-only. It returns cached data and never triggers scoring. For fresh, on-the-fly scoring, use
POST /v1/assess (available on every tier, gated by monthly quota).