Runloop · Schema

Runloop Gateway Config

A GatewayConfig defines a configuration for proxying API requests through the agent gateway. It specifies the target endpoint and how credentials should be applied.

Artificial IntelligenceAI AgentsCoding AgentsSandboxesDevboxesCode ExecutionEvaluationBenchmarksSWE-BenchMCPSnapshotsMicroVMEnterpriseSOC 2

Properties

Name Type Description
id string The unique identifier of the GatewayConfig.
account_id string The account ID that owns this config.
name string The human-readable name of the GatewayConfig. Unique per account (or globally for system configs).
endpoint string The target endpoint URL (e.g., 'https://api.anthropic.com').
auth_mechanism object How credentials should be applied to proxied requests.
description string Optional description for this gateway configuration.
create_time_ms integer Creation time of the GatewayConfig (Unix timestamp in milliseconds).
View JSON Schema on GitHub

JSON Schema

runloop-gateway-config-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/runloop-ai/main/json-schema/runloop-gateway-config-schema.json",
  "title": "Runloop Gateway Config",
  "description": "A GatewayConfig defines a configuration for proxying API requests through the agent gateway. It specifies the target endpoint and how credentials should be applied.",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "id": {
      "type": "string",
      "description": "The unique identifier of the GatewayConfig."
    },
    "account_id": {
      "type": "string",
      "nullable": true,
      "description": "The account ID that owns this config."
    },
    "name": {
      "type": "string",
      "description": "The human-readable name of the GatewayConfig. Unique per account (or globally for system configs)."
    },
    "endpoint": {
      "type": "string",
      "description": "The target endpoint URL (e.g., 'https://api.anthropic.com')."
    },
    "auth_mechanism": {
      "$ref": "#/$defs/AuthMechanismView",
      "description": "How credentials should be applied to proxied requests."
    },
    "description": {
      "type": "string",
      "nullable": true,
      "description": "Optional description for this gateway configuration."
    },
    "create_time_ms": {
      "type": "integer",
      "format": "int64",
      "description": "Creation time of the GatewayConfig (Unix timestamp in milliseconds)."
    }
  },
  "required": [
    "id",
    "name",
    "endpoint",
    "auth_mechanism",
    "create_time_ms"
  ],
  "$defs": {
    "AuthMechanismView": {
      "type": "object",
      "additionalProperties": false,
      "description": "Defines how credentials are applied to HTTP requests when proxying through the gateway.",
      "properties": {
        "type": {
          "type": "string",
          "description": "The type of authentication mechanism: 'header', 'bearer'."
        },
        "key": {
          "type": "string",
          "nullable": true,
          "description": "For 'header' type: the header name (e.g., 'x-api-key')."
        }
      },
      "required": [
        "type"
      ]
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/runloop-gateway-config"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.