Pricing, limits, and integration
LLM Pulse's REST API is included with the SaaS subscription rather than sold separately, but it is gated by tier. API key generation unlocks on the Scale plan (€299/month) per the pricing page, with headless keys for servers, cron jobs and custom backends emphasized at Scale+ (€599). There is no separate per-call API fee on top of the subscription.
Authentication is Bearer-token: generate keys in the dashboard, include them in the Authorization header, and rotate or revoke them under Settings, API Keys. Error handling is explicit: a missing or malformed header returns 401 ERR_MISSING_AUTH, an unknown key 401 ERR_INVALID_API_KEY, and a revoked key 403 ERR_REVOKED_API_KEY. The rate limit is 300 requests per minute per key, with rate-limit headers in responses; contact the team for higher quotas.
For most agent use cases the MCP server is the better path and it is cheaper: it is on every plan, uses OAuth with no API key, and exposes 45+ tools. Reach for the REST API when you need headless, scripted access from your own backend or a tool like n8n, which is where the Scale-tier gate and the 300 req/min limit come into play. A Postman collection is provided for both onboarding and testing.
How much does the LLM Pulse API actually cost?
LLM Pulse 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
Which AI clients can read LLM Pulse data?
Not every AI assistant supports MCP natively. Here's the per-client picture for LLM Pulse specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Add the MCP server URL and authenticate via OAuth; no API key needed. |
| Claude Code | Native MCP | Connects to the hosted MCP server over OAuth; full read/write tool access. |
| ChatGPT | Native MCP | Supported as an MCP client per LLM Pulse docs; OAuth sign-in. |
| Cursor | Native MCP | Native MCP support; add the server and sign in once. |
| Windsurf | Native MCP | Listed as a supported MCP client. |
| Gemini | Native MCP | Listed as a supported client; OAuth-based MCP connection. |
| n8n | API-only (custom code) | No native node; integrate via the REST API (Scale tier) with Bearer auth. |
LLM Pulse also has an MCP server
If you're wiring LLM Pulse into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See LLM Pulse MCP pageWhat you can build with the LLM Pulse API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue LLM Pulse into your daily workflow
- Pull a digest of ranking changes into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell LLM Pulse reporting at scale
- White-label LLM Pulse data into client-branded dashboards
- Run scheduled multi-account reports without logging into the LLM Pulse UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for LLM Pulse
- Real-time sync into your warehouse on a cron
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for LLM Pulse data older than the dashboard exposes
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- 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.
Agent-readiness verdict
A clean, well-documented REST API that returns all visibility data as JSON, with Bearer auth, a 300 req/min limit and a Postman collection. The main limitation is access: it is gated to the €299 Scale tier. Strong 8 out of 10 for API agent-readiness, helped by the fact the MCP server covers most agent needs on cheaper plans.
LLM Pulse API FAQ
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Does LLM Pulse have a public API?+
Sources
- LLM Pulse official site: https://llmpulse.ai
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.