ChainWard
Verification PAYMENT-READYpayment-ready until 2026-10-12
On-chain risk checks an agent pays for per call: a counterparty report for a Base or BNB Chain address ($0.05), where an x402 seller's buyers get their USDC ($0.10), and the datasets behind published investigations ($10). Paid in USDC on Base; a check that fails is never charged. Reports that flag behavior are EAS attestations on Base.
Pay from $0.05 to $10.00 in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.
listed 2026-10-05 · no on-chain settlement recorded yet
VERDICT
ranking generation 3solid 84/100 #48 of 122 in Verification by measured score
What the score read on this service: status online, 100% uptime, latest daily rollup (no 30d window yet), 239ms response p95, x402 compliance 14 of 14, $0.05 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.
The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.
It is a score inside Verification, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 122 listings, this one among them. That set is wider than the 122 the position above is counted against, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.
Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.
ALTERNATIVES IN VERIFICATION
Other Verification services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).
| SERVICE | BAND | SCORE | UPTIME 30D | VOL 30D |
|---|---|---|---|---|
| scvd.store — evidence observatory for the x402 economy | strong | 94 | 100% | $549.73 |
| Rubric Protocol — Post-Quantum AI Attestation | solid | 93 | 99.8% | $34.73 |
| PHION Agent Services | solid | 89 | 99.9% | $1.50 |
| KushBitx AgentProof | solid | 89 | 100% | $1.52 |
| LION — Verified Company & Compliance Data | solid | 89 | 100% | $5.67 |
ASSESSMENT
updated 42m agoThe parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.
reliability 100%
- uptime · latest daily rollup
- -
- uptime 7d
- -
- uptime 30d
- -
- uptime 90d
- -
- response p95
- 239ms
- avg response
- 239ms
- total checks
- 1
Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.
compliance A (14/14)
14 of 14 x402 conformance checks pass. Full checklist below.
price $0.05 to $10.00 (p80 in Verification)
- price (min)
- $0.05
- price (max)
- $10.00
- category percentile (min)
- p80 in Verification
- category percentile (max)
- p97 in Verification
- endpoints / prices
- 3 / 3
- model
- tiered
- stability
- 100%
risk clean
No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.
- domain age
- 216d
- registrar
- Cloudflare, Inc
- hosting
- custom
- domain created
- 2026-03-02
Identity facts, not a risk score.
traction $0.00 30d · 0 buyers
- volume 30d
- $0.00
- buyers 30d
- 0
- settlements 30d
- 0
- measured since
- --- (start of our harvest window)
- last settlement
- ---
- top buyer share
- -
- trend 7d vs 30d
- -
- networks
- eip155:8453
- volume all-time
- $0
- settlements all-time
- 0
- median settlement 30d
- -
- max settlement 30d
- -
- settled via
- -
Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.
Top buyer share is part of the ranking score: a higher share lowers the traction part of the score, by up to half when one address holds all 30d volume.
WHAT IT DOES
ai-derivedNo AI synthesis has been produced for this service yet.
ENDPOINTS
| METHOD | PATH | DESCRIPTION | PRICE | NETWORK | ASSET | 402 CHANNEL |
|---|---|---|---|---|---|---|
| GET | /api/paid/termix-wallets/file | $10.00 | Base | USDC | header | |
| GET | /api/risk/seller-demand | $0.10 | Base | USDC | header | |
| GET | /api/risk/x402 | $0.05 | Base | USDC | header |
REQUEST / RESPONSE EXAMPLE
An unpaid request to GET /api/paid/termix-wallets/file returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.
curl -i 'https://api.chainward.ai/api/paid/termix-wallets/file'
// 402 response (captured by monitor) · 3 payloads · click to expand
[
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xf7Ee65130Fb2B3bb42Cc5cbFED085d7D482667cD",
"amount": "50000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 120
}
],
"resource": {
"url": "https://api.chainward.ai/api/risk/x402",
"tags": [
"base",
"risk",
"counterparty",
"agents",
"eas",
"attestation"
],
"mimeType": "application/json",
"description": "Fresh on-chain risk report for a Base or BNB Chain (?chain=bsc) address before you pay it: neutral signal band, every flag with its evidence and source, what was not assessed, and the EAS attestation if one exists. Never a safety verdict.",
"serviceName": "ChainWard counterparty check"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"address": "0x4baadba26c3c0bdef9e8faf173925d463aa53bb2"
}
},
"output": {
"type": "json",
"example": {
"data": {
"report": {
"band": "high-signal",
"chain": "base",
"flags": [
{
"id": "stranded_value",
"title": "USDC balance held in a dormant wallet",
"source": "https://base.blockscout.com/address/0x4baadba26c3c0bdef9e8faf173925d463aa53bb2",
"evidence": "Holds 5451.386272 USDC while classified dormant",
"severity": "high"
}
],
"address": "0x4baadba26c3c0bdef9e8faf173925d463aa53bb2",
"freshness": {
"ttl_state": "fresh",
"as_of_block": 51846337,
"generated_at": "2026-09-27T04:07:05.375Z"
},
"disclaimer": "Risk flags from on-chain behavior only. ChainWard cannot see social engineering, off-chain agreements, or intent. Absence of flags is not a guarantee of safety.",
"attestation": {
"uid": "0xda5dc4ca34777d908c3f16fc9eb10a75325d2c83683adb7539c8bc4ade6f6560",
"explorer_url": "https://base.easscan.org/attestation/view/0xda5dc4ca34777d908c3f16fc9eb10a75325d2c83683adb7539c8bc4ade6f6560"
},
"not_assessed": [
"Contract bytecode or source auditing",
"Social-engineering or off-chain reputation"
]
},
"status": "ready"
},
"success": true
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"type": "object",
"required": [
"address"
],
"properties": {
"chain": {
"enum": [
"base",
"bsc"
],
"type": "string",
"default": "base",
"description": "Chain the address is on. Payment is USDC on Base either way."
},
"address": {
"type": "string",
"pattern": "^0x[a-fA-F0-9]{40}$",
"description": "Address to check"
}
}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
},
"x402Version": 2
},
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xf7Ee65130Fb2B3bb42Cc5cbFED085d7D482667cD",
"amount": "100000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 120
}
],
"resource": {
"url": "https://api.chainward.ai/api/risk/seller-demand",
"tags": [
"base",
"bsc",
"x402",
"seller",
"demand",
"wash",
"counterparty",
"agents"
],
"mimeType": "application/json",
"description": "Where a seller's buyers get their stablecoins, on Base or BNB Chain (?chain=bsc): how much of its top buyers' money traces back to the seller, how much it pays back, and whether one wallet funds most buyers. Describes money flows, never intent.",
"serviceName": "ChainWard x402 seller check"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"address": "0x68396bd35874695ad86cd29410bd80a550991a2b"
}
},
"output": {
"type": "json",
"example": {
"data": {
"sample": {
"buyers": 500,
"capped": true,
"inflow_transfers": 1000
},
"address": "0x68396bd35874695ad86cd29410bd80a550991a2b",
"signals": [
{
"id": "buyers_funded_by_seller",
"title": "Most checked buyers' USDC traces back to this address",
"evidence": "30 of 30 top buyers reach this address within 3 hops of their largest funders (100% of their volume)."
},
{
"id": "common_funder",
"title": "One wallet funds most checked buyers",
"evidence": "0x82b551e820efc3503a3a27fc450e07e328daf91c is the largest funder of 50% of the top buyers checked."
}
],
"disclaimer": "Describes where stablecoins moved on this chain, not why. A common funder can be a legitimate faucet, exchange or custodian. Not a safety verdict.",
"walk_stops": {},
"window_days": 30,
"seller_funded": {
"hops": {
"3": 30
},
"buyers": 30,
"volume_share": 1
},
"buyers_checked": 30,
"paid_back_share": 0,
"top_buyer_share": 0.037,
"common_first_funder": {
"address": "0x82b551e820efc3503a3a27fc450e07e328daf91c",
"buyer_share": 0.5
},
"via_intermediary_share": 0
},
"success": true
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET"
],
"type": "string"
},
"queryParams": {
"type": "object",
"required": [
"address"
],
"properties": {
"chain": {
"enum": [
"base",
"bsc"
],
"type": "string",
"default": "base",
"description": "Chain the address is on. Payment is USDC on Base either way."
},
"address": {
"type": "string",
"pattern": "^0x[a-fA-F0-9]{40}$",
"description": "Address to check"
}
}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
},
"x402Version": 2
},
{
"error": "Payment required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xf7Ee65130Fb2B3bb42Cc5cbFED085d7D482667cD",
"amount": "10000000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 120
}
],
"resource": {
"url": "https://api.chainward.ai/api/paid/termix-wallets/file",
"tags": [
"base",
"dataset",
"sybil",
"airdrop",
"points",
"agents"
],
"mimeType": "application/json",
"description": "The full dataset behind a published ChainWard decode (e.g. every wallet in an incentive-farming audit, tiered, with the transactions behind each one). CSV.",
"serviceName": "ChainWard dataset"
},
"extensions": {
"bazaar": {
"info": {
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"slug": "termix-wallets"
},
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"contentType": "text/csv"
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method"
],
"properties": {
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"GET"
],
"type": "string"
},
"pathParams": {
"type": "object",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"pattern": "^[a-z0-9][a-z0-9-]{0,59}$",
"description": "File slug from GET /api/paid"
}
}
},
"queryParams": {
"type": "object",
"properties": {}
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
},
"routeTemplate": "/api/paid/:slug/file"
}
},
"x402Version": 2
}
] OVER TIME
All charts use the 30d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/chainward/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.
Median across 3 endpoints. Use the selector to isolate one.
checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression
COMPLIANCE
14/14 checks pass · grade Alast 402 captured 2026-10-05 · last up 2026-10-05
- 402 payload captured
- accepts[] array present
- payTo address recoverable
- payTo at accepts[0].payTo (conformant shape)
- payTo is a valid on-chain address
- atomic price declared
- atomic price in a sane range
- asset (token) address declared
- network resolves to CAIP-2
- payment scheme declared
- served over HTTPS
- declares the current x402 version (2)
- EIP-712 domain parameters present on every EVM entry
- x402 v2 envelope delivered in the payment-required header
SITE PILLARS
- homepage reachable
- openapi doc
- pricing page
- llms.txt
- robots.txt
- terms page
recent checks (4) live · click to expand
EMBED THIS BADGE
<a href="https://x402-list.com/services/chainward?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/chainward.svg" alt="ChainWard listed on x402-list" height="28"> </a>
[](https://x402-list.com/services/chainward?utm_source=badge&utm_medium=referral&utm_campaign=embed)
<a href="https://x402-list.com/services/chainward?utm_source=badge&utm_medium=referral&utm_campaign=embed"> <img src="https://x402-list.com/badge/chainward.svg?data=uptime" alt="ChainWard uptime on x402-list" height="28"> </a>