That Marketing Buddy
Home/API/ChatSEO
ChatSEO

ChatSEO API

Yes. ChatSEO publishes a public REST API.

MCP also available
Public REST API documentedAgent-readiness 6/10
Data from Buddy's database, auto-rechecked weekly

What is the ChatSEO API?

ChatSEO offers REST API access bundled with its MCP server on the Pro plan and above. The API is positioned as part of the agent and integrations story rather than as a separate, standalone data product, so it is meant for wiring ChatSEO into your own tools and workflows rather than reselling raw SEO data.

Because ChatSEO sits on top of Google Search Console and Google Analytics, the underlying SEO data you most care about already lives in Google's own APIs, which you own and control. ChatSEO's API surface is more about driving the product (sites, conversations, projects, todos, integrations and artifacts) than exporting a proprietary index.

The access caveat matters: API access unlocks on the Pro tier (€49/month) alongside the MCP server. The €29 Starter plan is dashboard-only, so if programmatic access is the reason you want ChatSEO, budget for Pro.

For the broader picture: ChatSEO review, full pricing breakdown, .

HOOK IT TO YOUR STACK

Real ChatSEO API calls you'll write

chatseo-apirest
#Get the top organic keywords for a domain
GET/v3/site-explorer/organic-keywords?target=mysite.com&limit=10
200 OK · 10 results
marketing automationpos 4 · vol 12.4k
email marketing softwarepos 6 · vol 8.9k
seo tools 2026pos 8 · vol 6.3k
best crm small businesspos 12 · vol 4.6k
Cron daily to track ranking shifts.
chatseo-apirest
#Pull a competitor's backlink profile
GET/v3/site-explorer/backlinks?target=rival.com&limit=100
200 OK · 100 backlinks
Referring domains1,847
Domain Rating78
New backlinks (30d)+142
Lost backlinks (30d)-38
Pipe into a weekly Slack report.
chatseo-apirest
#Trigger a fresh site audit
POST/v3/site-audit/scan
202 Accepted · scan_id: 7f2a
Statusqueued
Estimated finish~4 min
Webhook callbackconfigured
Last scan issues47 (12 critical)
TMB SCORE FOR ChatSEOAgent fit: 6/10
Read review →

Endpoints illustrative. Confirm exact paths against the live API docs before integrating.

Pricing, limits, and integration

ChatSEO's REST API and MCP server are included with the SaaS subscription rather than sold separately, but both are gated by tier. They unlock on the Pro plan (€49/month) and above; the €29 Starter plan is dashboard-only. There is no separate per-call API fee, but the product itself is credit-based, where one credit equals one message, so agent-driven usage that sends many messages will consume credits.

Authentication for the MCP server is OAuth 2.1 with Protected Resource Metadata (RFC 9728) and automatic client bootstrap, issuer https://api.chatseo.app/auth, so most clients can connect with a URL and a sign-in rather than a manually managed key. Tool calls run against organizations, sites, conversations, projects, todos, integrations and artifacts, with send_message as the main entrypoint.

For most agent use cases the MCP server is the better path than the raw REST API: it is the documented, first-class way ChatSEO expects agents to connect, with clean OAuth and 34 ready tools. Reach for the REST API when you need to script ChatSEO from your own backend outside an MCP client. Either way, plan for the Pro tier and keep an eye on credit consumption, since every message an agent sends counts.

How much does the ChatSEO API actually cost?

Verify on docs

ChatSEO 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

API docs
—
Auth method
—
SDK languages
—
OpenAPI spec
—
Webhooks
not available
Structured outputs
—

Which AI clients can read ChatSEO data?

Not every AI assistant supports MCP natively. Here's the per-client picture for ChatSEO specifically.

ClientSupportNotes
Claude (Desktop/Web)Native MCPAdd the MCP server URL and authenticate via OAuth; no API key to paste. Requires the Pro plan.
Claude CodeNative MCPConnects to the hosted MCP server over OAuth; full access to the 34 tools on Pro and up.
ChatGPTNative MCPListed as a supported MCP client; OAuth sign-in, Pro plan required.
CursorNative MCPNative MCP support; add the server and sign in once.
vscodeNative MCPWorks via GitHub Copilot's MCP support in VS Code.

ChatSEO also has an MCP server

If you're wiring ChatSEO into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.

See ChatSEO MCP page

What you can build with the ChatSEO API

Three personas, three different shapes of build. Pick the row that matches how you actually ship.

SOLO DEV / FOUNDER

Glue ChatSEO 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
Effort: A weekend, one Node or Python script
AGENCY / CONSULTANT

Sell ChatSEO reporting at scale

  • White-label ChatSEO data into client-branded dashboards
  • Run scheduled multi-account reports without logging into the ChatSEO UI
  • Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Effort: 1-2 weeks, hits multi-tenant auth quickly
IN-HOUSE ENGINEER

Production pipelines for ChatSEO

  • Real-time sync into your warehouse on a cron
  • Custom alerts the dashboard's built-in alerting can't express
  • Backfill + idempotency handling for ChatSEO data older than the dashboard exposes
Effort: Multi-week project, expect rate-limit tuning

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.
6/10

Agent-readiness verdict

A REST API bundled with the Pro plan, aimed at integration and agent use rather than raw data export. It is gated to the €49 Pro tier and there is no cheaper API-only option, but for most agent use cases the MCP server is the better path anyway. A fair 6 out of 10 for API agent-readiness.

ChatSEO API FAQ

Should I use the API or the MCP server for Claude / Cursor / Codex?+
Prefer the MCP server for agent workflows — it's less code and pre-handles auth flows. Use the REST API for scheduled jobs, dashboards, and anything outside an LLM-driven flow.
Does ChatSEO have a public API?+
Not documented publicly as of the last check. Some tools expose private/partner APIs — contact sales if you need programmatic access.

Sources

Joonas Rotko
Joonas RotkoAuthor & Founder of That Marketing Buddy

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.

About meHow I review

ChatSEO

Try ChatSEO