MARKET MONITOR / CATALOGUE Services 131,105 MCP listed 40,658 x402 90,514 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-29 · 3 sources
← All services

Daily transfers, volume and coverage →

Contract

x402 resource x402 REST

x402-catalog-history.ai-business-surface.workers.dev · x402-catalog-history.ai-business-surface.workers.dev · Crypto & Payments

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.examp

Price per call 0.02 USDC per call published unit: per call
Calls · 30d — not reported by any source
Payers · 30d — not reported by any source
Observed inflows · 30d — not attributable
Inflow growth · 7d — not comparable (baseline under $1 or window incomplete)
Payment evidence Attribution blocked confidence: low · read 2026-10-29

Where you can pay

1 route from the provider's payment requirements
Payment networks and amounts published for Contract.
Network Scheme Amount Asset
Base exact 0.02 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 20000 = 0.02 USDC per call on Base.

What you can call

access: payment per call (x402)

endpoint https://x402-catalog-history.ai-business-surface.workers.dev/contract

Request

{
    "type": "http",
    "method": "GET",
    "queryParams": {
        "url": "https://x402-catalog-history.ai-business-surface.workers.dev/history"
    }
}

Response

{
    "type": "json",
    "example": {
        "mime": "application/json",
        "output": {
            "fields": [
                {
                    "name": "url",
                    "type": "string",
                    "example": "https://x402-catalog-history.ai-business-surface.workers.dev/history",
                    "required": true
                }
            ],
            "example": null,
            "declared": true,
            "fields_from": "properties",
            "declared_keys": [
                "properties",
                "required",
                "type"
            ],
            "properties_empty": false,
            "schema_only_type_example": false
        },
        "sha256": "0000000000000000000000000000000000000000000000000000000000000000",
        "target": {
            "url": "https://x402-catalog-history.ai-business-surface.workers.dev/history",
            "host": "x402-catalog-history.ai-business-surface.workers.dev",
            "path": "/history"
        },
        "weakness": [
            {
                "code": "error_shape_undeclared",
                "detail": "No error/failure shape is declared: what a failed paid call returns cannot be read from the 402."
            }
        ],
        "fetched_at": "2026-10-16T00:00:00.000Z",
        "product_id": "x402-output-contract",
        "x402Version": 2,
        "error_shape_declared": false
    }
}

Examples are the provider's own, not a call we made.

Observed inflows · last 30 days

No inflow observed in this window

The payout address is also published by 41 other service(s); the volume cannot be attributed to one of them.

Observed inflows by window for Contract.
Window Observed Transfers
Last complete day (2026-10-28) — —
Last 7 days — —
Last 30 days — —
Growth, 7d against the 7 before not comparable
Source: on-chain transfer scan (USDC on Base) Window: 2026-09-29 → 2026-10-28 Scanned: 30/30 days Sample: 0 days with a transfer First seen: never Last update: 2026-10-28

Daily history → · what a transfer does and does not prove

Opportunity insights

2 findings from measured data
  • Payment attribution is blocked

    The payout address is shared with 41 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.

    How attribution works →
  • Category benchmark

    287 of 30,055 services (1.0%) in Crypto & Payments have attributable inflows; 25,633 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

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


Competitors & category benchmark

Rank the whole category →
Closest competitors Crypto & Payments

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.

Category benchmark 30,055 services in this category
With a measured call count 25,633 (85.3 %)
With a published price 27,842 (92.6 %)
With attributable inflows 287 (1.0 %)
Observed inflows · 30d $639,332.76
Median measured calls 2
Median price per call $0.01

Similar services

All of Crypto & Payments →

Agents Trust API Search x402 REST usage

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...

api.agents-trust.com Crypto & Payments 12,306 calls / 30d checked 2026-10-29
0.01 USDC per call per call

X Pay x402 REST usage

Payment quote with amount, asset, and merchant wallet

www.api-xpay.com Crypto & Payments 7,233 calls / 30d checked 2026-10-29
0.005 USDC per call per call

Gondola x402 REST usage

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...

api.gondola-ai.com Crypto & Payments 4,666 calls / 30d checked 2026-10-29
0.01 USDC per call per call

Scry Wallet Intelligence x402 REST usage

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...

scry.solanahub.de Crypto & Payments 785 calls / 30d checked 2026-10-29
0.005 USDC per call per call

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.