What 0x JumpStart Gives a Startup
0x JumpStart gives Web3 startups up to $5,000 in 0x API credits, covering the swap, gasless, cross-chain and trade analytics endpoints that sit between your app and on-chain liquidity.
The important detail is the denomination. This credit line is measured in API calls with a dollar value attached, and it comes with a lifted requests-per-second ceiling. For most teams the rate limit, not the dollar figure, is the thing that was actually blocking them.
Allocations are not uniform, and the terms move. AI Perks tracks what is current alongside $7.7M in credits across 194 companies.
What the 0x API Is Actually For
0x is trading infrastructure: you send it a token pair and an amount, and it returns a priced, routed, ready-to-sign transaction that settles against the best available on-chain liquidity.
Any product that moves one token into another needs this layer. Wallets, trading apps, treasury tools, payment rails that settle in a stablecoin, on-chain agents that rebalance a position. The alternative is integrating DEXes one by one and maintaining your own router.
Routing is easy to build once and expensive to maintain forever. New pools appear weekly, liquidity migrates between venues, gas estimation drifts, approval flows change, and every new chain restarts the work. 0x aggregates 370+ liquidity sources across 18 chains, with $200B+ in settled volume and 211M+ transactions processed as of its published figures.
The metric founders should look at first is not price improvement, it is revert rate. A quote that fails on-chain costs your user gas and costs you trust. 0x publishes a 4.4% revert rate, and any router you build yourself will start much worse than that.
How 0x Pricing Behaves at Scale
0x charges on two meters that move independently: a monthly API subscription tied to request volume and rate limits, and a separate on-chain swap fee taken from the trade itself.
Here is the publicly listed structure, accurate at the time of writing and subject to change:
| Meter | Public price | Who pays it | Scales with |
|---|---|---|---|
| Free tier | $0 | You | Request volume, hard RPS cap |
| Standard plan | $1,000 / month | You | Request volume, 5 requests per second |
| Enterprise plan | $2,500 / month | You | Negotiated, volume-based discounts |
| On-chain swap fee | 0.15% on select pairs | Your users, at settlement | Trade volume |
The second meter is the one that surprises people. The swap fee is charged on-chain during the transaction rather than billed to your card, so it never appears on an invoice and never shows up in your burn rate. It scales with the value flowing through your app, not with your engineering.
This split matters for credits. A $5,000 credit line offsets the subscription and quota meter. It does not turn the on-chain fee off. Teams that model credits as a fee holiday build a unit economics deck that breaks the first month volume arrives. AI Perks lists what each program actually offsets, which is the part that decides whether a credit is worth applying for.
Why API-Call Credits Behave Differently From Dollar Credits
Credits denominated in API calls are consumed by your interface design, not by your revenue.
A cloud credit burns when you run compute. A swap API credit burns every time you display a price. Those are not the same trigger.
Three patterns quietly drain call volume:
Live price displays. A UI that refreshes a quote every few seconds while a user stares at the screen can generate fifty quote calls for every fill.
Portfolio and dashboard views. Every token row on a balance screen is a price lookup, multiplied by every session.
Agents and bots. Polling loops consume calls at a fixed rate whether or not the strategy trades.
Instrument your quote-to-fill ratio before you commit to a plan. It is the single number that tells you which plan you will need in six months, and most teams have never measured it. Track it alongside the other infrastructure meters you are funding through getaiperks.com.
What 0x Credits Stack With
Swap API credits cover one layer of a Web3 stack. On their own they leave the two bills either side of them untouched.
A typical on-chain product pays for three things at once:
- Node and RPC access. 0x returns you a transaction, it does not read chain state for you. Reads, receipts and event subscriptions stay on your RPC provider's bill.
- Cloud and compute. Indexers, webhook handlers and job queues run somewhere.
- AI model calls, if the product has an agent, a research feature or a natural language trading interface layered on top.
Credits exist for all three layers, and they are granted by different companies with different criteria, which is precisely why stacking works. Covering one layer and paying full price for the other two is how most first-year budgets quietly leak.
The practical move is to treat the three layers as one budget line rather than three unrelated ones. Covering a single layer is what makes a credit grant feel smaller than it looked on paper. AI Perks exists to show which combinations are available and compatible.
What Founders Get Wrong About Swap API Credits
The most common mistake is chasing credits before there is anything to spend them on.
A credit balance that lands before your integration is live mostly sits in an empty dashboard. The teams that get real value out of infrastructure credits are the ones whose meter is already running when the balance arrives, which usually means shipping something on the free tier first.
Four more that cost real money:
Treating slippage as a set-and-forget config. The cheapest quote that reverts is more expensive than the second cheapest that lands. Tune this against your own fill data, not a default.
Building the router first. Migrating to an aggregator later means rewriting your settlement path, which is the code with the least margin for error in the whole product.
Assuming multichain is free. Every additional chain multiplies quote calls before it adds a single user.
Ignoring the analytics endpoints. Trade data you already generate is usually sitting in an API you are already paying for, and teams rebuild it in a warehouse instead.
Program terms in this category move faster than in cloud or AI, so re-check what is current rather than trusting a screenshot from last quarter. AI Perks re-verifies listings continuously.
Frequently Asked Questions
How much is the 0x JumpStart program worth?
Up to $5,000 in 0x API credits, denominated in API calls with a lifted requests-per-second ceiling attached. The exact allocation is not uniform across companies. Current program terms, alongside $7.7M in credits from 194 companies, are tracked at getaiperks.com.
Do 0x credits remove the on-chain swap fee?
No. The published 0.15% fee on select token pairs is charged on-chain to your users at settlement, on a separate meter from your API subscription. Credits offset the subscription and request quota. Model the two independently or your unit economics will be wrong the month volume arrives.
Can I build on 0x without any credits?
Yes. There is a free tier intended for evaluation and early integration, which is the sensible place to start. Its rate limit is the usual reason teams move up to a paid plan, and hitting that ceiling is the clearest signal that a credit line would actually get used rather than sit idle.
What else should a Web3 startup apply for alongside this?
RPC and node providers, cloud infrastructure, and AI model credits if the product has an agent or research layer. These are separate bills granted by separate companies with different criteria, which is exactly why they stack rather than compete. See which combinations are currently live at getaiperks.com.
Is 0x worth it versus integrating DEXes directly?
For almost every team, yes. Direct integration is cheap to build once and expensive to maintain, because liquidity venues, gas behaviour and approval standards keep changing. Aggregation also buys you a low revert rate, which direct integrations take a long time to match.
How many chains does 0x support?
18 chains as published, including Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, Linea, Unichain and Monad. Coverage expands regularly, so verify against current documentation before planning a launch around a specific network.
Ship the swap. Let someone else fund the infrastructure under it.