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

# API Overview

> Understand how SDK, Backend API, and MCP relate to each other inside ActionX.

This page is not a parameter reference. It helps you understand where each integration surface sits in the system.

```mermaid theme={null}
flowchart LR
    sdk["SDK"] --> ads["ads-server"]
    api["Backend API"] --> ads
    mcp["MCP"] --> ads
```

## How the three integration paths relate

* SDK: best for frontend rendering and page integration when you want to show results quickly
* Backend API: best for server-side request control and centralized orchestration
* MCP: best for tool-calling scenarios in agent runtimes and MCP clients

## Where they all converge

* All three paths eventually feed into the ActionX decisioning flow.
* `ads-server` remains the core decision point for request handling.
* The main difference is who makes the request, who consumes the result, and who renders it.

## Suggested reading path

<Columns cols={3}>
  <Card title="Backend API structure" href="/backend-api/overview">
    Review the request body, slots, and response structure.
  </Card>

  <Card title="SDK Integration" href="/developers/sdk-integration">
    See how a frontend app can integrate quickly.
  </Card>

  <Card title="MCP Integration" href="/developers/mcp-integration">
    See how `ads.request` is called in MCP-based scenarios.
  </Card>
</Columns>