v1 · OpenAPI 3.0.3

SEOLadders Docs

The whole platform, programmatically — topical authority, content writing and publishing, AI-visibility tracking, audits and automation. Use it the agentic way — an MCP server + skill that let Claude, Cursor and any agent run your SEO — or build directly against the REST API and webhooks. Same backend that powers the dashboard.

Two ways in

Everything runs on one backend, so both paths do the same things. Pick by how you build:

1. The agentic way (recommended)

  • MCP Server + Skill — the whole platform as drop-in tools over Model Context Protocol, for Claude Code, Cursor, Windsurf, ChatGPT, or any agent. Pair the MCP with the SEOLadders skill for guided /seoladders-* commands and full workflows — the agent runs the entire SEO loop for you. Set up the MCP →

2. Build it yourself (direct)

  • REST API — you call us. Bearer-token authenticated, versioned at /v1, fully described by the OpenAPI spec.
  • Webhooks — the push side of the same API: we call you. Signed (HMAC-SHA256) event deliveries when articles finish generating, optimizations complete, or batch jobs finish.

What you can do

The MCP and REST API both expose the whole platform, grouped the same way it's grouped in the dashboard:

  • Topical authority — build topic clusters (a pillar plus its supporting keywords) and track the AI prompts under each one, with live coverage rollups
  • Research — keyword discovery and competitor-gap analysis, live Google rankings, Search Console performance, and technical site audits
  • Content — generate expert articles from a keyword or a raw topic, list your posts, manage the content calendar and knowledge base, and surface pages worth acting on with Content Radar
  • Publishing — publish ready articles to your connected CMS (WordPress) or any HTTPS endpoint via webhook, and optimize any URL against the live top-5 SERP
  • AI visibility (GEO) — your score across ChatGPT, Perplexity, Gemini, Claude and Google AI, plus citations, sentiment, sources, content gaps, tracked prompts and competitors
  • Autopilot — recommended actions, plus toggles for AutoBlog calendar auto-refill and auto-publish to your CMS

Authentication

All endpoints require a bearer token in the Authorization header:

Authorization: Bearer sk_live_••••••••••••••••

Generate API keys on the Developers page inside the dashboard. Keys can be rotated and revoked at any time.

Base URL

https://www.seoladders.com/api/v1

Localhost development uses http://localhost:3000/api/v1. The OpenAPI spec at /api/openapi.json adapts the server URL based on the request origin.

Rate limits & quotas

Each surface (article generation, keyword research, optimization) has a per-month quota tied to your subscription tier. When a surface's quota is exhausted, calls to it return 429 Too Many Requests with a rate_limited error body. Track your remaining quota on the Usage & billing page. Full details in Authentication.

Where next?