FDA recall / enforcement reports (openFDA) for drugs, devices or food, searched by keyword across product, reason and firm, newest first: classification (Class I-III), status, firm, product, reason, distribution, dates. Not charged on errors.
Price per call0.02 USDC per call
published unit: per call
Calls · 30d2counted by the source, no daily split
Payers · 30d2
distinct paying addresses seen by the source
Observed inflows · 30d
—
not attributable
Inflow growth · 7d
—
not comparable (baseline under $1 or window incomplete)
The payout address is also published by 1 other service(s); the volume cannot be attributed to one of them.
Observed inflows by window for Recalls.
Window
Observed
Transfers
Last complete day (2026-10-29)
—
—
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-30 → 2026-10-29Scanned: 30/30 daysSample: 0 days with a measurementFirst seen: neverLast update: 2026-10-29
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 Recalls.
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.
$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.
{
"example": {
"q": "listeria",
"recalls": [
{
"classification": "Class I",
"distribution": "NY, NJ",
"product": "Lemon Alfredo Fettuccine\u2026",
"reason": "Products may be contaminated with Listeria monocytogenes.",
"recallInitiationDate": "20260904",
"recallNumber": "H-0014-2027",
"recallingFirm": "Example Foods Inc",
"reportDate": "20261021",
"status": "Ongoing"
}
],
"source": {
"disclaimer": "Do not rely on openFDA to make decisions regarding medical care...",
"license": "CC0",
"name": "openFDA"
},
"totalMatches": 7498,
"type": "food"
},
"type": "json"
}
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 1 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.
FDA recall / enforcement reports (openFDA) for drugs, devices or food, searched by keyword across product, reason and firm, newest first: classification (Class I-III), status, firm, product, reason, distribution, dates. Not charged on errors.
Quoted from x402 Bazaar
· source record
· read 2026-10-29
Not checked by us yet — the data is as the source published it
First seen
2026-10-29
Usage
2 calls
· 2 unique payers
in the 30 days before 2026-10-29.
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 1 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.04 — 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 1 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 0x94D642596761470161B37771FAC222111A5FfAd6
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.