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, retrieve	Metadata; check business errors inside HTTP 200
Conversation applications	Chat, Responses	Text, SSE, tools, structured output, and images depend on the model
Native protocols	Claude, Gemini	Text, SSE, and client tools, not the entire provider API
Images, audio, video	Images, speech, transcription, video	Separate models and channel capabilities; task and synchronous APIs differ
Retrieval	Embeddings, Rerank, RAG	Vectors, ranking, and application orchestration; no hosted knowledge base
Moderation	Moderations	Common text contract; verify channel field preservation
Context compaction	Compaction	Separate non-streaming request requiring a compatible upstream
Plugin task responses	Background and retrieval	Host task responses, not arbitrary upstream response IDs
Bidirectional connections	WebSocket integration	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, native Gemini embeddings, tasks and artifacts, Alpha Search, and Midjourney. Specialized search and plugin submission require deployment-specific request schemas, not an invented universal payload.

Compatibility routes and plugin boundaries 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 is a curated contract with source revisions per operation, not automatic coverage of every route.

Start with model capabilities, then complete production acceptance. The existence of an SDK method does not replace either step.

阅读中文

Topic audit against OpenRouter

This table checks developer integration topics against the OpenRouter documentation index. Local implementation and the actual channel determine support, not another platform’s navigation.

Topic	Local documentation and boundary
Sampling and token probabilities	Generation parameters: model support, filtering, and forced-formatting limits
PDFs and files	File inputs: native inline input; no general file management or OCR fallback
Search and citations	Web search: upstream native tools; alternatively client functions or deployment Alpha Search
Caching, reasoning, and long context	Prompt caching, reasoning models, and context management
Routing, fallbacks, and rate limits	Model routing and rate limits; no promise of OpenRouter provider ordering, models fallback arrays, or router syntax
SDKs, streams, structured output, and tools	Example index: 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: 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 now explains input and the limits of audio output and assistant audio-ID replay.
• Video generation does not cover understanding: native Gemini video input explains Chat video_url parsing differences and Files/Interactions gaps.
• Text latency coverage adds predicted outputs, describing the existing Chat prediction field without conversion or performance guarantees.
• Troubleshooting adds media size/encoding, hidden SDK resource calls, ineffective parameters, and request-stop boundaries.

Tool and output-control audit

Tool controls covers tool_choice, explicit false, and conversion boundaries; 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 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.