Skip to main content
Pass your raw API key in the Authorization header on every request (same convention as Mobula, zero migration friction). No Bearer prefix: the header value is the key itself.

Get a key

1

Create an account

Sign up at serialized.xyz/signup with an email and password, Google or GitHub.
2

Add a card, unlock 100,000 free credits

In Billing, add a payment method. Nothing is charged today: the card unlocks your 100,000 free credits.
3

Create your keys

In API keys, create up to 5 active keys, one per app or environment. Store each key as a secret. Copy, rename, rotate or revoke it at any time from the same page.
Usage, invoices, your plan and your spend cap live in the portal at serialized.xyz/portal.

Try it instantly

Every endpoint page has an interactive playground. The market endpoints (token details, price, stats, metadata, pools, candles, trades, search, screener, pulse, markets, native prices, chains, factories) run live against https://demo.serialized.xyz with no key, rate-limited per IP: fill the parameters and send. For the others (wallets, holders, top traders, security, audit, every batch) and to test with your own key, switch the server to https://api.serialized.xyz and paste your key in the Authorization field.

Pricing

How Growth is billed, plan changes and a worked example: Plans.
  • Billed monthly for what you use. Usage is billed per period between two reset dates: every month from the moment you subscribed, started Growth or moved up a tier (the 1st of each month for a pay as you go subscription started before October 16, 2026). Your card is charged as usage accrues, then for the balance on your reset date. On Growth, the fee is charged in advance when your plan starts and on each reset date, and usage beyond the included credits is billed this way. Starting Growth and moving up a tier happen right away; moving down a tier or going back to pay as you go takes effect on your next reset date. Invoices and receipts are in Billing.
  • Free credits are granted once per account and carry over from month to month until they are used. On Growth, they come on top of your included credits and are used after them.
  • Monthly spend cap. Every account has a spend cap, $10,000 per month by default. Set your own in Billing, from $0 to $100,000. On Growth, it applies to usage beyond your included credits; the plan fee is not counted. Reaching it pauses billable calls until you raise it or your next reset date.
  • Custom: Enterprise volume pricing for high volume, dedicated limits, custom endpoints or chains. Talk to us.

Credits

An endpoint costs 1 credit unless it is listed here: POST batch endpoints are priced below. Price webhooks bill 1 credit per trigger sent to your URL (when its first delivery attempt goes out, retries included), never for managing them. Streams bill per message delivered: 1 credit per message on the live views, 1 credit per element with on-chain activity in each message on the other channels (see WebSocket). Only successful (2xx) responses are billed: you never pay for your own 4xx, for auth, billing or rate-limit rejections, or for a 5xx on our side. The full grid is also in the portal, under “What a call costs”. Every billable response carries X-Credits-Remaining: the credits your account can use right now, shared by all the keys of the account. It counts your free credits left (pay as you go) or your included credits left (Growth), plus your current billing allowance, which grows each time a usage payment goes through, up to your monthly spend cap.

Batches

POST batches are billed by tranche: each tranche of items served costs one call of the endpoint.
  • Tranches: up to one tranche of items is billed as one call of the endpoint, two tranches as two calls, and so on. 25 prices cost 1 credit and 100 prices cost 4; 25 token details cost 2, as do 25 tokens of stats; 100 markets of pool data cost 8; 2 security checks cost 10 credits, the price of one; 20 wallets of PnL cost 8; 10 candle series cost 10.
  • Wallet batches (wallet positions, closed positions, wallet trades and swaps): each wallet is billed at the endpoint’s price.
  • Wallet batches count wallets, not chains: the same address requested on several chains counts as one wallet.
  • Token details with windows: the windows are included in the price of the token details, on a single call and on a batch.
  • Token details with include=security: 2 more credits per call, on a single call and on a batch alike, when at least one tokenSecurity block is served: 25 token details with their security block cost 4 credits.
  • Wallet PnL with include=portfolio: 2 more credits per wallet whose portfolio block is served. A single call costs 4 credits; in a batch the option adds to the tranches, and a wallet is counted as the batch counts it: 20 wallets with their block cost 8 + 40 = 48 credits.
  • POST /v1/token/trades is not a batch: it filters the tape of one token and is billed as one call.
