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

# Welcome to CDP API

> Trusted crypto infrastructure at scale

## Overview

CDP offers two distinct sets of APIs that serve different use cases:

* **Non-custodial APIs**: User Wallets, API Key Wallets, Onramp, and related tools. Available to any CDP entity immediately after signing up.
* **Custodial APIs**: Transfers between custodied accounts, trading orders, payment acceptance, financial reporting, and more. These require a verified business account linked to CDP. To verify your business and link an account, see [Initial Setup](/get-started/initial-setup#verify-your-business-and-go-live).

## Custodial API groups

The following API groups require a verified business account. See each group in the API reference for its full, current list of endpoints.

* **[Accounts](/api-reference/v2/rest-api/accounts/accounts)**: Create and manage custodied accounts, or link existing Coinbase Prime and Coinbase Business accounts.
* **[Deposit Destinations](/api-reference/v2/rest-api/deposit-destinations/deposit-destinations)**: Inbound deposit addresses attached to your accounts, used to receive crypto from external sources.
* **[Transfers](/api-reference/v2/rest-api/transfers/transfers)**: Move funds between your accounts.
* **[Payment Methods](/api-reference/v2/rest-api/payment-methods/payment-methods)**: External financial instruments (Fedwire, SWIFT, SEPA) linked to your accounts. Currently supported for Coinbase Prime only.

## API stability

Some CDP API groups are labeled **Beta** in the API reference sidebar. A Beta label signals that the endpoint is functional and used in production today, but its request/response shape may still evolve as we incorporate feedback, so plan for change. API groups without a label are generally available, meaning the contract is stable and suitable for production traffic without special handling.

**Recommendations when integrating with Beta endpoints**

* Isolate the call site behind a thin adapter in your code so a future schema change is a one-file update.
* Share feedback in the [CDP Discord](https://discord.com/invite/cdp).

## Get started

Authenticate with a single API key to access every CDP service.

<CardGroup cols={2}>
  <Card title="Get an API key" icon="key" href="https://portal.cdp.coinbase.com/api-keys/secret">
    Create a project and generate your API key in the CDP Portal
  </Card>

  <Card title="Authentication guide" icon="lock" href="/api-reference/v2/authentication">
    Learn how to sign requests and connect to the API
  </Card>
</CardGroup>

## OpenAPI Spec

<Card title="Download OpenAPI Spec" icon="download" href="https://docs.cdp.coinbase.com/api-reference/v2/cdp-api-v2.yaml">
  To use with Postman or to generate client SDKs.
</Card>