Parse and classify an IPv4/IPv6 address (private, loopback, CGNAT, documentation, ...). Canonical and expanded forms, integer and hex values, version, scope per the IANA special-purpose registries (private, loopback, link-local, CGNAT, multicast, documentation, 6to4, NAT64, IPv4-mapped with the embe
Price—
no price published
Calls · 30d—not reported by any source
Payers · 30d—
not reported by any 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 Swift Bot Labs Toolbox.
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 Swift Bot Labs Toolbox.
Network
Full wallet address
Evidence
Base Sepolia
0x2481e29895b43e87e547a50fb0bb5aa1e70585eb
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.
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...
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.
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...
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
1 route
from the provider's payment requirements
Payment networks and amounts published for Swift Bot Labs Toolbox.
Network
Scheme
Amount
Asset
Base Sepolia
exact
—
—
“exact” is the price per call. “upto” is a ceiling the client sets, not a price.
Raw amount 3000 of asset 0x036CbD53842c5426634e7929541eC2318f3dCF7e — unit not resolvable, so no price is shown.
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.
Parse and classify an IPv4/IPv6 address (private, loopback, CGNAT, documentation, ...). Canonical and expanded forms, integer and hex values, version, scope per the IANA special-purpose registries (private, loopback, link-local, CGNAT, multicast, documentation, 6to4, NAT64, IPv4-mapped with the embedded address), whether it is globally routable, and the reverse-DNS name.
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-27
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
nothing measurable: no price, no attributable address, no receipt.
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 Sepolia · payee 0x2481E29895b43e87e547a50fB0BB5aa1E70585EB
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.