The payout address is also published by 77 other service(s); the volume cannot be attributed to one of them.
Observed inflows by window for MealPulse.
Window
Observed
Transfers
Last complete day (2026-10-30)
—
—
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-01 → 2026-10-30Scanned: 30/30 daysSample: 0 days with a measurementFirst seen: neverLast update: 2026-10-30
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 MealPulse.
Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar
World Chain
0x50ab2018c06c6e4eaa9ba52057eb55ed284912fc
Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar
X Layer
0x50ab2018c06c6e4eaa9ba52057eb55ed284912fc
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.
One weather instrument's 247 rank: its place in its state today, reports due and received, timeliness, longest silence and its history. This call needs key, the instrument as net:<STATE>_<NETWORK>:<id>; the example below...
Weather forecast and air quality for any location worldwide. Returns current conditions plus a 16-day daily weather forecast - temperature highs and lows, precipitation, and wind - alongside air-quality readings includin...
Price a swap without building a transaction. Returns expected input, output, and gas without constructing an executable transaction. Quotes are informational and can change with liquidity and chain state.
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
7 routes
from the provider's payment requirements
Payment networks and amounts published for MealPulse.
Network
Scheme
Amount
Asset
Arbitrum
exact
0.08
USDC
Base
exact
0.08
USDC
Monad
exact
—
—
Polygon
exact
0.08
USDC
Solana
exact
0.08
USDC
World Chain
exact
—
—
X Layer
exact
—
—
“exact” is the price per call. “upto” is a ceiling the client sets, not a price.
Atomic amount 80000 = 0.08 USDC per call on Base. 7 payment options published.
{
"errors": {
"400": {
"description": "Invalid or missing parameter(s) \u2014 required: dietary. Returned before the payment gate on paid requests, so a malformed call is never charged. JSON body: { error: <what is wrong and how to fix it> } plus usage hints.",
"example": {
"error": "dietary parameter required"
}
},
"402": {
"description": "Payment required \u2014 x402 v2 challenge; the accepts array lists scheme, network, and amount. Retry the same request with a PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header. Verification is free."
},
"500": {
"description": "Unexpected server error. If a payment settled without a usable result, contact info@theaslangroupllc.com with the settlement tx hash for a re-run or credit.",
"example": {
"error": "upstream_failed"
}
}
},
"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 77 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-24
Usage
2 calls
· 2 unique payers
in the 30 days before 2026-10-24.
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 77 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.16 — 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 77 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.
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.