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

# API coverage

> Distinguish implemented routes, deployment-dependent capabilities, and unavailable features.

This page checks public integration scope against the current source. **Route registration, channel support, model capabilities, and token permissions are separate requirements.** “Provided” means a route and handler exist, not that every model supports the feature.

## Documented integrations

| Capability | Reference and guide | Scope |
| - | - | - |
| Model discovery | [List](/en/api-reference/models), [retrieve](/en/api-reference/model-retrieve) | Metadata; check business errors inside HTTP 200 |
| Conversation applications | [Chat](/en/api-reference/chat-completions), [Responses](/en/api-reference/responses) | Text, SSE, tools, structured output, and images depend on the model |
| Native protocols | [Claude](/en/guides/native-claude), [Gemini](/en/guides/native-gemini) | Text, SSE, and client tools, not the entire provider API |
| Images, audio, video | [Images](/en/guides/image-generation), [speech](/en/guides/speech), [transcription](/en/guides/speech-to-text), [video](/en/guides/video-generation) | Separate models and channel capabilities; task and synchronous APIs differ |
| Retrieval | [Embeddings](/en/guides/embeddings), [Rerank](/en/guides/rerank), [RAG](/en/guides/rag) | Vectors, ranking, and application orchestration; no hosted knowledge base |
| Moderation | [Moderations](/en/guides/moderations) | Common text contract; verify channel field preservation |
| Context compaction | [Compaction](/en/guides/compaction) | Separate non-streaming request requiring a compatible upstream |
| Plugin task responses | [Background and retrieval](/en/guides/background-responses) | Host task responses, not arbitrary upstream response IDs |
| Bidirectional connections | [WebSocket integration](/en/guides/websocket) | Responses and Realtime use different protocols |

## SDK features you cannot assume

| Feature | Current boundary | Application choice |
| - | - | - |
| Files upload, list, download, delete | `/v1/files` routes use an unimplemented handler | Use supported URL / Base64 image inputs and endpoint-specific audio uploads, not Files first |
| Image variations, model deletion, legacy fine-tunes | Explicitly unimplemented | Use documented generation / editing or a separate service provided by the administrator |
| Claude count\_tokens | Route disabled | Local estimates may guide budgets, but do not guarantee actual usage |
| Gemini `/v1beta/models/{model}:countTokens` | Explicitly returns not found | A wildcard route does not imply support for every action |
| Arbitrary Responses ID retrieval | Only platform plugin task mappings are supported | Retain full history; retrieve plugin tasks using their returned IDs |
| Responses REST delete / cancel / input\_items | Not provided by the current router | Stopping client waiting does not cancel the upstream task |
| Assistants, Threads, Conversations resources, Vector Stores, Batch | No complete resource API in current public inference routing | Maintain history, retrieval, and batch queues in your application |
| Realtime WebRTC / temporary credentials / SIP | Cannot be inferred from the WebSocket route | Confirm a separate integration path; see WebSocket integration |

## Additional protocols and tasks

Coverage now includes [legacy Completions](/en/guides/legacy-completions), [native Gemini embeddings](/en/guides/gemini-embeddings), [tasks and artifacts](/en/guides/tasks), [Alpha Search](/en/guides/alpha-search), and [Midjourney](/en/guides/midjourney). Specialized search and plugin submission require deployment-specific request schemas, not an invented universal payload.

[Compatibility routes and plugin boundaries](/en/guides/protocol-compatibility) covers historical entries, model catalog protocol selection, dynamic native routes, and Playground differences. Management `/api/*` uses separate authentication and permissions and is outside these inference contracts. Local checks include a source route inventory; model support and real artifacts still require deployment acceptance.

## Review after upgrades

This review checked `router/relay-router.go`, `router/task-plugin-protocol-router.go`, `pkg/jsplugin/routing.go`, and relevant handlers at `30a6d88a4`. Plugin declarations and deployment settings affect availability. The site's [OpenAPI](/openapi/relay.json) is a curated contract with source revisions per operation, not automatic coverage of every route.

Start with [model capabilities](/en/guides/model-capabilities), then complete [production acceptance](/en/guides/production). The existence of an SDK method does not replace either step.

[阅读中文](/zh/guides/api-coverage)

## Topic audit against OpenRouter

This table checks developer integration topics against the [OpenRouter documentation index](https://github.com/OpenRouterTeam/docs/blob/main/docs.json). Local implementation and the actual channel determine support, not another platform's navigation.

| Topic | Local documentation and boundary |
| - | - |
| Sampling and token probabilities | [Generation parameters](/en/guides/generation-parameters): model support, filtering, and forced-formatting limits |
| PDFs and files | [File inputs](/en/guides/file-inputs): native inline input; no general file management or OCR fallback |
| Search and citations | [Web search](/en/guides/web-search): upstream native tools; alternatively client functions or deployment Alpha Search |
| Caching, reasoning, and long context | [Prompt caching](/en/guides/prompt-caching), [reasoning models](/en/guides/reasoning-models), and [context management](/en/guides/context-management) |
| Routing, fallbacks, and rate limits | [Model routing](/en/guides/model-routing) and [rate limits](/en/guides/rate-limits); no promise of OpenRouter provider ordering, models fallback arrays, or router syntax |
| SDKs, streams, structured output, and tools | [Example index](/en/guides/recipes): choose the actual protocol, not platform-specific plugin parameters |
| Images, speech, video, embeddings, and reranking | Existing bilingual guides and API references; model discovery does not establish every capability |
| Data policy and service tiers | [Data controls](/en/guides/data-controls): forwarding does not establish ZDR, training policy, or residency guarantees |
| Containers, hosted shell, MCP catalogs, response healing, general response cache | No gateway-wide server contract verified in this audit; not published as general capabilities. Application function tools and host task plugins are separate mechanisms |
| BYOK, account management, budgets, and OAuth | OpenRouter product APIs do not directly apply. Project management features require separate management API authentication and permission documentation, not inference-token assumptions |

The topic audit complements the source-route inventory: automation detects registered route changes but cannot prove parameter semantics or upstream compatibility.

## Remaining-topic audit in this pass

* Audio extends beyond TTS/STT: [Chat audio input](/en/guides/audio-input) now explains input and the limits of audio output and assistant audio-ID replay.
* Video generation does not cover understanding: [native Gemini video input](/en/guides/video-understanding) explains Chat video\_url parsing differences and Files/Interactions gaps.
* Text latency coverage adds [predicted outputs](/en/guides/predicted-outputs), describing the existing Chat prediction field without conversion or performance guarantees.
* [Troubleshooting](/en/guides/troubleshooting) adds media size/encoding, hidden SDK resource calls, ineffective parameters, and request-stop boundaries.

## Tool and output-control audit

[Tool controls](/en/guides/tool-controls) covers tool\_choice, explicit false, and conversion boundaries; [JSON mode](/en/guides/json-mode) adds json\_object examples in both protocols. Source inspection confirms function-tool strict is not copied by Chat ↔ Responses conversion. Guides and API references now document that boundary without backend changes or cross-protocol strict guarantees.

## Native server-tool audit

[Gemini built-ins](/en/guides/gemini-builtins) adds search grounding, URL retrieval status, and code execution parts. The native handler preserves raw response metadata; typed request re-serialization and protocol conversion are separate boundaries. This is conditional upstream support, not OpenRouter's cross-model search/fetch service.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.