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

# API

> Connect Remapdb to your backend or internal tools with clear setup, endpoint, and operations guidance.

Use this section to set up and run API access safely, including direct API requests, SDK workflows, and MCP-based AI tool connections.

Need endpoint-level request/response details? Open the [API reference](/api-reference/introduction).

Click the [**API**](https://app.remapdb.com/api) item in the main navigation.

## Use this section when

* You want to pull Remapdb data into your own backend.
* You want to automate workflows outside the Remapdb interface.
* You want to connect AI tools to Remapdb vehicle tuning data through API access.
* You need a clear setup path for credentials, endpoint usage, and daily request planning.

<Info>
  API access depends on your [plan](https://app.remapdb.com/settings/billing) and [feature access](/feature-availability-by-plan).
</Info>

<Warning>
  Never place API credentials in frontend code, browser storage, or public repositories. Keep them on your server or secure environment.
</Warning>

## What you can do from the API page

* Copy your `API key` and `API secret`.
* Click the **Generate new credentials** button when you need to rotate keys.
* Click the **API documentation** link for endpoint contracts.
* Open [API reference](/api-reference/introduction) for interactive endpoint docs.
* Use API access with MCP-based AI tools through [AI Integrations](/api/ai-integrations).
* Click the **PHP SDK** or **JavaScript SDK** link if you prefer SDK-based integration.

## Recommended order

* Start with [Credentials and authentication](/api/credentials-and-authentication).
* Connect [Remapdb AI Integrations](/api/ai-integrations) if you want MCP-based AI tools to use vehicle data through API access.
* Continue with [Best practices](/api/best-practices) before go-live.
* Check [Usage limits](/api/usage-limits) so traffic stays stable.
* If credentials are locked, open [Plan access](/api/plan-access).

## Success looks like

* Your integration authenticates successfully.
* Your requests return expected data in staging and production.
* You can monitor usage and rotate credentials without downtime.

## Pages in this section

<div className="px-4 pb-10 max-w-6xl mx-auto">
  <Columns cols={2}>
    <Card title="Credentials and authentication" href="/api/credentials-and-authentication" className="rounded-sm">
      Copy, store, and rotate API credentials safely.
    </Card>

    <Card title="AI Integrations" href="/api/ai-integrations" className="rounded-sm">
      Use API access to connect MCP-based AI tools to Remapdb vehicle tuning data.
    </Card>

    <Card title="Best practices" href="/api/best-practices" className="rounded-sm">
      Use security, reliability, and rollout standards that prevent outages.
    </Card>

    <Card title="Plan access" href="/api/plan-access" className="rounded-sm">
      Check which plans include API access and unlock credentials if needed.
    </Card>

    <Card title="Usage limits" href="/api/usage-limits" className="rounded-sm">
      Plan daily request volume and avoid limit-related interruptions.
    </Card>

    <Card title="API reference" href="/api/api-reference" className="rounded-sm">
      Browse interactive endpoint documentation.
    </Card>
  </Columns>
</div>