The payout address is also published by 11553 other service(s); the volume cannot be attributed to one of them.
Observed inflows by window for wikidata-entity.
Window
Observed
Transfers
Last complete day (2026-10-31)
—
—
Last 7 days
—
—
Last 30 days
—
—
Growth, 7d against the 7 before
not comparable
Source: on-chain transfer scan (USDC on Base)Window: 2026-10-02 → 2026-10-31Scanned: 30/30 daysSample: 0 days with a measurementFirst seen: neverLast 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 wikidata-entity.
Shared address · activity cannot be assigned to this serviceFrom source record · source: payai
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.
$0.01/screen. Screen any name against OFAC, EU, and UK sanctions (UN included) plus Wikidata-derived PEP watchlists — fuzzy matching, instant JSON verdict. Compliance in one call, one of 155 Relaystation tools on one bal...
Send a reply in an existing LinkedIn conversation through a human-connected account that granted `reply`. Flat price per message. Requires an Idempotency-Key header. Per-account daily cap (default 50) shared across all c...
List the US recalls of consumer products, food, drugs or medical devices that match a product name, a manufacturer or, for consumer products, a recall title.
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 11553 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.
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 · 30dUnknown
Observed inflows · 30d—
AttributionShared
Receipt ledgerNot connected
Attribution blocked· confidence low
The payout address is also published by 11553 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 11553 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 0xFC24FD34da9e49A0110DCaEe3Ad30eC54175eBB3
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.