Skip to main content
The Scope3 Agentic API is built from the ground up for AI agents. Both humans and agents share the same surface: a REST API and a generic MCP wrapper that exposes the entire surface through three tools — no per-domain tool sprawl, no SDK, no glue code.

​
Why agent-first

Same surface for humans and agents

REST and MCP expose an identical featureset against the same OpenAPI — no parallel “AI surface” to drift out of sync. See Philosophy for the SESOFI pattern (Single Endpoint, Single Object, Full Intent) that keeps composite intents legible.

Generic MCP wrapper

Three tools (health, ask_about_capability, api_call) cover every endpoint. Adding a new REST endpoint instantly makes it agent-callable — no new MCP tool to write, register, or deploy.

Declarative tool surface

A single skill.md URL teaches an agent the entire API. ask_about_capability queries it on demand, so agents discover endpoints instead of memorizing them.

Role-aware

Buyer and storefront roles each get their own skill file and OpenAPI spec, so agents see only the surface relevant to the caller.

​
Supported AI agents

  • Claude (Claude.ai Team/Enterprise, Claude Desktop, Claude Code)
  • ChatGPT (MCP Connectors and Custom GPTs)
  • Cursor
  • Custom agents — anything that speaks MCP or HTTP
Per-agent setup details are below; the Quickstart is a one-page index that links here.

​
Connection Methods

​
REST API

Standard HTTP REST API for traditional integrations:
EnvironmentBuyer Base URLStorefront Base URL
Productionhttps://api.agentic.scope3.com/api/buyerhttps://api.agentic.scope3.com/api/storefront
Staginghttps://api.agentic.staging.scope3.com/api/buyerhttps://api.agentic.staging.scope3.com/api/storefront

​
MCP (Model Context Protocol)

For AI agent integrations using JSON-RPC 2.0:
EnvironmentBuyer MCP EndpointStorefront MCP Endpoint
Productionhttps://api.agentic.scope3.com/mcp/buyerhttps://api.agentic.scope3.com/mcp/storefront
Staginghttps://api.agentic.staging.scope3.com/mcp/buyerhttps://api.agentic.staging.scope3.com/mcp/storefront
These URLs always resolve to the latest stable API version.

​
Available MCP Tools

Each MCP endpoint exposes exactly three tools:
ToolPurpose
healthCheck API health and verify connectivity
ask_about_capabilityQuery the skill documentation to discover endpoints and their schemas
api_callMake authenticated REST API calls to any endpoint
Workflow: an agent first uses ask_about_capability to learn what endpoints exist, then uses api_call to execute them.

​
Connecting AI Agents

​
Claude Connector (Claude.ai Team / Enterprise)

This is the recommended way to connect Claude to Scope3. It provides OAuth-based authentication and works across both Claude.ai (browser) and Claude Desktop automatically.
Admin Setup (one-time):
  1. Go to claude.ai → Admin Settings → Integrations → MCP Connectors
  2. Click Add Connector
  3. Enter the MCP endpoint URL:
    • Production: https://api.agentic.scope3.com/mcp/buyer
    • Staging: https://api.agentic.staging.scope3.com/mcp/buyer
  4. Name it (e.g., “Scope3 Agentic API”)
  5. Save the connector — it is now available to all members in your organization
User Setup:
  1. Go to claude.ai → Settings → Integrations → MCP Connectors
  2. Find the Scope3 connector and click Connect
  3. Log in with your Scope3 credentials when prompted (OAuth)
  4. Start chatting! Ask Claude: “List my advertisers” or “Create a performance campaign”
Once connected via the connector, it works in both Claude.ai (browser) and Claude Desktop. No separate configuration needed.

​
Claude Desktop (Personal / Manual Setup)

If you don’t have a Claude Team or Enterprise plan, you can connect Claude Desktop directly using an API key. Edit your Claude Desktop config file:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "scope3-buyer": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.agentic.scope3.com/mcp/buyer"],
      "env": {
        "SCOPE3_API_KEY": "your-api-key-here"
      }
    }
  }
}
Restart Claude Desktop after saving.

​
Claude Code (CLI)

# Add the production MCP server
claude mcp add --transport http scope3-buyer https://api.agentic.scope3.com/mcp/buyer

# Set your API key
export SCOPE3_API_KEY="your-api-key-here"

# Start Claude Code
claude
Then ask: “Use ask_about_capability to learn how to list advertisers, then use api_call to list them”

​
ChatGPT

Important: ChatGPT MCP connectors use OAuth authentication only. Custom headers like x-scope3-api-key are not supported. Authentication is handled automatically through the OAuth login flow.
Connect ChatGPT to Scope3 via MCP:
  1. Go to ChatGPT → Settings → MCP Connectors
  2. Click Add Connector
  3. Enter MCP Server URL: https://api.agentic.scope3.com/mcp/buyer
  4. Select OAuth as the authentication method
  5. Complete the Scope3 login flow when prompted
  6. Once connected, you’ll have access to 3 tools:
    • health - Check API status
    • ask_about_capability - Learn about available endpoints
    • api_call - Make authenticated API calls
  7. Test with: “Use ask_about_capability to learn how to list advertisers”

​
Cursor

Configure Cursor with the Scope3 MCP server:
  1. Open Cursor Settings → MCP tab
  2. Add a new MCP server:
    • Name: scope3
    • URL: https://api.agentic.scope3.com/mcp/buyer
    • Headers: Authorization: Bearer your-api-key
  3. Restart Cursor
  4. In chat, ask: “Use Scope3 tools to list advertisers”

​
Authentication

Use OAuth for Claude/ChatGPT MCP connectors (handled automatically) or an API key (Authorization: Bearer scope3_...) for CLIs, Cursor, and custom agents. See Authentication for full details.

​
Notifications

The API surfaces unread notifications inline in ask_about_capability responses, so agents can proactively flag campaign or creative issues to users. See the Notifications guide for setup and the REST endpoints.

​
Next Steps

Quickstart

Connect Claude, ChatGPT, Cursor, or a custom agent in minutes.

Buyer Onboarding

The end-to-end campaign-launch journey for buyer integrations.

Skill

What skill.md is and how agents use it for capability discovery.

Authentication

API keys, OAuth, and SSO configuration.