MARKET MONITOR / CATALOGUE Services 133,919 MCP listed 40,872 x402 93,128 Rails Base / Solana / Polygon / Arbitrum Imported 2026-11-01 · 3 sources
← All services

Daily transfers, volume and coverage →

NodeFlare

x402 resource x402 REST

rpc.nodeflare.app · rpc.nodeflare.app · Crypto & Payments

Base RPC (chain 8453): JSON-RPC over HTTPS on NodeFlare's own bare-metal nodes. Pay per request in USDC, no account or API key - built for AI agents. All methods including eth_getLogs, eth_call, trace, and debug (archive) - good for indexing, event queries, and simulation. Simple calls $0.001; heavy

Price per call 0.001 USDC per call published unit: per call
Calls · 30d 177 counted by the source, no daily split
Payers · 30d 16 distinct paying addresses seen by the source
Observed inflows · 30d $0.654 625 transfers to the payout address
Inflow growth · 7d — not comparable (baseline under $1 or window incomplete)
Payment evidence Observed transfers confidence: medium · read 2026-11-01

Observed inflows · last 30 days

$0.24USD observed / day
2026-10-02grey = not scanned · UTC days2026-10-31
Observed inflows by window for NodeFlare.
Window Observed Transfers
Last complete day (2026-10-31) $0.004 4
Last 7 days $0.295 284
Last 30 days $0.654 625
Growth, 7d against the 7 before not comparable
Source: on-chain transfer scan (USDC on Base) Window: 2026-10-02 → 2026-10-31 Scanned: 30/30 days Sample: 30 days with a measurement First seen: 2026-10-02 Last update: 2026-10-31

Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.

Blockchain wallets

Full addresses · public payment evidence

Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.

Receiving wallets · provider payment addresses

All published receiving wallet addresses for NodeFlare.
NetworkFull wallet addressEvidence
Arbitrum 0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296 Exclusive to this catalogue serviceFrom source record · source: x402_bazaar
Base 0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296 Exclusive to this catalogue serviceFrom source record · source: x402_bazaar
Polygon 0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296 Exclusive to this catalogue serviceFrom source record · source: x402_bazaar

Sending wallets · observed counterparties

All 10 retained sending addresses are listed below. Source: on-chain transfer scans. Dates are UTC days.

All retained sending wallet addresses observed for NodeFlare.
NetworkFull wallet addressTransfersFirst / last observedLast scanned (UTC)
Base 0x35fe83e85f949b7235595a76782296c6c9c3c030 1 2026-10-29 / 2026-10-29 2026-10-30 23:38:16
Base 0x645e38d1951047edbf045e0da64344536dceca76 1 2026-10-31 / 2026-10-31 2026-11-01 00:36:50
Base 0x73cc9400bd9f086d7427d3421d79195a68bb1ea4 2 2026-10-29 / 2026-10-30 2026-10-31 23:38:42
Base 0x8ec901f7e2710163387d70950f680f1ea2269d15 2 2026-10-30 / 2026-10-30 2026-10-31 23:38:42
Base 0x99d030970b404d9e22063a479a91eb8366ae6506 1 2026-10-28 / 2026-10-28 2026-10-29 23:38:15
Base 0xa1d1c0cf717402ff3651aa4873ccf96410b01978 1 2026-10-28 / 2026-10-28 2026-10-29 23:38:15
Base 0xa22b360f177e5ef68405b74141479b8309618acc 1 2026-10-28 / 2026-10-28 2026-10-29 23:38:15
Base 0xaa34bd941511cc82a19878e2efbe0bd7077e1db3 1 2026-10-30 / 2026-10-30 2026-10-31 23:38:42
Base 0xc4e64a4e5617052e6e2a1a8a565915a1875f47b6 1 2026-10-30 / 2026-10-30 2026-10-31 23:38:42
Base 0xc9c7b38c0942914fc8ea12063bc92dcd3b581670 3 2026-10-31 / 2026-10-31 2026-11-01 00:36:50

Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.

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 31,075 services in this category
With a measured call count 26,541 (85.4 %)
With a published price 28,857 (92.9 %)
With attributable inflows 297 (1.0 %)
Observed inflows · 30d $626,743.28
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,843 calls / 30d checked 2026-10-31
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,252 calls / 30d checked 2026-11-01
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,672 calls / 30d checked 2026-11-01
0.01 USDC per call per call

Tech Detect x402 REST usage

One HTTP request per host, matched against an in-house signature set. Every hit carries a confidence value from 0 to 100 and the evidence it rests on: response header, asset path, cookie name, meta generator, DNS or ASN...

