Data that software can buy on its own

WhaleTape sells Hyperliquid market data one request at a time, paid in USDC over the x402 protocol. No account, no API key, no subscription. The customers it is built for are programs, and a program cannot sign up for anything.

The problem

Every market data provider gates access behind the same wall: create an account, verify identity, pick a monthly plan, receive an API key. That wall assumes a human with a credit card and a company behind them.

An autonomous agent has none of those things. It cannot open an account or agree to terms. But it can pay. And if a service needs to be consulted once, a monthly subscription is the wrong shape for the transaction anyway.

How a paid request works

The caller asksAny client requests an endpoint. No credentials are needed or offered.

The server quotes a priceIt answers 402 Payment Required, a status code defined in 1997 and left unused ever since, carrying machine-readable payment terms.

The caller pays and retriesPayment settles in USDC. The request repeats with proof attached.

The data is returnedTypically within a second of the first attempt. Nothing was stored about the buyer.

Also payable on Algorand

The same catalogue is sold in USDC on Algorand under the /algo prefix, at the same prices: GET https://whaletape.xyz/algo/coverage instead of GET https://whaletape.xyz/coverage. Settlement runs through the GoPlausible facilitator and transaction fees are sponsored, so a buyer needs nothing but USDC. The machine-readable list of all 27 routes is at /algo/.well-known/x402.

What is for sale

Market data across roughly 320 Hyperliquid perpetual markets covering cryptocurrencies, equities, commodities, foreign exchange and indices: prices, funding rates, open interest, 24-hour volume, whale positioning, squeeze indicators and liquidation maps. Prices run from $0.001 to $0.99 per request depending on the endpoint.

Where it stands today

Every number in this section is read from /metrics when the page loads. Nothing here is written by hand, so nothing here can go stale without the service going stale with it. The window is whatever the service has actually measured, and it is printed below.

402 quotes served
over the measured window
x402 callers
software that speaks the protocol
Settled payments
our own wallets excluded
Distinct payers
external wallets that paid

Who is on the other end

Counting requests flatters the picture, because one crawler generates thousands of them. This is the same breakdown the service publishes for itself, by client class:

Caller type402 quotesWhat it is

Most of that is background noise. The number worth watching is the small one at the end: the callers that actually settle. That is what early looks like, and it is printed here rather than dressed up. The same figures, with every transaction hash, are on the metrics page.

The standard behind it

x402 is not a WhaleTape invention. It is an open payment standard released by Coinbase and now governed by the x402 Foundation under the Linux Foundation, formalised in April 2026. Its membership includes the institutions that run global payments:

VisaMastercardAmerican ExpressStripe AdyenFiservGoogleMicrosoft Amazon Web ServicesShopifyCircleCloudflare
Transactions settled
157M
cumulative across the protocol
Stablecoin volume
$41M
cumulative
Active agents
69,000
reported by Coinbase
Networks
7
18 tracked facilitators

Those headline figures deserve a caveat that is rarely printed alongside them: independent analysis suggests roughly half of that activity is incentive-driven rather than genuine purchasing, with real daily volume across the whole protocol in the order of $28,000. Machine-payable commerce is real, early, and small. WhaleTape is building for where it goes, not for where it is.

Why euros may matter next

x402 is a protocol, not a currency. It defines how a server asks for payment and how a client proves it paid; what settles the transaction is a separate layer. Today that layer is USDC, because that is what is liquid.

The European Central Bank is building a digital euro, and its innovation platform has been testing conditional payments with more than 70 banks, fintechs and merchants. That is the same capability this kind of protocol depends on.

OCTOBER 2025
Preparation phase closed. The ECB moved to building technical capacity.
DURING 2026
Regulation before the co-legislators. The working assumption is adoption within the year.
2029
Possible first issuance. Subject to the legislation landing.

If a digital euro ships with programmable payment capability, the same per-request model could settle in euro rather than a dollar stablecoin, inside the EU regulatory perimeter, with central bank money. That is a possibility rather than a plan: no such capability exists yet, and no timetable is confirmed. It is noted because it suggests this technique is not confined to crypto markets.

Where else this fits

Per-request payment solves one narrow problem: charging a very small amount to someone who will not open an account. That problem shows up in a lot of places.

Data and API access One query instead of a monthly plan. what WhaleTape does
Agents buying services An agent pays for a search, a translation or a dataset without a human issuing it a key.
Metered computation Charging for a single inference or unit of processing, with no account provisioned in advance.
Journalism and publishing Paying for one article without subscribing, long blocked by card fees larger than the article's price.
Machines settling with machines Vehicle charging, tolls, metered utilities, sensor data.
Research and archives Access to a single paper or record without an institutional subscription.

The common obstacle is that conventional card payments carry a fixed fee and a chargeback window, which together make a two-cent transaction impossible. Removing that constraint is the whole point.

Support the project

Why it helps

WhaleTape runs on a single free-tier virtual machine and costs almost nothing to operate, which is why it can charge a cent a request and mean it. Support goes toward what free tiers cannot cover: historical data storage, wider market coverage, and settlement on additional networks so more agents can pay in whatever they already hold.

There is no reward, no token, and nothing to claim. The API is the product, and it is already live and priced. This is simply a way to help if the work seems worth continuing.

USDC on Base

0x25a8b697Da5c0bAF698Fd6BD9701B5e825214145
NETWORK · BASE ASSET · USDC SAME ADDRESS THE API SETTLES TO

Send only USDC on Base to this address. Assets sent on another network may be unrecoverable.