Skip to main content
Migration Guides help teams move from another onchain data API to Codex with as little friction as possible. Each guide is written for engineers who already have working code against a different provider and want a clear, endpoint-by-endpoint path to the Codex equivalent. Every guide in this section follows the same shape:
  • Mental model: how Codex’s API differs from the source provider so you know what to expect.
  • Endpoint mapping: a table that pairs each source endpoint with the closest Codex query, subscription, or webhook.
  • Side-by-side examples: working request/response comparisons for the most common patterns.
  • Gaps and gains: things the source provider does that Codex doesn’t (yet), plus the capabilities you pick up by moving.
  • AI migration prompt: a copy-paste prompt you can hand to an LLM to translate your existing integration.

​
Available guides

SourceStatusGuide
BirdeyeLiveBirdeye to Codex
CoinGeckoLiveCoinGecko to Codex
Dune SimLiveDune Sim to Codex
Note: Looking for a migration guide for a different provider? Reach out to us via email and we’ll add it to our queue.

​
Before you start

No matter which provider you’re moving from, two things are worth doing first:
  1. Get an API key. Codex authenticates every request with an API key from the dashboard. See Authentication for the request format and short-lived key flow.
  2. Skim Queries and Subscriptions. Codex is a GraphQL API with WebSocket subscriptions, not a REST API. If your existing integration is REST-only, the shape of requests will change even where the data is identical.
If you hit something a guide doesn’t cover, the FAQ, Troubleshooting page, and our community are the fastest paths to an answer.