Skip to main content
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.

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.

Use these docs in your AI

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.

REST API

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.

Per-page AI actions

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.

​
Which one should I use?

You’re building…Use
An agent in Claude, Cursor, ChatGPT, WindsurfMCP Server — tools are pre-wired
A custom backend / your own agent loopREST API with an API key
An assistant that answers docs questionsllms.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. 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 and rate limits apply.
New to the API? Start with the Quickstart to get a key and make your first call, then point your agent at the MCP Server.