API Changelog

Versioning policy

Additive changes ship in place under /api/v1 with a minor version bump: new optional parameters, new fields on existing objects, new values in a response enum, and brand-new endpoints. Your client keeps sending exactly what it sent and keeps getting everything it got. Parse responses leniently — ignore fields you do not recognize — and these releases are invisible to you.

A change that would require you to send something new to keep working, or that renames, removes or retypes a field you already read, ships as a new base path (/api/v2), with a deprecation window on /api/v1 announced here before anything is switched off. We do not quietly change the meaning of an existing field.

The version is reported as info.version in the OpenAPI specification. It is documentation of what the v1 surface currently offers, not a value you send: there is no version header or parameter, and the base path is the only version selector.

1.1.0 2026-09-27

Multi-chain support. Entirely additive — no breaking changes, and no action required from existing integrations.

• Optional chain parameter on every endpoint — a query parameter on GET, a body field on POST /score and POST /whale-activity. Values are the chain keys the endpoint covers, plus all.
• chain field on every token object — scores, token info blocks, DCA orders, limit orders and LP cheat-sheet rows — plus a top-level chain echo on the score, top-scores, dlmm/:address, dlmm-pools and lp-cheat-sheet responses, and inside every query_parameters echo.
• Three new 400 error codes: invalid_chain, chain_not_supported and chain_mismatch. They only ever appear on a request that sends chain, or that sends a 0x address to a Solana-only endpoint. A chain that simply names which chain an address is on is never an error — only one that contradicts the address is.
• One CLOBr score per asset. A token that trades on more than one chain has a single score, computed from depth merged across all of them. /score and /top-scores report that one number, the same one the CLOBr web app shows, whichever of the asset's addresses you ask about.
• GET /score/:address is now documented in the OpenAPI specification. The route itself is unchanged and has been live since 1.0.0.
• /score, /top-scores and /limit-orders now serve Robinhood Chain tokens alongside Solana. Address-keyed endpoints accept a 0x contract address wherever the data exists on that chain.
• List endpoints still default to solana (/top-scores, /dca-pressure, /dlmm-pools, /lp-cheat-sheet). Mixing other chains into a list you already consume would be a breaking change in disguise, so you opt in with chain=all or a specific key.

Details and per-endpoint chain support: Chains in the endpoint reference.

1.0.0

Initial public release of the CLOBr API, Solana only:

• Token scores — GET /score/:address and the Enterprise batch POST /score, plus GET /top-scores.
• Liquidity — GET /market-depth with optional aggregated support/resistance summaries.
• Order flow — GET /dca-pressure, GET /dca-orders and GET /limit-orders.
• Holders — GET /whale-activity and the bulk POST /whale-activity.
• LP tooling — GET /dlmm/:address, GET /dlmm-pools and GET /lp-cheat-sheet.
• API-key authentication via the x-api-key header, with Premium and Enterprise tiers.