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

# Overview

> Move an integration from another spot data provider to Metastreams.

Each guide maps one provider's spot API to this one: authentication, chain identifiers, endpoint by endpoint, and field by field on the token object.

<CardGroup cols={2}>
  <Card title="Mobula to Metastreams" icon="arrow-right-arrow-left" href="/migrate/mobula">
    Endpoints, streams and every field on the token object.
  </Card>
</CardGroup>

## What every migration has in common

Whatever you are coming from, four things differ from most providers:

| | Metastreams |
| - | - |
| Authentication | `Authorization: Bearer <key>` only. No query-string key, no `x-api-key`, and no keyless tier. |
| Chain | A slug in the path: `/v1/tokens/solana/{address}`. Not a query parameter, and not a numeric chain ID. |
| Money | Every priced value carries both `native` and `usd`, as decimal strings. There is no bare `priceUsd`. |
| Windows | Trailing stats nest under `stats`, keyed `5m` to `24h`, rather than fusing the window into the field name. |

[Reading responses](/concepts/reading-responses) covers all four in full.

## Before you start

1. [Get a key](/get-started/api-keys). There is no self-serve signup, and no keyless host to test against.
2. Read [Errors, limits and retries](/concepts/errors), so your client handles refusals the same way from day one.
3. Check [Chains](/concepts/chains) for the slugs, which are the one thing no provider spells the same way.

Missing a provider you need? [Ask us](/resources/support) and we will write the guide.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.