x402-catalog-history.ai-business-surface.workers.dev
https://x402-catalog-history.ai-business-surface.workers.dev/contractShares a payout wallet with 41 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
This 402 — can you tell what it returns from the type alone? Ask for any x402 URL and one GET normalises the output contract the seller actually declared into field names, types and required flags, so you can decide before you pay whether you can bind to it. curl: GET /contract?url=https://api.example.com/paid (a free sample is GET /contract/sample?url=…, and /contract/sample with no url shows this service's own /history). Response: {url, x402Version, mime, output:{fields:[{name,type,required,example}], declared, schema_only_type_example, properties_empty}, error_shape_declared, weakness:[...], fetched_at, sha256}. measured 2026-10-16 over 2433 observed x402 resources: 100% declare an output schema and 87.8% declare nothing in it but {type, example} (type 2135, example 2137); 288 declare an empty properties object; only a dozen or so name any field at all. That is the gap this report closes: it says field by field what the paid 200 will contain, or says declared:false and lists the weakness instead of inventing a shape. Failure is reported with the code, not a guess: 400 invalid_url / blocked_target / credentials_not_allowed and missing_url before anything is fetched and before any payment; 502 unreachable / timeout / too_many_redirects when the target could not be read, and 200 with declared:false when it answered but serves no readable x402 challenge (a non-x402 route is not an error, it is a finding). The target is read once with no payment header, with a 5-second timeout, at most 3 redirects and a 64 KB body cutoff, exactly as a buyer would see it. No keys, no account, one GET, one delivery — 0.02 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 11ms · p95 14msData 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 | 11ms |
| 11/16/2026, 9:00:00 PM | 100% | 1 | 14ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- 1
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 50% — 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"
}