Skip to content
WP EngineDocumentation

Overview

AI Gateway 0.15

Section titled “AI Gateway 0.15”

An OpenAI-compatible API gateway that routes chat completion and image generation requests to multiple upstream AI providers (OpenAI, Google Gemini, Anthropic) based on the model prefix in the request.

Information

  • OpenAPI version: 3.0.3

Operations

Section titled “Operations”
GET
/v1/models
GET
/v1/models/{owner}/{model}/schema
POST
/v1/chat/completions
POST
/v1/messages
POST
/v1/messages/count_tokens
POST
/v1/images/generations
POST
/v1/images/alt-text
POST
/v1/content/summarize
POST
/v1/content/suggest-taxonomy
POST
/v1/audio/speech
POST
/v1/audio/transcriptions
GET
/v1/analytics
GET
/v1/credits
POST
/v1/sites
GET
/v1/sites/{client_id}
DELETE
/v1/sites/{client_id}
PATCH
/v1/sites/{client_id}
POST
/v1/sites/{client_id}/heartbeat
GET
/v1/mcp
POST
/v1/mcp
DELETE
/v1/mcp
GET
/v1/kb/collections
POST
/v1/kb/collections
GET
/v1/kb/collections/{id}
DELETE
/v1/kb/collections/{id}
PATCH
/v1/kb/collections/{id}
POST
/v1/kb/collections/{id}/documents
POST
/v1/kb/collections/{id}/documents/bulk
GET
/v1/kb/collections/{id}/documents/{documentID}
DELETE
/v1/kb/collections/{id}/documents/{documentID}
POST
/v1/kb/collections/{id}/search
GET
/v1/agents
POST
/v1/agents
GET
/v1/agents/{agent_id}
DELETE
/v1/agents/{agent_id}
PATCH
/v1/agents/{agent_id}
GET
/v1/sessions
POST
/v1/sessions
GET
/v1/sessions/{session_id}
DELETE
/v1/sessions/{session_id}
PATCH
/v1/sessions/{session_id}
POST
/v1/sessions/{session_id}/archive
GET
/v1/sessions/{session_id}/events
POST
/v1/sessions/{session_id}/events

Authentication

Section titled “Authentication”

bearerAuth

Section titled “bearerAuth”

Accepts three token types: (1) JWT access token verified against the configured JWKS endpoint; (2) WP Engine API key (prefixed “wpe_”); (3) browser session token (prefixed “wpbs_”) — short-lived tokens minted for browser clients via POST /v1/browser/client_secret. Per-route permission checks apply to API keys and browser session tokens; some management endpoints are JWT-only, while agents, sessions, and events also accept an API key scoped to a project. A WordPress site access token must carry the scope “urn:wpengine:wordpress”; the pre-URN spelling “wpengine:wordpress” is also accepted, so sites registered before the rename continue to work without re-registering. A token carrying neither is rejected with 403.

Security scheme type: http

internalServiceAuth

Section titled “internalServiceAuth”

Google-issued ID token for an authorized service account.

Security scheme type: http

Bearer format: JWT

anthropicApiKey

Section titled “anthropicApiKey”

WP Engine API key sent via the Anthropic SDK convention. Equivalent to presenting the same key as a bearer token. Supported only on the /v1/messages endpoints.

Security scheme type: apiKey

Header parameter name: x-api-key