> ## 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.

# Choose an integration path

> Compare SDK, Backend API, and MCP side by side to choose the right integration path.

If you want to answer one question first, "How should I integrate ActionX?", this page is the answer.

```mermaid theme={null}
flowchart LR
    sdk["SDK<br/>Frontend rendering<br/>Fastest path"] --> ads["ActionX decision layer"]
    api["Backend API<br/>Server-side control<br/>Unified orchestration"] --> ads
    mcp["MCP<br/>Tool calling<br/>Agent workflows"] --> ads
```

<Columns cols={3}>
  <Card title="SDK" href="/developers/sdk-integration">
    Best for web applications that render placements, cards, or recommendations directly in the frontend.
  </Card>

  <Card title="Backend API" href="/developers/api-overview">
    Best when your backend requests results centrally and passes them into your product frontend.
  </Card>

  <Card title="MCP" href="/developers/mcp-integration">
    Best for AI clients, agent runtimes, or toolchains that already use MCP.
  </Card>
</Columns>

## How to choose

* Choose SDK if you want the frontend to control rendering directly.
* Choose Backend API if you want the backend to control requests, policy, or shared logic across clients.
* Choose MCP if your product already works around MCP and tool calling.

## Confirm these three things before deciding

* Who initiates the request: the frontend, the backend, or an agent runtime
* Who renders the result: the SDK, your frontend, or an MCP client
* Whether you need monetization logic to live centrally on the server or in the tool-calling layer