View daily earnings, market cap, volume and coverage →
x402-catalog-history.ai-business-surface.workers.dev · x402-catalog-history.ai-business-surface.workers.dev · Crypto & Payments
| Day · UTC | Earned | Gross volume | Refunds | Observed transfers | Market cap | Revenue coverage |
|---|---|---|---|---|---|---|
| 2026-10-26 | — | — | — | — | — | none |
| 2026-10-25 | — | — | — | — | — | none |
| 2026-10-24 | — | — | — | — | — | none |
| 2026-10-23 | — | — | — | — | — | none |
| 2026-10-22 | — | — | — | — | — | none |
| 2026-10-21 | — | — | — | — | — | none |
| 2026-10-20 | — | — | — | — | — | none |
View daily history → · UTC days; today's figures are partial.
Canonicalize JSON before you hash, compare or sign it: one POST takes a JSON string or any JSON value and returns the RFC 8785 (JCS) form, its SHA-256 and its UTF-8 byte length. Object keys are ordered by UTF-16 code units, strings use minimal escaping, numbers use ECMAScript Number::toString, and arrays keep their order. Duplicate keys, NaN, Infinity, trailing commas and a lone surrogate are refused with 400 before any payment; integers outside +-2^53 come back with a number_precision_loss warning instead of being silently rounded. input_sha256 is the hash of the json as supplied, so it differs from sha256 when only whitespace or key order changed. The value is not stored, no URL is fetched and nothing is signed or transferred. curl: POST /json-canonical -H 'content-type: application/json' -d '{"json":"{\"b\":2,\"a\":1}"}' . Response: {canonical, sha256, bytes, input_sha256, warnings[], canonicalization, limits, paid, delivery}. No keys, no account, one POST, one delivery - 0.002 USDC. A purchase is two calls by design: this first call returns 402 with the price and the payment terms, and you then repeat the same request with the PAYMENT-SIGNATURE header to receive the 200 delivery.
Quoted from PayAI · source record · read 2026-10-26
No settled payment on record. Earnings for this service are unknown — not zero.
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.
{
"body": {
"json": "{\"b\":2,\"a\":1}"
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
{
"type": "json",
"example": {
"paid": true,
"bytes": 13,
"sha256": "0000000000000000000000000000000000000000000000000000000000000000",
"delivery": {
"payer": "0x\u2026",
"payment": {
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"pay_to": "0x6f60659390aDA1D02B14024d8c9d0C889f2F89c3",
"scheme": "exact",
"network": "eip155:8453",
"transaction": "0x\u2026",
"amount_atomic": "2000"
},
"delivered_at": "2026-10-20T00:00:00.000Z"
},
"warnings": [],
"canonical": "{\"a\":1,\"b\":2}",
"checked_at": "2026-10-20T00:00:00.000Z",
"input_type": "string",
"product_id": "x402-json-canonical",
"input_sha256": "0000000000000000000000000000000000000000000000000000000000000000",
"schema_version": 1
}
}
Examples are the provider's own, not a call we made.
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://x402-catalog-history.ai-business-surface.workers.dev/json-canonical
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
facilitator.payai.network | 2026-10-26 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
facilitator.payai.network | 2026-10-26 |
| Payment | Provider claim |
1 rail: Base · payee 0x6f60659390aDA1D02B14024d8c9d0C889f2F89c3
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. |
facilitator.payai.network | 2026-10-26 |
| Pricing | Provider claim |
0.002 USDC per call
EvidenceAtomic amount 2000 = 0.002 USDC per call on Base. Netzwerk: Base. |
facilitator.payai.network | 2026-10-26 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
facilitator.payai.network | 2026-10-26 |
| Provider | Provider claim |
x402-catalog-history.ai-business-surface.workers.dev
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
facilitator.payai.network | 2026-10-26 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.
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...
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...
Solana token price and liquidity before you swap: one cheap per-mint market-data call returning the live price and liquidity depth, sourced from Jupiter and Helius. The pre-trade numbers when you do not need the full due...
Solana wallet risk screen via x402 (quick flag): service/router quarantine, bundler-routing hint, identity when covered, coverage and cached freshness. Low-cost first check before forensics, lineage or PnL. Not a live sc...
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.