Only the items served are billed. An item that comes back as an { error } slot (unknown token, malformed address, a failure on our side) costs nothing, and a batch where every item fails still answers 200 and costs 0 credits. The tranche counts the items served: 30 prices with 6 unknown tokens are 24 items served, 1 credit.

Rate limits

The limit is per key, on a 1-minute window, with a per-second burst cap so a full minute’s budget cannot land in a single second. Standard X-RateLimit-* headers are on every response; exceeding a limit returns 429 with code RATE_LIMITED and a Retry-After header. Against the per-minute limit and the burst cap, a batch call counts as one request; batch items have their own per-second allowance of 10 × the burst cap. Against the group caps below, a batch counts one per item, a wallet PnL asked with include=portfolio counts 2 per wallet, and an all-time top traders ranking filtered by watchlist counts 4; a token holders page filtered by watchlist counts 1, whatever its limit. The limits are the same on pay as you go and Growth. A few endpoint groups carry their own per-key cap. The defaults below apply to every key and are raised on request: tell us your expected peak and we size the key. Every response of an endpoint in a group also carries the group’s own headers, next to the X-RateLimit-* headers of your per-minute limit: A 429 from a group cap carries details.group, and its Retry-After and X-RateLimit-* headers are those of the group cap. A call refused by a group cap uses nothing of it. Watchlist management and filtered token holders each have their own group: a call counts one, whatever the number of wallets it carries or the page size, and neither is limited by the Wallet group. Like every call, they also count against your per-minute limit and burst cap. In the Webhook group, adding triggers counts one per distinct token of the call (up to 100), or one per 10 triggers when that is more (up to 100), removing counts one per 100 ids, a page of triggers one per 100 rows asked (limit), any other call one.

Payment and quota responses

A billable call your account cannot pay for returns HTTP 402, with X-Credits-Remaining: 0 when the monthly allowance is reached. The body tells you why and what to do next:
error.code is PAYMENT_REQUIRED (the account needs a billing step) or QUOTA_EXCEEDED (the account reached its allowance for now). Branch on details.action, not on the message: the message is written for a human and may evolve. account_pending, verify_payment and payment_processing clear on their own: retry with a backoff (for example 30 seconds, then longer). The other actions need someone on your side to act in the portal: surface the message to your operators rather than retrying in a loop. A suspended account returns HTTP 403 with code FORBIDDEN (details.action = account_suspended). Contact hello@serialized.xyz. Zero-credit endpoints (including usage) stay reachable in every case, so you can always inspect your own state. Enterprise keys follow their contract: when a contracted monthly allowance is spent, billable endpoints return 402 QUOTA_EXCEEDED.

Usage introspection

Query your own consumption programmatically, at no credit cost, and a level of self-serve visibility no other provider exposes over the API:
  • GET /v1/usage: current month: { keyId, tenant, plan, month, scope, credits: { used, limit, remaining }, requests }. For keys created in the portal, scope is "account": the figures cover the whole account, all keys included.
  • GET /v1/usage/history: time series of requests and credits for the calling key, bucketed at 15m, 1h, 6h or 1d.
  • GET /v1/usage/breakdown: per endpoint for the calling key, stream channels included.
A key only ever sees its own account. The portal shows the same data across all your keys, with cost per endpoint and errors.

WebSocket

wss://ws.serialized.xyz/v1/stream. The first frame authenticates with your key. Close codes: On 4402, read the action from the close reason and handle it as in the table above; reconnect only once it is resolved. Streaming bills the messages you receive: 1 credit per message on the live views (pulse, pulse-pools, screener, screener-pools), and on every other channel 1 credit per element with on-chain activity in each message (a pool that traded, a token, a candle series, a wallet on one chain). The connection itself is free. Details in Streams billing. Per account: 100 concurrent connections and 200 subscriptions in total, raised on request. Every channel is open to every key. Details in the Streams overview.