Camelot API: subgraphs and pool data for Arbitrum's native DEX
Camelot is Arbitrum's native DEX, built on Algebra with volatility-adjusted fees. Its pool data comes from subgraphs on The Graph, or from one keyless REST call that covers V2 and V3, checked 16 November 2026.

Camelot publishes its pool data as subgraphs on The Graph's decentralized network: one each for its V2 and V3 pools, plus a blocks helper listed under V4. According to DexPaprika data, Camelot's V2 and V3 pools traded $1.39 million on Arbitrum in the 24 hours to 16 November 2026, and both versions can also be read with one REST call, no Graph key needed.
Camelot is Arbitrum's native DEX, built on Algebra's concentrated liquidity engine for V3, with fees that adjust to volatility and direction.
Camelot (GRAIL) launched on Arbitrum in 2022 and has built for the Arbitrum ecosystem since, including Arbitrum's Orbit chains. This guide covers the two ways a developer reads its pools: the subgraphs Camelot lists, and a REST index that covers both versions.
Camelot subgraphs: where they are and how to call them
The documentation at docs.camelot.exchange is organized around the protocol: the Orbital Liquidity Network, Launch & Genesis, Protocol, Tokenomics and Contracts, among others. The subgraphs sit on the Contracts page for Arbitrum One, under a "Subgraphs" heading:
The subgraphs exist, but they sit under Contracts, several clicks from the References section a developer would check first. The Arbitrum One contracts page lists three entries under a small "Subgraphs" heading:
AMMv2 https://gateway-arbitrum.network.thegraph.com/api/api_key/subgraphs/id/8zagLSufxk5cVhzkzai3tyABwJh53zxn9tmUYJcJxijG
AMMv3 https://gateway-arbitrum.network.thegraph.com/api/api_key/subgraphs/id/3utanEBA9nqMjPnuQP1vMCCys6enSM3EawBpKTVwnUw2
AMMv4 https://gateway-arbitrum.network.thegraph.com/api/api_key/subgraphs/id/JBnWrv9pvBvSi2pUZzba3VweGBTde6s44QvsDABP47Gt
(this one is named "Blocks")
The api_key segment is a placeholder for a key from The Graph's Studio. Queries run on The Graph's gateway and The Graph bills for them, the same arrangement Uniswap uses for its own subgraphs. The V4 entry, named "Blocks", maps block numbers to timestamps, a helper for time-based queries. Camelot's newest AMM, documented in full under Protocol, does not have a full subgraph listed yet.
Around that, CamelotLabs on GitHub maintains the integration pieces other tools rely on: a token list, the DefiLlama TVL adapter and the DexScreener adapter. Since late September it also hosts two repos for Frontier, a Uniswap v4 hook deployed on Robinhood Chain.
Camelot's place in Arbitrum DEX volume
Summing every DEX DexPaprika indexes on Arbitrum, 17 of them, as of 16 November 2026, 10:52 UTC, this is where Camelot lands:
Camelot's two versions together traded $1.39 million that day, 0.8% of Arbitrum's indexed DEX volume. Uniswap V3 and V4 together were 77.1%, and Fluid took 17.2%. An app that needs the whole chain should index all 17 DEXes; an app built around Camelot gets both of its versions from the calls below.
On 23 September 2026 the same call put Camelot at 3.3%, $7.4 million in a day, and Arbitrum's total was higher too, $221.2 million against $178.3 million. Two readings make no trend, so rerun the call for today's numbers.
Camelot pool data with one REST call
Instead of composing GraphQL against a subgraph ID, you can call a REST index that already covers both versions. No Graph key, no api_key placeholder to fill in:
curl "https://api.dexpaprika.com/networks/arbitrum/pools/search?dex_name=camelot_v3&limit=3"
That returns HTTP 200 with {results, has_next_page, next_cursor, query}. Each row carries id, dex_id, dex_name, chain, volume_usd_24h, volume_usd_7d, volume_usd_30d, liquidity_usd, transactions_24h, price_usd, fee, created_at, the five price_change_percentage_* windows and a tokens array. One field is worth explaining rather than treating as missing data: fee comes back null on every Camelot V3 row. Camelot's docs describe "Directional & Dynamic Volatility Fees", a fee that adjusts per pool by market volatility and can differ for buys and sells, so there is no single static number to report.
Swap camelot_v3 for camelot_v2 and the shape does not change. Candles come from /networks/arbitrum/pools/{address}/ohlcv, individual swaps from /networks/arbitrum/pools/{address}/transactions, which Camelot's subgraphs only give you through your own GraphQL queries and a Graph key. Candles work without a key for the last 24 hours, so a relative start keeps the call valid whenever you run it:
curl "https://api.dexpaprika.com/networks/arbitrum/pools/0x60451b6ac55e3c5f0f3aee31519670ecc62dc28f/ohlcv?start=-12h&interval=1h&limit=5"
That pool is GRAIL/WETH on Camelot V3, and its factory_id is the AlgebraFactory address Camelot's contracts page lists under AMMv3. The transactions endpoint needs a Dev or Pro plan; without a key it answered HTTP 403 on 16 November.
Pool search and recent candles need no key. A free key from console.dexpaprika.com raises the rate and the quota and reaches further back in candle history, current numbers on the pricing page because they move. Free-tier data can run up to 60 seconds behind the chain; real-time is the paid tier. There is also a live page for Camelot on Arbitrum, both versions, updating as swaps land.
Where GRAIL itself trades
GRAIL is listed on CoinPaprika under the id grail-camelot-token. DexPaprika counts 139 GRAIL pools on Arbitrum, and Camelot's own pools carried 82.2% of the token's 24 hour volume, led by GRAIL/WETH on Camelot V3 and GRAIL/ARB on Camelot V2; the rest traded on PancakeSwap V3 and SushiSwap V3.
One thing worth one sentence: GRAIL has a second, non-transferable token, xGRAIL, earned by staking GRAIL or through farming and used to vote for protocol plugins. Camelot's own docs call it "a non-transferable escrowed governance token, corresponding to staked GRAIL", so it never lists on a DEX and carries no market price to index.
Common questions
Does Camelot have an API?
Camelot publishes its data as subgraphs: full subgraphs for V2 and V3 on The Graph's decentralized network, plus a blocks helper listed under V4, all on its Contracts page. You call them with your own Graph API key, or read both versions over REST from an index such as DexPaprika.
Do you need an API key for Camelot data?
For the subgraphs, yes: a key from The Graph's Studio, billed by The Graph. Camelot does not issue keys itself. DexPaprika's pool search and recent candles need no key.
What is Camelot V3 built on?
Algebra's V1.9, a tick-based concentrated liquidity engine, by Camelot's own description. The dynamic, direction-specific fee it adds is why a pool-data API reports fee: null for Camelot V3 rows rather than a fixed tier.
How much of Arbitrum's DEX volume does Camelot carry?
About 0.8% combined across V2 and V3 on 16 November 2026, measured against every DEX DexPaprika indexes on the chain (3.3% on 23 September). Uniswap's two versions together were 77.1%.
What is the difference between GRAIL and xGRAIL?
GRAIL is the tradeable token, indexed and priced like any other. xGRAIL is a non-transferable escrowed version earned by staking GRAIL, used for governance and yield plugins, and it has no market price because it cannot be sold.
Does Camelot support Arbitrum only?
No. Camelot's Contracts section also lists a Sepolia testnet deployment and more than a dozen Orbit chains. This article measures Arbitrum One, where the volume is.
How these numbers were measured
Everything above was read from a live source on 16 November 2026, except the 23 September figures, which come from our first measurement with the same calls.
The docs structure and the three subgraph URLs came from a full crawl of docs.camelot.exchange's sitemap, then Contracts > Arbitrum > One (Mainnet), where the AMMv3 factory address matched DexPaprika's factory_id for camelot_v3 exactly. The GitHub repo list is the CamelotLabs organization via the GitHub API.
The Arbitrum table is one GET /networks/arbitrum/dexes call, fetched 10:52 UTC on 16 November 2026, covering all 17 DEXes DexPaprika indexed on the chain that hour. Every share in the table is that DEX's volume divided by the sum of all 17 rows. GRAIL's listing and pool count came from CoinPaprika and DexPaprika directly, and Camelot's share of GRAIL volume is the sum of the 13 GRAIL pools pool search returned with volume, which matches the token's 24 hour total. The OHLCV call returned HTTP 200 without a key; the transactions call returned HTTP 403.
Every volume figure is a 24 hour window closing at measurement time and will have moved by the time you read this. Rerun the DEX share before relying on it for anything that matters.
Full REST reference at docs.dexpaprika.com. For the rest of Arbitrum's data options, there is a broader comparison of seven Arbitrum APIs, and the same question answered for two other DEXes: what the Uniswap API returns, and what PancakeSwap documents for BNB Smart Chain.
CoinPaprikaオリジナルガイド。