Compatibility routes and plugin boundaries

Review historical entries, dynamic plugin routes, and documentation coverage.

This page records path differences outside the curated contracts. Prefer an endpoint with a complete reference and example instead of guessing compatibility by substituting path segments.

Registered entry	Usage and boundary
GET /v1beta/models	Gemini model catalog shape; use a gateway token in x-goog-api-key or Bearer
GET /v1beta/openai/models	OpenAI catalog shape; does not relocate all OpenAI resources under this prefix
GET /v1/models	x-api-key plus anthropic-version selects Claude; x-goog-api-key or key selects Gemini; ordinary Bearer selects OpenAI. Prefer headers over query credentials
GET /v1/models/{model}	Claude header combination selects Claude details, otherwise OpenAI; not a Gemini model detail alias
POST /v1/models/*path	Compatibility prefix for Gemini actions; examples use /v1beta/models/{model}:action
POST /v1/engines/{model}/embeddings	Historical entry uses the Gemini relay format; not a promised transparent OpenAI embeddings alias. Use explicit embedding endpoints
POST /v1/video/generations, GET /v1/video/generations/{task_id}	Historical video entries depend on plugin bindings and adaptors; response shapes are not interchangeable with /v1/videos
POST /v1/edits	Legacy path enters the image relay format; not a current text-edit API or a universal alias of /v1/images/edits
POST /pg/chat/completions	Session-authenticated Playground; external applications use /v1/chat/completions

Native plugin routes

Enabled plugins register provider protocol paths through meta.routes. JSON / form / multipart requests, response fields, and query paths depend on each plugin. Use gateway Bearer credentials. Paths may have provider prefixes; replacing the provider hostname is insufficient. Obtain the plugin key, version, model, actual routes, and a valid request from the operator. An installed plugin list is not a guarantee for every deployment.

Native routes differ from /v1/tasks/{plugin_key}: native routes run native decoders and presenters, while the latter is a legacy generic entry for normalized JSON. A third surface consists of host protocols /v1/responses, /v1/images/*, and /v1/videos, explicitly claimed by plugins. Responses sync / stream / background support is declared separately.

Use returned IDs with tasks for status and artifacts. Retrieval is not guaranteed for discarded results. Private provider IDs, dashboard database row IDs, and public task IDs are not interchangeable. There is no uniform webhook guarantee; use bounded polling.

Coverage checks

scripts/route-coverage.json inventories core relay, video, task, and host protocol routes with links to bilingual references or explicit boundaries. In the main repository, check:content compares route declarations and fails on additions or removals to prompt mapping updates. After export to a standalone docs repository, it still checks inventory/page links but explicitly skips source comparison when backend files are absent. It does not prove complete DTO, plugin, or runtime compatibility.

See API coverage for unimplemented features. Management APIs, organizations, account authentication, and plugin authoring are outside inference integration documentation.

阅读中文版

Prompt caching · Reasoning models · Context management