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

# AI Agents

> Every way to drive SmartlyQ from an AI agent or LLM — MCP, llms.txt, the per-page AI menu, and the REST API.

SmartlyQ is built to be driven by AI. Whether you're wiring up an autonomous agent, an assistant, or a coding tool, there are four ways to connect — pick the one that fits your client.

<CardGroup cols={2}>
  <Card title="MCP Server" icon="plug" href="/mcp-server">
    The hosted **Model Context Protocol** server. Connect Claude, Cursor, ChatGPT, or any MCP client and let an agent post, generate content, and read analytics with natural language. **Start here for most agents.**
  </Card>

  <Card title="Use these docs in your AI" icon="file-lines" href="/llms.txt">
    A machine-readable index of the entire documentation at **`/llms.txt`**. Paste it (or the `Open in ChatGPT/Claude` links at the top of any page) so an assistant can answer questions against the real, current docs.
  </Card>

  <Card title="REST API" icon="code" href="/quickstart">
    Every capability is a plain HTTPS endpoint with an `sqk_live_` Bearer key. Agents that can't speak MCP can call the API directly — see the [API Reference](/api-reference).
  </Card>

  <Card title="Per-page AI actions" icon="sparkles">
    Every page has a **Copy page** button and an **Open ▾** menu (ChatGPT, Claude, Perplexity, Grok, Cursor, VS Code). Send any page straight into your assistant to ask questions about it.
  </Card>
</CardGroup>

## Which one should I use?

| You're building…                              | Use                                                 |
| --------------------------------------------- | --------------------------------------------------- |
| An agent in Claude, Cursor, ChatGPT, Windsurf | **[MCP Server](/mcp-server)** — tools are pre-wired |
| A custom backend / your own agent loop        | **[REST API](/quickstart)** with an API key         |
| An assistant that answers docs questions      | **[llms.txt](/llms.txt)** + the per-page AI menu    |

## Authentication is the same everywhere

Whichever path you take, access is governed by a single **API key** and its [scopes](/authentication). The MCP server, the REST API, and any SDK all forward that key — there's no separate agent credential to manage, and the same [billing](/guides/billing-and-credits) and [rate limits](/guides/rate-limiting) apply.

<Tip>
  New to the API? Start with the **[Quickstart](/quickstart)** to get a key and make your first call, then point your agent at the **[MCP Server](/mcp-server)**.
</Tip>