stack.netzhandwerker.de Crypto & Payments 683 calls / 30d checked 2026-10-31
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.

Service details, payment routes and source evidence

Where you can pay

6 routes from the provider's payment requirements
Payment networks and amounts published for NodeFlare.
Network Scheme Amount Asset
Arbitrum exact 0.001 USDC
Arbitrum upto up to 0.1 USDC
Base exact 0.001 USDC
Base upto up to 0.1 USDC
Polygon exact 0.001 USDC
Polygon upto up to 0.1 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 1000 = 0.001 USDC per call on Base. 6 payment options published.

What you can call

access: payment per call (x402)

endpoint https://rpc.nodeflare.app/base/x402

Request

{
    "body": {
        "id": 1,
        "jsonrpc": "2.0",
        "method": "eth_blockNumber",
        "params": []
    },
    "bodyType": "json",
    "method": "POST",
    "type": "http"
}

Response

{
    "example": {
        "id": 1,
        "jsonrpc": "2.0",
        "result": "0x1a2b3c"
    },
    "type": "json"
}

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

Opportunity insights

2 findings from measured data
  • Call count and inflow disagree

    The observed inflow implies about 654 calls at list price; the source counted 177 (factor 4). Either the effective price differs from the list price, or part of the volume belongs to other payers on the same address. Do not read the inflow as this service's revenue.

    Peers with attributed inflows →
  • Category benchmark

    297 of 31,075 services (1.0%) in Crypto & Payments have attributable inflows; 26,541 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

Base RPC (chain 8453): JSON-RPC over HTTPS on NodeFlare's own bare-metal nodes. Pay per request in USDC, no account or API key - built for AI agents. All methods including eth_getLogs, eth_call, trace, and debug (archive) - good for indexing, event queries, and simulation. Simple calls $0.001; heavy calls priced by compute units.

Quoted from x402 Bazaar · source record · read 2026-11-01


Facts and where they come from

Price
0.001 USDC per call Provider claim
Recorded value: 0.001 USDC per call.
Unit
per call
Protocol
x402, REST · transport: HTTP Provider claim
Auth
x402
Source
x402 Bazaar (Coinbase CDP) · 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-24
Usage
177 calls · 16 unique payers in the 30 days before 2026-10-31. Measured by the x402 Bazaar, not by us and not by the provider.

Money, and what it actually proves

Verified revenue · 30d Unknown
Observed inflows · 30d $0.654
Attribution Exclusive
Receipt ledger Not connected

Observed transfers · confidence medium
Token transfers reached this service's own payout address. A transfer is not a purchase, and shared, refunded or unrelated transfers cannot be excluded.

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 $0.654 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.

Cross-check. At the published price the observed inflow would cover about 654 calls; the source counted 177. Two independent measurements of the same question — they never match exactly, because the effective price differs per call size and the address can also receive unrelated transfers.

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

Arbitrum · upto · USDC
0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
0.1 USDC
From source record
Base · exact · USDC
0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
0.001 USDC
From source record
Polygon · exact · USDC
0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
0.001 USDC
From source record
Arbitrum · exact · USDC
0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
0.001 USDC
From source record
Base · upto · USDC
0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
0.1 USDC
From source record
Polygon · upto · USDC
0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
0.1 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.

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://rpc.nodeflare.app/bob/x402
Evidence

Als Resource-URL im Bazaar-Eintrag geführt.

api.cdp.coinbase.com 2026-11-01
Input output Provider claim
Request/response examples published with the listing
Evidence

Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.

api.cdp.coinbase.com 2026-11-01
Payment Provider claim
6 rails: Base, Polygon, Arbitrum · payee 0x9d86e0e74333b297b1d0b6ba30d2ed1b5f01f296
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.

api.cdp.coinbase.com 2026-11-01
Pricing Provider claim
0.001 USDC per call
Evidence

Atomic amount 1000 = 0.001 USDC per call on Base. 6 payment options published. Netzwerk: Base, Polygon, Arbitrum.

api.cdp.coinbase.com 2026-11-01
Protocol Provider claim
x402 (HTTP 402 payment challenge)
Evidence

Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).

api.cdp.coinbase.com 2026-11-01
Provider Provider claim
rpc.nodeflare.app
Evidence

Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.

api.cdp.coinbase.com 2026-11-01
Usage Verified
3 calls / 3 unique payers in the last 30 days
Evidence

Source-reported usage from Coinbase x402 Bazaar, read on 2026-11-01. Letzter Aufruf laut Quelle: 2026-10-21T23:09:27.612Z. Aufrufe sind kein Umsatz.

api.cdp.coinbase.com 2026-11-01

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags