What the provider says
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.
Quoted from PayAI
· source record
· read 2026-10-29
Facts and where they come from
- Price
-
0.02 USDC per call
Provider claim
Recorded value: 0.02 USDC per call.
- Unit
- per call
- Protocol
-
x402, REST
· transport: HTTP
Provider claim
- Auth
- x402
- Source
-
PayAI
· Public discovery API (provider-published records)
- Last checked
-
Not checked by us yet — the data is as the source published it
- First seen
- 2026-10-26
Money, and what it actually proves
Verified revenue · 30d
Unknown
Observed inflows · 30d
—
Attribution
Shared
Receipt ledger
Not connected
Attribution blocked
· confidence low
The payout address is also published by 41 other service(s); the volume cannot be attributed to one of them.
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
nothing measurable: no price, no attributable address, no receipt.
The payout address is also published by 41 other service(s); the volume cannot be attributed to one of them.
Daily market statistics — the ledger view, day by day
No daily history has been archived for this service yet. Open the full daily history →
Payment rails
Base
· exact · USDC
0x6f60659390aDA1D02B14024d8c9d0C889f2F89c3
0.02 USDC
From source record
A payment rail is where the provider asks to be paid. It is not proof that anything was paid
through it. See evidence levels.
Provenance
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/contract
Evidence
Als Resource-URL im Bazaar-Eintrag geführt.
|
facilitator.payai.network
|
2026-10-29 |
|
Input output
|
Provider claim |
Request/response examples published with the listing
Evidence
Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.
|
facilitator.payai.network
|
2026-10-29 |
|
Payment
|
Provider claim |
1 rail: Base · payee 0x6f60659390aDA1D02B14024d8c9d0C889f2F89c3
Evidence
Aus 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-29 |
|
Pricing
|
Provider claim |
0.02 USDC per call
Evidence
Atomic amount 20000 = 0.02 USDC per call on Base. Netzwerk: Base.
|
facilitator.payai.network
|
2026-10-29 |
|
Protocol
|
Provider claim |
x402 (HTTP 402 payment challenge)
Evidence
Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).
|
facilitator.payai.network
|
2026-10-29 |
|
Provider
|
Provider claim |
x402-catalog-history.ai-business-surface.workers.dev
Evidence
Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.
|
facilitator.payai.network
|
2026-10-29 |
Endpoint checks
We have not called this endpoint yet. Until we do, everything above is what the source
published — no more.
Tags