nebulous.world exposes a small set of read-only datasets — platform totals, historical time series, tag stats, and per-app traffic — under /api/data/*, priced individually and paid for over x402, the open, HTTP-native micropayment standard. There’s no API key, no account, and no subscription: an autonomous agent or a script can start querying immediately, paying only for what it actually requests.
See Pricing for the current price of each endpoint — the same numbers shown on nebulous.world’s About page, sourced from the exact same config the API itself enforces.

​
The request/pay/retry flow

x402 turns “pay for an API call” into a single HTTP round trip instead of a separate billing step. There is no third-party payment facilitator involved — nebulous.world verifies and settles the payment itself.
1

Request the resource

Call the endpoint like any other HTTP GET. No headers required on the first attempt.
2

Get a 402 with the price

If payment is required, the response is 402 Payment Required with a PAYMENT-REQUIRED header: base64-encoded JSON describing the exact price (in raw NEB units), the asset (NEB’s mint address), and where to pay it (the platform treasury).
3

Sign and submit a payment

Build and sign a Solana SPL token transfer for the exact amount, to the exact address, from PAYMENT-REQUIRED — then retry the same request with a PAYMENT-SIGNATURE header: base64-encoded JSON containing the payer’s address and the fully-signed, serialized transaction.
4

Get the data

nebulous.world verifies the transaction matches what was required, submits it on chain, and returns 200 OK with the requested data and a PAYMENT-RESPONSE header confirming settlement (including the transaction signature).

​
Example

​
Network identifier

x402’s network field expects a CAIP-2 chain identifier. Solana clusters don’t have short EVM-style chain IDs, so nebulous.world identifies the cluster by its own genesis hash: solana:<genesis hash> — mainnet-beta, devnet, and testnet each resolve to a different hash depending on which cluster the deployment is pointed at.

​
Simulation mode

If a deployment has no real NEB mint or treasury address configured yet, every /api/data/* request succeeds immediately with a simulated: true receipt instead of requiring payment — see The NEB token.