OpenRouter model endpoints, providers, image and video models, rankings (BYOK)

OpenRouter model endpoints, providers, image and video models, rankings (BYOK) — connector documentation

• MCP endpoint: https://byok-openrouter-catalog.connectorbay.com/mcp
• REST API: POST https://byok-openrouter-catalog.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-openrouter-catalog.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own OpenRouter Catalog OpenRouter API key, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-openrouter-catalog.connectorbay.com/health · Tool schemas: https://byok-openrouter-catalog.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-openrouter-catalog · agent@connectorbay.com

What OpenRouter model endpoints, providers, image and video models, rankings (BYOK) is for

OpenRouter model endpoints, providers, image and video models, rankings (BYOK) lets an AI assistant read your own OpenRouter Catalog data through the OpenRouter Catalog API with a key you supply (OpenRouter API key). Read-only: 8 tools (get_model, list_model_endpoints, list_zdr_endpoints, list_models_for_account, list_image_models, list_video_models, get_daily_rankings, get_task_classifications). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to openrouter.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenRouter Catalog. OpenRouter Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "What is the context length and price of anthropic/claude-sonnet-4.5 on OpenRouter?"
• "Which providers serve anthropic/claude-sonnet-4.5 on OpenRouter and at what uptime?"
• "Which OpenRouter endpoints guarantee zero data retention?"
• "Which OpenRouter models can my account actually use with my provider preferences?"
• "Which image generation models does OpenRouter offer?"
• "Which video generation models are on OpenRouter and what durations do they support?"

What it does

• get_model: Get one OpenRouter model: context length, per-token prices (USD as text), modalities, supported parameters, knowledge cutoff and Hugging Face id.
• list_model_endpoints: List every provider endpoint that serves one model, with price, context length, quantization, status and recent uptime. The endpoints array is returned whole.
• list_zdr_endpoints: List provider endpoints that have a zero-data-retention policy, with model, provider, price, context length and uptime.
• list_models_for_account: List models available to the key's account after its provider preferences and guardrails are applied, with prices and context length.
• list_image_models: List OpenRouter image generation models with description, input and output modalities and streaming support.
• list_video_models: List OpenRouter video generation models with supported durations, resolutions, aspect ratios and whether audio can be generated.
• get_daily_rankings: Get public daily, weekly or monthly token usage per model across OpenRouter (the rankings dataset, from 2025-01-01).
• get_task_classifications: Get the share of OpenRouter usage by task category over the trailing 7 days, with the models used per category.

BYOK key

You bring your own OpenRouter Catalog OpenRouter API key (https://openrouter.ai/settings/keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to openrouter.ai over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://github.com/OpenRouterTeam/typescript-sdk (the API this connector calls, with a BYOK key)

Live from the OpenRouter Catalog API (openrouter.ai) with a BYOK key; documentation: https://github.com/OpenRouterTeam/typescript-sdk. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenRouter Catalog. OpenRouter Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your OpenRouter Catalog account.

Built for: Worldwide. Languages: English.

OpenRouter model endpoints, providers, image and video models, rankings (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What OpenRouter model endpoints, providers, image and video models, rankings (BYOK) is. OpenRouter model endpoints, providers, image and video models, rankings (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own OpenRouter Catalog data: Read OpenRouter provider endpoints per model, zero-retention endpoints, image and video models and usage rankings with your own API key. You bring your own OpenRouter Catalog OpenRouter API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one OpenRouter Catalog call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to openrouter.ai, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If OpenRouter Catalog rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What OpenRouter Catalog receives. The request we make on your behalf, including the key and the arguments, under OpenRouter Catalog's own terms and privacy policy. OpenRouter Catalog acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer OpenRouter Catalog gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your OpenRouter Catalog data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. OpenRouter Catalog (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at OpenRouter Catalog at any time to end all access.

Children. OpenRouter model endpoints, providers, image and video models, rankings (BYOK) is a general-audience service operated by the adult using the assistant, under OpenRouter Catalog's own age rules.

Changes. We will post changes here with a new effective date.

OpenRouter model endpoints, providers, image and video models, rankings (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the OpenRouter model endpoints, providers, image and video models, rankings (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. OpenRouter model endpoints, providers, image and video models, rankings (BYOK) provides: Read OpenRouter provider endpoints per model, zero-retention endpoints, image and video models and usage rankings with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own OpenRouter Catalog credentials and only access data you are allowed to access. OpenRouter Catalog's terms apply to your use of OpenRouter Catalog; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by OpenRouter Catalog. OpenRouter Catalog and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data OpenRouter Catalog returns, lightly trimmed; it may be incomplete, delayed or changed by OpenRouter Catalog. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your OpenRouter Catalog account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent OpenRouter Catalog's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; OpenRouter Catalog may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your OpenRouter Catalog key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action OpenRouter Catalog takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-openrouter-catalog

OpenRouter model endpoints, providers, image and video models, rankings (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-openrouter-catalog.connectorbay.com/mcp
• REST API: https://byok-openrouter-catalog.connectorbay.com/openapi.json
• Live status: https://byok-openrouter-catalog.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. OpenRouter model endpoints, providers, image and video models, rankings (BYOK) never asks for them.