BlackForge vs Laevitas
Updated
BlackForge and Laevitas are two of the small number of crypto data feeds an agent can pay for by the call, with no account and no key, over the x402 rail. That shared rail makes them look like direct rivals, and at the protocol layer they are similar. The difference is what comes back in the response. Laevitas returns options and derivatives analytics; BlackForge returns per-venue spot order-book depth, ladders and book behaviour. This page is about the payload, because the payload is the whole decision.
What is the difference between BlackForge and Laevitas?
Laevitas ships options and derivatives analytics over a keyless x402 rail and an MCP server. BlackForge ships spot order-book microstructure over its own keyless x402 rail and an MCP server. Both are machine-payable by the call with no account. Laevitas is derivatives and volatility; BlackForge is per-venue spot depth, order ladders and book behaviour. Same rail, different payload.
What each feed returns
Laevitas is options and derivatives first. Its data is implied volatility, Greeks, funding, and volatility surfaces, covering venues including Deribit and Hyperliquid, and it advertises coverage across more than fifteen exchanges and over a thousand assets. It exposes that through an MCP server of more than eighty tools and an x402 endpoint priced at $0.001 per call, keyless, on Base and Solana. For an agent whose question is implied volatility or funding, that is a deep and well-worn tool surface.
BlackForge is spot first. One keyless x402 call at 0.005 USDC returns up to 100 rows, and each row carries all 120 columns across all nine venues: depth walls, seven-rung order ladders, and the computed book-microstructure columns like level flicker, resting-level lifetime and liquidity added and removed. It is a narrow universe measured deeply, rather than a wide universe summarised.
The one place the two seem to touch is spot depth, and it is worth being precise. Laevitas does carry spot L2, but it is aggregated across venues and it is not in the x402-eligible path. So over the machine-payable rail, the spot book with per-venue detail is not what a Laevitas call returns.
| Laevitas | BlackForge | |
|---|---|---|
| Primary domain | Options and derivatives, implied volatility | Spot order-book microstructure |
| x402 | $0.001/call, keyless, Base and Solana | 0.005 USDC/call up to 100 rows, keyless, Base |
| MCP server | More than 80 tools | Yes |
| Spot book over x402 | Aggregated L2, not in the x402 path | Per-venue walls, ladders and book behaviour |
| Coverage claim | 15-plus exchanges, 1000-plus assets | 9 spot venues, ~11,800 pairs |
| Retention | Not stated | Every window stored, retention infinite |
Is the x402 rail the differentiator? No, the payload is
Machine payment over x402 and an MCP server are both table stakes now. CoinGecko, CoinMarketCap, Velo and Usenami all ship MCP, and a growing cohort accepts x402. So "we are on x402" says nothing on its own. The question an agent builder should ask is what a single keyless call actually returns, and there the cohort splits cleanly.
Across the whole x402 cohort, nobody else ships per-venue raw multi-exchange order-book depth, meaning walls plus ladders. The others sell aggregate per-asset USD bands (Cryptyx), per-venue precomputed slippage at a notional size (Usenami), cross-venue-aggregated L2 (Laevitas), or single-venue top-of-book (scrape402, now retired). Those are all legitimate shapes, and for some jobs they are exactly right. None of them is per-venue depth with the ladders and the computed book columns attached.
So the honest claim, stated carefully, is this: BlackForge is the only x402 payload that returns per-venue depth walls, order ladders and computed book microstructure across the full spot universe in one call. Not "the only order book on x402", which would be wrong, but the only one carrying that specific per-venue, computed shape.
The reason this shape is worth caring about for an agent is that per-venue detail is where routing and execution questions actually live. An aggregate USD band tells you the market has depth somewhere; it does not tell you which venue holds it. A slippage-at-notional number answers one preset size; it does not let the agent pick its own. A per-venue depth wall with the ladders attached lets the agent reason about where the size sits and what it would cost to reach, on the specific venue it can trade on, without a second call to resolve the ambiguity the first one left.
| Service | x402 price | What the payload carries | Per-venue raw depth? |
|---|---|---|---|
| Cryptyx | $0.01 | Aggregate per-asset USD bands | No |
| Usenami | $0.001 to $0.010 | Precomputed slippage at notional | Partial |
| Laevitas | $0.001 | Aggregated L2 and derivatives analytics | Partial |
| BlackForge | 0.005 USDC up to 100 rows | Per-venue depth walls, seven-rung ladders, book microstructure | Yes |
What one BlackForge call carries
The point of a single 120-column row is that an agent does not have to make three calls to reason about a pair. Depth, ladder rungs and book behaviour arrive together, for the venue you asked about, in the shape you can act on. Here are three of those columns, measured live on the largest venue in the most recent closed window.
BTCUSDT on binance
- Near bid depth
- $48.1M
- Near ask ladder rung
- $31.8M
- Bid liquidity removed
- $283.9M
Where Laevitas wins
Laevitas
- Options analytics, implied volatility and volatility surfaces, and Greeks, none of which BlackForge computes.
- Hyperliquid and Deribit derivatives coverage that BlackForge does not carry.
- A longer operating track record than BlackForge, and a wider advertised universe of exchanges and assets.
- An established keyless x402 ledger and an MCP server of more than eighty tools, live longer than BlackForge and broader in surface.
Choose them if you need options or derivatives analytics, implied volatility, Hyperliquid coverage, or a broader agent tool surface. Choose BlackForge if you need per-venue spot order-book depth, ladders and book behaviour in the x402 payload.
So which do you point your agent at?
If the agent is reasoning about volatility, options, or derivatives positioning, Laevitas has the tools and the history, and BlackForge has none of that. If the agent is reasoning about the spot book, where depth sits per venue, how the ladders stack, how much liquidity was pulled, then you want the per-venue computed payload, and over x402 that is BlackForge. Both are keyless and pay-per-call, so an agent can hold both and choose per question rather than committing to one.
Is BlackForge on x402?
Yes. BlackForge accepts x402 keyless on Base at 0.005 USDC per call for up to 100 rows, and each row carries all 120 columns across all nine venues. There is no account and no API key on that rail: the wallet that pays is the identity. An API-key path also exists for teams that prefer a key and a plan, but the x402 rail is there specifically so an agent can pay by the call.
Does Laevitas have spot order book over x402?
Its spot L2 is aggregated across venues and is not in the x402-eligible path, so a keyless Laevitas call does not return per-venue spot depth. What Laevitas does serve over x402 is its derivatives and volatility analytics, at $0.001 per call on Base and Solana. If the per-venue spot book is what you need over the machine-payable rail, that is the gap BlackForge fills.
Who ships raw per-venue depth over x402?
BlackForge. Across the x402 cohort checked 2026-08-11 and 12, the others sell aggregate per-asset USD bands, per-venue precomputed slippage at a notional, or cross-venue-aggregated L2. BlackForge is the one returning per-venue depth walls, seven-rung order ladders and computed book microstructure across the full spot universe in a single call. That is a specific shape, not a claim to be the only order book on x402.
Do I need an API key for BlackForge?
Not on the x402 rail. The wallet that pays for the call is your identity, so there is no signup, no key to store and no plan to pick before you can read a row. That is what makes it usable by an autonomous agent. If you would rather work with a key and a monthly plan, that path exists too, but keyless pay-per-call is the default machine rail.
See the full metric reference, or browse all comparisons.