SEOforGPT Developers

    Use the Public API v1 for scripts and CI, or point an MCP-capable assistant at our hosted MCP URL (Claude is the primary documented path). We do not ship a separate ChatGPT-only MCP. The same endpoint is for any client that supports remote MCP. Machine-readable specs and API keys are linked below.

    Public API v1

    REST base: https://www.seoforgpt.io/api/v1. Authenticate with Authorization: Bearer and a session JWT or user API key (sgpt_…).

    API documentation

    OpenAPI

    Parseable OpenAPI 3 description of Public API v1 for codegen, agents, and contract checks. Same endpoints as the interactive docs.

    openapi.json

    Hosted MCP

    One connector URL for MCP clients we support today, with docs focused on Claude: https://www.seoforgpt.io/mcp. OAuth sign-in; tools map to the same product capabilities as the app.

    MCP & Claude setup

    Agent context

    /llms.txt and /index.md summarize the product for crawlers and assistants. Discovery metadata lives under /.well-known/.

    llms.txt

    Claude (MCP), ChatGPT / OpenAI, and the REST API

    Claude can use the same product surface as the app through hosted MCP at https://www.seoforgpt.io/mcp with OAuth. Tools match the app. You are not calling raw OpenAPI from chat. We document this path step by step.

    OpenAI has been adding MCP-style connectors and remote MCP server URLs in some ChatGPT and API surfaces; availability varies by product, region, and account. If the surface you are using asks for an MCP server URL, use the same address as above. We do not maintain different MCP endpoints per vendor. If that surface only accepts HTTP actions or you prefer a schema import, use a Custom GPT Action (or equivalent). Use the publicly reachable schema URL https://www.seoforgpt.io/openapi.json in tools that fetch from the internet. On this site you can also open openapi.json in a new tab. Use Bearer auth and a user API key (sgpt_…) or session JWT as appropriate. See OpenAI’s current Platform docs on MCP and apps for what their UI accepts today.

    /.well-known/ai-plugin.json is legacy discovery metadata for crawlers; it does not register a live ChatGPT plugin by itself.

    Quick reference

    • List projects: GET /api/v1/projects
    • Run saved visibility: POST /api/v1/analyze/project with projectId
    • Reports: GET /api/v1/reports/latest?projectId=… and GET /api/v1/reports/:id?view=summary|full|raw
    • API keys (JWT only): POST|GET|DELETE /api/v1/keys
    • Errors: JSON envelope with code, message, optional details, and request_id.