Pricing, limits, and integration
Access is included on every plan: the €89 Starter, the €379 Growth, the €299 Agency Growth and Enterprise all get both the API and the MCP server, with rate limits as the only scaling axis (60, 120 and 300 requests a minute respectively, with X-RateLimit headers telling you where you stand). There is no separate API pricing and no add-on fee, and keys are self-serve from the dashboard.
Plan limits shape agent workloads more than the rate limits do. Starter tracks 50 prompts across 3 engines and retains 2 months of history; Growth raises that to 150 prompts and adds CSV, Excel and JSON exports; only Enterprise keeps all-time history. For an agent stack, that retention limit is the thing to design around: schedule a pull of metrics and responses through the API into your own store, and the 2-month window stops mattering.
The practical pattern I would run: connect Claude Code or Cursor to the MCP server for interactive analysis (competitive gaps, citation sources, page audits, the strategic action plan tool), give scheduled jobs a Bearer key to archive time series and raw responses weekly, and grant write:prompts scope only to the agent that manages your tracking set. The open-source server code is a bonus most vendors do not offer: you can read exactly what each tool does before you wire it in.
How much does the Superlines API actually cost?
Superlines publishes an API, but per-tier gating wasn't extracted automatically.
- Most likely scenario: API access is either included in all paid plans, or it's gated to higher tiers and we need to verify on the live docs page.
- Until verified, treat the question "which plan unlocks the API" as open. Don't budget on the assumption it's free with the cheapest paid plan.
API at a glance
Webhooks: Webhook notifications are listed on the developer page for event-driven workflows alongside the API. Setup details live in the app rather than public docs, so confirm the event catalog on your plan during the trial.
Which AI clients can read Superlines data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Superlines specifically.
| Client | Support | Notes |
|---|---|---|
| Claude Code | Native MCP | Documented client: add the remote server URL with your API key token, or run @superlines/mcp-server locally via npx with SUPERLINES_API_KEY. |
| Claude (Desktop/Web) | Native MCP | Works via the npm package (stdio) with SUPERLINES_API_KEY in the env, or the remote HTTP endpoint. |
| Cursor | Native MCP | Documented client with the same remote URL or npx setup. |
| Windsurf | Native MCP | Listed among supported MCP-compatible agents. |
| n8n | API-only (custom code) | No native node; the Bearer-authenticated API plus webhooks cover workflow automation. |
Superlines also has an MCP server
If you're wiring Superlines into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Superlines MCP pageWhat you can build with the Superlines API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Superlines into your daily workflow
- Pull a digest of fresh activity into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Superlines reporting at scale
- White-label Superlines data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Superlines UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Superlines
- Real-time sync into your warehouse via webhooks
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Superlines data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Superlines API docs: https://docs.superlines.io curl -X GET "https://api.superlines.io/<your-endpoint>" \ -H "Authorization: Bearer $YOUR_API_KEY" \ -H "Accept: application/json" | jq .
Template only. Endpoint paths, exact base URL, and auth header format come from docs.superlines.io.
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- Webhooks available — react to Superlines events in real time instead of polling.
- No official SDK detected. Plan on hitting the API directly with your HTTP client of choice.
- Rate limits: always read the docs page before scaling — the published limit is usually lower than the practical one and overages can be expensive.
- Structured JSON outputs — agent-friendly, no scraping required.
Agent-readiness verdict
A complete, honestly rate-limited API included on every plan, with webhooks and markdown docs. The query-parameter endpoint design and the missing OpenAPI spec cost it polish and client-generation convenience, holding it at 7 out of 10.
Official MCP server (GitHub Superlines/mcp-server, npm @superlines/mcp-server, remote HTTP at mcpsse.superlines.io) with 27 tools: 21 reads covering metrics, citations, competitive gaps, webpage audits and strategy, plus 6 writes gated behind scoped permissions (write:brands, write:prompts). REST API with Bearer keys and published per-plan rate limits (60/120/300 rpm) on every plan including Starter. Held back from higher: query-param API design with no OpenAPI spec, and the remote MCP passes the API key as a URL token parameter.
Superlines API FAQ
Does Superlines have a public API?+
What auth does the Superlines API use?+
Does Superlines support webhooks?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Superlines official site: https://www.superlines.io
- API docs: https://docs.superlines.io
- MCP server: https://docs.superlines.io/mcp/overview
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.