--- title: "Developer Documentation: REST API, MCP Server, CLI & OpenAPI | SEOPro AI" description: "SEOPro AI developer docs for REST API v1, MCP server, CLI, OpenAPI, auth, rate limits, agent skills, and support." url: https://seoproai.co/developers --- # SEOPro AI developer documentation Use this page as the canonical developer and agent entry point for SEOPro AI. It covers the versioned REST API, MCP server, API keys, OAuth discovery, CLI usage, free tools, rate limits, manifests, and support paths. ## Quick start Create an API key in Settings -> API keys, store it outside prompts as SEOPROAI_API_KEY, then test the REST API with curl. The first REST call should be GET https://api.seoproai.co/api/v1/websites because it returns the numeric website_id required by most website-scoped operations. - curl -H "Authorization: Bearer sk_..." https://api.seoproai.co/api/v1/websites - API keys are created at https://seoproai.co/settings?tab=api-keys; no sales contact is required. - Browser dashboard calls use the signed-in session. Third-party clients should use API keys or OAuth, not the browser-only X-User-Id header. ## Authentication and scopes Programmatic REST clients send Authorization: Bearer sk_your_api_key. API keys expose the enforced write scopes blogs:generate and blogs:publish: blogs:generate is required for generating articles or keyword plans, and blogs:publish is required for publishing. Read operations are governed by organization membership rather than read scopes, so a valid key can read resources in the organization it belongs to. - Self-serve key creation endpoint for the browser session: POST https://api.seoproai.co/api/v1/keys (browser session). - Key usage endpoint: GET https://api.seoproai.co/api/v1/keys/{key_id}/usage. - OAuth metadata starts at https://api.seoproai.co/.well-known/oauth-protected-resource/api/mcp; clients should use authorization code with PKCE S256 when they support OAuth. ## REST API The canonical REST base URL is https://api.seoproai.co/api/v1. The unversioned /api prefix remains a supported alias, but every new integration should document and call /api/v1. The OpenAPI document is https://api.seoproai.co/openapi.json, the API index is https://api.seoproai.co/api/v1, and the RFC 9727 API catalog is https://api.seoproai.co/.well-known/api-catalog. - Website list: GET https://api.seoproai.co/api/v1/websites. - Free tools: POST https://api.seoproai.co/api/v1/free-tools/{tool_name}/generate. - Use OpenAPI operation names and schemas rather than scraping dashboard pages. ## MCP server The hosted Streamable HTTP MCP endpoint is https://api.seoproai.co/api/mcp. Public discovery can call initialize, ping, tools/list, resources/list, resources/templates/list, prompts/list, and the public documentation resources without a credential. Tool calls that read or write account data require an API key or OAuth. - Initialize example: curl -X POST https://api.seoproai.co/api/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"agent","version":"1.0.0"}}}' - Well-known MCP discovery and handshake: https://api.seoproai.co/.well-known/mcp. - MCP server card: https://api.seoproai.co/.well-known/mcp/server-card.json. Registry manifest: https://api.seoproai.co/server.json. OAuth protected-resource metadata: https://api.seoproai.co/.well-known/oauth-protected-resource/api/mcp. - Public MCP resources: seopro://guide/getting-started (text/markdown), seopro://guide/tools (text/markdown), seopro://guide/workflows (text/markdown), seopro://guide/plans-and-limits (text/markdown), mcp://server-card.json (application/json). ## CLI The SEOPro AI CLI package is seoproai on npm. Install it with npm install -g seoproai, run one-off commands with npx seoproai, keep credentials in SEOPROAI_API_KEY, and add --json when an agent or script needs parseable output. - npx seoproai websites list --json - npx seoproai websites stats --json - npx seoproai search summary|keywords|trends|ai-traffic --json - npx seoproai keywords plan|generate --json - npx seoproai articles list|status|generate --json - npx seoproai articles get|publish --json - npx seoproai backlinks profile --json - npx seoproai indexing status|request --json - npx seoproai audit --json - npx seoproai ai-citations --json - npx seoproai free-tools run (no key needed) --json - npx seoproai api index --json ## Free tools without an account 16 AI tools run without an account or an API key, over the same public REST endpoints the site uses. Anonymous clients get 5 runs per day, free account users get 15 per day, and paid plans are not daily-capped for these tools. - Endpoint: POST https://api.seoproai.co/api/v1/free-tools/{tool_name}/generate. - Remaining quota: GET https://api.seoproai.co/api/v1/free-tools/rate-limit. - Browser hub: https://seoproai.co/tools. ## Rate limits Anonymous API clients are limited to 600 requests per 60 seconds per client IP. API keys also carry hourly, daily, and monthly quotas. Every /api response includes RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, RateLimit-Policy and the X-RateLimit-* aliases; a 429 response includes Retry-After. - Inspect key usage at https://api.seoproai.co/api/v1/keys/{key_id}/usage. - Headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, RateLimit-Policy, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, Retry-After. ## Versioning and deprecation SEOPro AI uses semver API versions and puts the current version in the path at /api/v1. The /api alias remains supported, but agent-facing documentation should prefer /api/v1. Deprecated operations are marked in OpenAPI and return Deprecation, Sunset, Link; rel="deprecation" for at least 90 days before removal, following https://www.rfc-editor.org/rfc/rfc8594. ## Agent skill and manifests Agent instructions live at https://seoproai.co/.well-known/agent-skills/index.json and https://seoproai.co/.well-known/agent-skills/seopro-ai/SKILL.md. Agents should also read https://seoproai.co/llms.txt, https://seoproai.co/llms-full.txt, https://seoproai.co/.well-known/agents.json, https://seoproai.co/.well-known/agent-permissions.json, and https://seoproai.co/.well-known/mcp.json before acting. ## Support and contact For implementation help, contact hi@seoproai.co, call +1-510-342-5413, read the help center at https://seoproai.featurebase.app/help, or use the contact page at https://seoproai.co/contact. Human users can compare plan allowances at https://seoproai.co/pricing and try account-free tools at https://seoproai.co/tools. ## Machine-readable entry points - Agent index: https://seoproai.co/llms.txt - Full text of every public page: https://seoproai.co/llms-full.txt - MCP server: https://api.seoproai.co/api/mcp - OpenAPI description: https://api.seoproai.co/openapi.json