The payout address is also published by 105 other service(s); the volume cannot be attributed to one of them.
Observed inflows by window for Facilitator directory.
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-28Scanned: 30/30 daysSample: 0 days with a measurementFirst seen: neverLast update: 2026-10-28
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 Facilitator directory.
Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar
Sending wallets · observed counterparties
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
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.
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...
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...
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...
Examples are the provider's own, not a call we made.
Opportunity insights
2 findings from measured data
Payment attribution is blocked
The payout address is shared with 105 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.
Not checked by us yet — the data is as the source published it
First seen
2026-10-27
Usage
1 calls
· 1 unique payers
in the 30 days before 2026-10-27.
Measured by the x402 Bazaar, not by us and not by the provider.
Money, and what it actually proves
Verified revenue · 30dUnknown
Observed inflows · 30d—
AttributionShared
Receipt ledgerNot connected
Attribution blocked· confidence low
The payout address is also published by 105 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
an activity value of $0.10 — the source's call count
multiplied by the published price. That is what the list price implies, not what anyone paid.
The payout address is also published by 105 other service(s); the volume cannot be attributed to one of them.
Daily market statistics — the ledger view, day by day
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.
1 rail: Base · payee 0xf47b7e5912Fd4218aC4c992Cdc6FAE04e1fF512E
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.