> ## Documentation Index
> Fetch the complete documentation index at: https://docs.interchange.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Make API call via MCP

> Make REST API calls to any Buyer API endpoint through MCP.

## Parameters

- `method`: HTTP method (GET, POST, PUT, DELETE)
- `path`: API path (e.g., "/advertisers", "/campaigns/{id}")
- `body`: Request body for POST/PUT requests (optional)
- `query`: Query parameters (optional)

## Example: List Advertisers

```json
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "api_call",
    "arguments": {
      "method": "GET",
      "path": "/advertisers",
      "query": { "take": 10 }
    }
  }
}
```

## Example Response

```json
{
  "jsonrpc": "2.0",
  "id": 2,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{ \"advertisers\": [...], \"total\": 5 }"
      }
    ]
  }
}
```



## OpenAPI

````yaml /v2/buyer-api-v2.yaml post /api-call
openapi: 3.0.0
info:
  title: Scope3 Buyer API
  version: 2.0.0
  description: |-
    REST API for advertisers to manage advertisers, campaigns, and reporting.

    ## Authentication

    All endpoints require a Bearer token in the Authorization header:
    ```
    Authorization: Bearer your-api-key
    ```

    ## Base URL

    `https://api.interchange.io/api/v2/buyer`

    ## For AI Agents

    AI agents can use the MCP endpoint at `/mcp/v2/buyer` with three tools:
    - `initialize`: Start an MCP session
    - `api_call`: Make REST API calls
    - `ask_about_capability`: Learn about API features
servers:
  - url: https://api.interchange.io/api/v2/buyer
    description: Production server
security: []
tags:
  - name: Signup
    description: Request reviewed access to Interchange
  - name: Account
    description: Account management, service tokens, and preferences
  - name: Asks
    description: >-
      What you are waiting on Scope3 for — support, product, and supply asks in
      one list
  - name: Advertisers
    description: Manage advertisers
  - name: Product Discovery
    description: Discover and select products
  - name: Campaigns
    description: Manage advertising campaigns
  - name: Creatives
    description: Build, manage, and sync campaign creatives via AdCP Creative Protocol
  - name: Reporting
    description: Access performance metrics
  - name: Event Sources
    description: >-
      Manage event source configurations and log conversion/marketing events for
      attribution
  - name: Property Lists
    description: Validate property lists against AAO registry
  - name: Sales Agents
    description: View and connect sales agents
  - name: Measurement
    description: Measurement sources, records, context, and freshness
  - name: Syndication
    description: Syndicate resources to ADCP agents
  - name: Tasks
    description: Track async operation status
  - name: Buyer Billing
    description: >-
      Consolidated invoicing for buyers — invoices and pending invoice items
      issued by Scope3 across the buyer customer.
  - name: MCP
    description: Model Context Protocol endpoints for AI agents
paths:
  /api-call:
    servers:
      - url: https://api.interchange.io/mcp/v2/buyer
        description: Production MCP server
    post:
      tags:
        - MCP
      summary: Make API call via MCP
      description: |-
        Make REST API calls to any Buyer API endpoint through MCP.

        ## Parameters

        - `method`: HTTP method (GET, POST, PUT, DELETE)
        - `path`: API path (e.g., "/advertisers", "/campaigns/{id}")
        - `body`: Request body for POST/PUT requests (optional)
        - `query`: Query parameters (optional)

        ## Example: List Advertisers

        ```json
        {
          "jsonrpc": "2.0",
          "id": 2,
          "method": "tools/call",
          "params": {
            "name": "api_call",
            "arguments": {
              "method": "GET",
              "path": "/advertisers",
              "query": { "take": 10 }
            }
          }
        }
        ```

        ## Example Response

        ```json
        {
          "jsonrpc": "2.0",
          "id": 2,
          "result": {
            "content": [
              {
                "type": "text",
                "text": "{ \"advertisers\": [...], \"total\": 5 }"
              }
            ]
          }
        }
        ```
      operationId: mcpApiCall
      parameters:
        - name: mcp-session-id
          in: header
          required: true
          schema:
            type: string
            format: uuid
          description: MCP session identifier from the initialize call.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/McpApiCallRequest'
            example:
              jsonrpc: '2.0'
              id: 2
              method: tools/call
              params:
                name: api_call
                arguments:
                  method: GET
                  path: /advertisers
                  query:
                    take: 10
      responses:
        '200':
          description: API call executed successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/McpToolResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: 733d6489-8133-47a7-a8f6-ec5ea14f58e6
      security:
        - bearerAuth: []
components:
  schemas:
    McpApiCallRequest:
      type: object
      properties:
        jsonrpc:
          type: string
          enum:
            - '2.0'
          description: JSON-RPC version
        id:
          oneOf:
            - type: string
            - type: number
          description: Request ID
        method:
          type: string
          enum:
            - tools/call
          description: Method name
        params:
          type: object
          properties:
            name:
              type: string
              enum:
                - api_call
              description: Tool name
            arguments:
              type: object
              properties:
                method:
                  type: string
                  enum:
                    - GET
                    - POST
                    - PUT
                    - DELETE
                  description: HTTP method
                path:
                  type: string
                  description: API path (e.g., "/advertisers")
                body:
                  type: object
                  description: Request body for POST/PUT
                query:
                  type: object
                  description: Query parameters
              required:
                - method
                - path
          required:
            - name
            - arguments
      required:
        - jsonrpc
        - id
        - method
        - params
    McpToolResponse:
      type: object
      properties:
        jsonrpc:
          type: string
          enum:
            - '2.0'
        id:
          oneOf:
            - type: string
            - type: number
        result:
          type: object
          properties:
            content:
              type: array
              items:
                type: object
                properties:
                  type:
                    type: string
                    enum:
                      - text
                  text:
                    type: string
                    description: Response content
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: API key or access token

````