docs(openrouter): document native openrouter provider - #366
Conversation
Rewrite the OpenRouter page for the first-class native integration (chat, image, video, speech/TTS, server tools, SDK usage) and update supported-providers references away from the OpenAI-compatible workaround.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6609320262
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
|
|
||
| ## Setting Up OpenRouter as a Custom Provider | ||
| <Note> | ||
| OpenRouter is now a native provider — you no longer need to set it up as an OpenAI-compatible custom provider. The legacy [custom provider](/features/custom-providers) approach still works, but the native integration is recommended because it uses the official OpenRouter SDK and unlocks image, video, and speech capabilities. |
There was a problem hiding this comment.
This page now tells users OpenRouter is a native provider and no longer needs custom-provider setup, but docs.json still lists features/openrouter-integration only under Providers > Custom Providers (docs.json:139-145). In the published sidebar, users will still find the native setup guide in the custom-provider bucket, which contradicts the new guidance and makes the provider setup harder to discover; move the page to the main Providers section while keeping the existing slug.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Moved features/openrouter-integration to the main Providers section in docs.json (kept the same slug). Also updated the Custom Providers page so it no longer lists OpenRouter as a custom-provider guide.
List the OpenRouter page in the main Providers section instead of Custom Providers, and update the custom-providers cross-link.
faizan-185
left a comment
faizan-185
left a comment
There was a problem hiding this comment.
Addressed the Codex/review feedback in 30b0e85: OpenRouter guide now lives under Providers, not Custom Providers.
2 participants
Summary
OpenRouter is now a first-class native provider in PromptLayer (official OpenRouter SDK, native API key, and chat/image/video/speech). The docs still described it as an OpenAI-compatible custom provider, so this updates them:
features/openrouter-integration.mdx— rewritten for the native integration:run()examples (one call works across all api types)features/supported-providers.mdx— added a native OpenRouter entry under Provider Details and repointed the OpenAI tip + OpenAI-compatible examples fromcustom-providers#openrouterto the native page.No dangling
custom-providers#openrouterlinks remain;<CodeGroup>is an already-used Mintlify component.Linear
Part of PRO-248 — Integrate OpenRouter as a first-class provider
Related: backend
promptlayer-app#1457, SDKsprompt-layer-library#336,prompt-layer-js#190,promptlayer-mcp#41Test plan
docs.jsonnav; no nav changes needed