x402-catalog-history.ai-business-surface.workers.dev
https://x402-catalog-history.ai-business-surface.workers.dev/json-canonicalShares a payout wallet with 41 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
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.
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 8ms · p95 11msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 11/12/2026, 8:00:00 AM | 100% | 1 | 11ms |
| 11/14/2026, 8:00:00 PM | 100% | 1 | 7ms |
| 11/16/2026, 9:00:00 PM | 100% | 1 | 8ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- 0
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 48% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- self-hosted
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- CloudFlare, Inc.
- Domain registered
- 2019-02-08
- Hosting network
- CLOUDFLARENET
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 11/15/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 10/21/2026 | 4 | 0.03 | 3 |
| 10/22/2026 | 3 | 0.03 | 2 |
| 10/23/2026 | 3 | 0.02 | 2 |
| 10/25/2026 | 1 | 0.01 | 1 |
| 10/26/2026 | 2 | 0.01 | 2 |
| 10/27/2026 | 2 | 0.02 | 1 |
| 10/28/2026 | 1 | 0.01 | 1 |
| 10/30/2026 | 1 | 0 | 1 |
| 11/1/2026 | 1 | 0.01 | 1 |
| 11/9/2026 | 10 | 0.1 | 1 |
| 11/10/2026 | 10 | 0.1 | 1 |
| 11/15/2026 | 1 | 0 | 1 |
This payout wallet is shared: figures cover all 42 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"additionalProperties": true,
"description": "One delivery: the paid payload plus the period, coverage and evidence fields this service reports with it.",
"type": "object"
}