> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cryptorank.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What changed between Public API v2 and v3, and how to move your integration over.

This guide is a high-level map for teams already integrated on v2 — what moved, what to call instead, and how to recheck your plan. For field-by-field details, follow the links to each endpoint's reference page.

## What changed at a glance

v2 exposed a few **monolithic `full-metadata` endpoints** that returned everything about an entity in one response. Data is split into **granular endpoints**, each returning one focused slice.

This is the core shift to plan around — see [Endpoint mapping](/migration/endpoints-mapping) for the full table.

<CardGroup cols={2}>
  <Card title="Plans & limits" icon="gauge" href="/migration/plans-and-limits">
    Per-plan rate limits and credit allowances, and how the new call pattern affects consumption.
  </Card>

  <Card title="Endpoint mapping" icon="arrows-left-right" href="/migration/endpoints-mapping">
    Every v2 endpoint and its v3 replacement(s).
  </Card>
</CardGroup>

## Base conventions

* **Prefix.** All routes live under `/v3`. There is no shared-version mode — a key calls v3 routes directly.
* **Authentication.** Pass your key in the **`X-Api-Key` header**. v3 never accepts the key as a query parameter.
* **Response envelope.** Object responses return `{ data, status }`; list responses return `{ data, meta, status }`. Read your payload from `data`.

## Migration timeline

<Steps>
  <Step title="Parallel window — v2 and v3 run together">
    For several months after v3 ships, v2 and v3 are both live. Integrate and
    validate v3 against your real traffic during this window.
  </Step>

  <Step title="v2 shutdown">
    After the parallel window, v2 plans can't be purchased or renewed. Active
    subscriptions run until their paid period ends, then you'll need v3.
  </Step>
</Steps>