Daily transfers, volume and coverage →
10x402.com · 10x402.com · Crypto & Payments
Run ONE named check against a response you paste
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-31) | $0.00 | 0 |
| Last 7 days | $0.008 | 2 |
| Last 30 days | $0.02 | 5 |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0x885e7bef433eb78f5976b28a7c10739c98db11e5 | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
| Solana | 6Cg4g7rXQApimMc9wVJGLLZfHsvbwGpGrUpGDgyJ2RaP | Exclusive to this catalogue serviceFrom source record · source: x402_bazaar |
All 1 retained sending addresses are listed below. Source: on-chain transfer scans. Dates are UTC days.
| Network | Full wallet address | Transfers | First / last observed | Last scanned (UTC) |
|---|---|---|---|---|
| Base | 0xa1d1c0cf717402ff3651aa4873ccf96410b01978 | 1 | 2026-10-30 / 2026-10-30 | 2026-10-31 23:38:42 |
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 26,598 (85.3 %) |
|---|---|
| With a published price | 28,919 (92.7 %) |
| With attributable inflows | 296 (0.9 %) |
| Observed inflows · 30d | $626,736.92 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
API recommendation and x402 discovery for your task. Required query: need. Which API should I call? Recommends which x402 API to use for any task, with evidence. Describe a task in plain words. Compare up to five paid AP...
Payment quote with amount, asset, and merchant wallet
OpenAI-compatible chat completions across the Venice AI model catalog. Pay per request in USDC on Base via x402, with no account and no API key. Overpayment is never lost: it banks as reusable wallet credit for your next...
One HTTP request per host, matched against an in-house signature set. Every hit carries a confidence value from 0 to 100 and the evidence it rests on: response header, asset path, cookie name, meta generator, DNS or ASN...
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.004 | USDC |
| Solana | exact | 0.004 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 4000 = 0.004 USDC per call on Base. 2 payment options published.
endpoint
https://10x402.com/lint/envelope/one
{
"body": {
"body": "{\"x402Version\":1,\"accepts\":[{\"scheme\":\"exact\",\"network\":\"base\",\"maxAmountRequired\":\"1000\",\"resource\":\"https://example.com/api/thing\",\"description\":\"an example paid endpoint\",\"mimeType\":\"application/json\",\"payTo\":\"0x0000000000000000000000000000000000000001\",\"maxTimeoutSeconds\":60,\"asset\":\"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913\",\"extra\":{\"name\":\"USD Coin\",\"version\":\"2\"},\"outputSchema\":{\"input\":{\"type\":\"http\",\"method\":\"POST\",\"discoverable\":true,\"bodyType\":\"text\",\"description\":\"the request body\"},\"output\":{\"type\":\"string\",\"description\":\"the response body\"}}}]}",
"check": "V2_HEADER_PRESENT",
"headers": {
"content-type": "application/json"
},
"status": 402
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": "{\"check\":\"V2_HEADER_PRESENT\",\"applied\":true,\"passed\":false,\"finding\":{\"severity\":\"error\",\"code\":\"V2_HEADER_PRESENT\",\"message\":\"no PAYMENT-REQUIRED response header \u2014 this endpoint publishes no x402 v2 envelope.\",\"fix\":\"Add a PAYMENT-REQUIRED response header to the 402 carrying the standard-base64 JSON v2 envelope. This costs you DISCOVERY rather than payment, and the distinction is worth being precise about: @x402/core reads the header first but DOES fall back to a v1 body when there is none, so the current client generation can still pay you. What it cannot do is find you \u2014 CDP marks the PAYMENT-REQUIRED header a required indexing check, so a v1-only 402 is not catalogued at all, and a strictly-v2 client cannot pay it either. Keep the v1 body exactly as it is; the two versions share a 402 without either noticing the other.\",\"core\":false,\"sources\":[{\"kind\":\"spec\",\"ref\":\"specs/transports-v2/http.md:7-25 \u00a7 Payment Required Signaling\"},{\"kind\":\"cdp-validator\",\"ref\":\"cdp-validator-toolshed.json preflight[6] payment_required_header (required)\"},{\"kind\":\"client-code\",\"ref\":\"@x402/core@2.23.0 dist/cjs/http/index.js:1620-1628 \u2014 the v2 client DOES fall back to a v1 body\"},{\"kind\":\"field-report\",\"ref\":\"x402-foundation/x402#3091 \u2014 x402-fetch@1.x is still a live buyer population\"}]},\"regime\":\"bazaar\",\"severity\":\"error\",\"core\":false,\"sources\":[{\"kind\":\"spec\",\"ref\":\"specs/transports-v2/http.md:7-25 \u00a7 Payment Required Signaling\"},{\"kind\":\"cdp-validator\",\"ref\":\"cdp-validator-toolshed.json preflight[6] payment_required_header (required)\"},{\"kind\":\"client-code\",\"ref\":\"@x402/core@2.23.0 dist/cjs/http/index.js:1620-1628 \u2014 the v2 client DOES fall back to a v1 body\"},{\"kind\":\"field-report\",\"ref\":\"x402-foundation/x402#3091 \u2014 x402-fetch@1.x is still a live buyer population\"}],\"summary\":{\"versions_detected\":[1],\"payTo\":\"0x0000000000000000000000000000000000000001\",\"network\":\"base\",\"price\":\"$0.001 (1000 atomic)\"},\"checks_run\":1}",
"format": "application/json",
"type": "text"
}
Examples are the provider's own, not a call we made.
The observed inflow implies about 5 calls at list price; the source counted 4 (factor 1). A transfer is still not a purchase, but the order of magnitude holds — this is the strongest monetisation signal in the catalogue short of a receipt feed.
Peers with attributed inflows →296 of 31,187 services (0.9%) in Crypto & Payments have attributable inflows; 26,598 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Run ONE named check against a response you paste
Quoted from x402 Bazaar · source record · read 2026-11-01
Observed transfers
· confidence medium
Token transfers reached this service's own payout address. A transfer is not a purchase, and shared, refunded or unrelated transfers cannot be excluded.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is $0.02 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.
Cross-check. At the published price the observed inflow would cover about 5 calls; the source counted 4. Two independent measurements of the same question — they never match exactly, because the effective price differs per call size and the address can also receive unrelated transfers.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://10x402.com/lint/envelope/one
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-11-01 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-11-01 |
| Payment | Provider claim |
2 rails: Base, Solana · payee 0x885E7BEF433eb78F5976b28A7c10739c98DB11E5
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-11-01 |
| Pricing | Provider claim |
0.004 USDC per call
EvidenceAtomic amount 4000 = 0.004 USDC per call on Base. 2 payment options published. Netzwerk: Base, Solana. |
api.cdp.coinbase.com | 2026-11-01 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-11-01 |
| Provider | Provider claim |
10x402.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-11-01 |
| Usage | Verified |
4 calls / 3 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-11-01. Letzter Aufruf laut Quelle: 2026-10-30T02:19:57.449Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-11-01 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.