Want a free personalized recommendation for your software stack?Get yours
That Marketing Buddy
Home/API/Search Atlas
Search Atlas

Search Atlas API

Yes. Search Atlas publishes a public REST API.

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

What is the Search Atlas API?

Search Atlas exposes a v2 REST API that covers its full platform surface, the same hosted v2 that the official MCP server bridges to. That means programmatic access is first-class rather than a bolted-on afterthought, and the breadth (SEO, PPC, content, local, PR, LLM visibility) is unusually wide for an SEO tool.

Authentication is by token or API key: a SEARCHATLAS_TOKEN (a JWT) or a SEARCHATLAS_API_KEY. In practice the token is obtained through a browser login today rather than a self-serve API-key dashboard with OAuth, which is the main friction for a clean programmatic setup.

Because the same hosted v2 surface powers both the REST API and the MCP server, an integration can choose either path: raw REST for custom backends, or MCP for agent-driven use. For most agent use cases the MCP server is the faster route, since it surfaces the whole tool catalogue automatically.

For the broader picture: Search Atlas review, full pricing breakdown, .

HOOK IT TO YOUR STACK

Real Search Atlas API calls you'll write

searchatlas-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.
searchatlas-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.
searchatlas-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 Search AtlasAgent fit: 9/10
Read review →

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

Pricing, limits, and integration

API and MCP access come with the SaaS subscription rather than as a separate product, and scale with the plan you are on (OTTO projects, keywords, seats and content pages). Pricing is public: Starter $99/mo, Growth $199/mo, Pro $399/mo and Agency $999/mo, with 20% off annual and a 7-day trial.

There is no separate metered API price list surfaced publicly; usage is governed by your plan's quotas rather than per-call billing. Authentication is by token or API key, and the same hosted v2 surface backs both the REST API and the MCP server, so limits apply consistently across both paths.

For agent use, the MCP server is the primary path because it exposes the full ~587-tool catalogue automatically. Plan for the token-from-browser-login step during setup, and size your plan by how many sites (OTTO projects) and content pages you need, since those are the limits that bite first.

How much does the Search Atlas API actually cost?

Verify on docs

Search Atlas 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 Search Atlas data?

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

ClientSupportNotes
Claude (Desktop/Web)fullConnects to the official hosted MCP server (Streamable-HTTP, or the npm stdio bridge). ~587 tools available once a token is configured.
Claude CodefullWorks via the same official MCP server. Token or API-key auth (SEARCHATLAS_TOKEN / SEARCHATLAS_API_KEY).
CursorfullMCP-compatible; connect to mcp.searchatlas.com with a configured token.
n8nAPI-only (custom code)Drive via the v2 REST API (or an MCP node where supported). Token / API-key auth.

Search Atlas also has an MCP server

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

See Search Atlas MCP page

What you can build with the Search Atlas API

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

SOLO DEV / FOUNDER

Glue Search Atlas 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 Search Atlas reporting at scale

  • White-label Search Atlas data into client-branded dashboards
  • Run scheduled multi-account reports without logging into the Search Atlas 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 Search Atlas

  • Real-time sync into your warehouse on a cron
  • Custom alerts the dashboard's built-in alerting can't express
  • Backfill + idempotency handling for Search Atlas 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.
9/10

Agent-readiness verdict

A broad, first-class v2 REST API that covers the entire platform and underpins the official MCP server. The only knock is that obtaining the token runs through a browser login rather than a self-serve OAuth/API-key flow. A strong 9 out of 10 for API agent-readiness.

Search Atlas 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 Search Atlas 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.

Search Atlas

Try Search Atlas
WEEKLY NEWSLETTER

The marketing tools worth your money, scored for AI agent readiness

Every week I score the tools for MCP, API, and agent-readiness, then email you the ones that actually deliver, what plugs into Claude and Cursor, the pricing changes, and what to skip. No fluff, no daily spam.

Join for free. One email a week, unsubscribe anytime.