Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
OpenRouter (BYOK) icon

OpenRouter (BYOK)

Read OpenRouter model catalog and prices, providers, key limits, credits, activity and generation records with BYOK

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderOpenRouterunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which OpenRouter models have the cheapest prompt price and a long context?
Tools called
list_models
How many models does OpenRouter offer?
Tools called
count_models
Which embedding models can I use on OpenRouter?
Tools called
list_embedding_models
Which providers does OpenRouter route to and where are they based?
Tools called
list_providers
How much have I spent with my OpenRouter key and what is the limit?
Tools called
get_current_key
How many OpenRouter credits do I have left?
Tools called
get_credits

About

OpenRouter (BYOK) lets an AI assistant read your own OpenRouter data through the OpenRouter API with a key you supply (API key (some tools need a management key)). Read-only: 8 tools (list_models, count_models, list_embedding_models, list_providers, get_current_key, get_credits, get_activity, get_generation). 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. OpenRouter and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the OpenRouter API (openrouter.ai) with a BYOK key; documentation: https://openrouter.ai/docs/api-reference/overview. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • List modelsList models on OpenRouter with context length, per-token prices and supported parameters.
  • Count modelsCount the models on OpenRouter, optionally for one output modality.
  • List embedding modelsList embedding models on OpenRouter with context length and prices.
  • List providersList the inference providers behind OpenRouter with headquarters, data centers and links to their policy and status pages.
  • Get current keyShow the API key used for this call: label, spend today, this week, this month and in total, limit and remaining limit, free-tier flag and rate limit.
  • Get creditsShow total credits purchased and total credits used on the account.
  • Get activityShow daily usage per model and provider for the last 30 completed UTC days: requests, tokens and spend.
  • Get generationLook up metadata of one past OpenRouter request by its generation id: model, provider, token counts, cost and latency.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-openrouter.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-openrouter.connectorbay.com/mcp
RESTPOST https://byok-openrouter.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-openrouter.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your API key (some tools need a management key) in the X-Upstream-Key header (get one at openrouter.ai).
  • Ask a question; the agent picks the right tool and answers from the live data.

OpenRouter connector: questions and answers

What is the OpenRouter connector?

OpenRouter (BYOK) lets an AI assistant read your own OpenRouter data through the OpenRouter API with a key you supply (API key (some tools need a… It is a hosted MCP server with 8 tools such as List models, Count models, List embedding models, List providers, Get current key, Get credits, published by Unify Dynamics LLC. It is independent and not affiliated with OpenRouter.

How do I connect OpenRouter to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-openrouter.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-openrouter.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-openrouter.json.

Do I need a OpenRouter account or API key?

Yes: this is a bring-your-own-key connector. Create a API key (some tools need a management key) at https://openrouter.ai/settings/keys and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is OpenRouter read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the OpenRouter connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Meraki Switches (BYOK)

Read the port configuration, port status, port usage, client counts, LLDP/CDP neighbors and PoE draw of your Cisco Meraki switches with your own Dashboard API key

Live · MCP + REST7 tools

Meraki Usage Summary (BYOK)

Read top-N usage summaries of your Cisco Meraki organization: busiest appliances, devices, device models, SSIDs, applications, switches by energy and networks by status

Live · MCP + REST8 tools

Meraki Wireless (BYOK)

Read access point channel utilization, packet loss, Ethernet status, client counts and BSSID status of your Cisco Meraki wireless network with your own Dashboard API key

Live · MCP + REST7 tools

Merge Agent Handler (BYOK)

Browse Merge Agent Handler connectors and their tools, your tool packs, connection health and tool-call credit usage, with your own Agent Handler access key

Live · MCP + REST8 tools

Mergify (BYOK)

Read your Mergify merge queue state, queue statistics, activity log and CI test health for GitHub repositories with your own application key

Live · MCP + REST12 tools

Meshy (BYOK)

Read your Meshy credit balance and the status of your text-to-3D, image-to-3D, text-to-image, remesh and retexture tasks with your own API key

Live · MCP + REST10 tools

Documentation

Back to top

OpenRouter (BYOK) — connector documentation

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

What OpenRouter (BYOK) is for

OpenRouter (BYOK) lets an AI assistant read your own OpenRouter data through the OpenRouter API with a key you supply (API key (some tools need a management key)). Read-only: 8 tools (list_models, count_models, list_embedding_models, list_providers, get_current_key, get_credits, get_activity, get_generation). 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. OpenRouter 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:

  • "Which OpenRouter models have the cheapest prompt price and a long context?"
  • "How many models does OpenRouter offer?"
  • "Which embedding models can I use on OpenRouter?"
  • "Which providers does OpenRouter route to and where are they based?"
  • "How much have I spent with my OpenRouter key and what is the limit?"
  • "How many OpenRouter credits do I have left?"

What it does

  • list_models: List models on OpenRouter with context length, per-token prices and supported parameters. Prices are USD per token as text. Filter by search text, author or modality.
  • count_models: Count the models on OpenRouter, optionally for one output modality.
  • list_embedding_models: List embedding models on OpenRouter with context length and prices.
  • list_providers: List the inference providers behind OpenRouter with headquarters, data centers and links to their policy and status pages.
  • get_current_key: Show the API key used for this call: label, spend today, this week, this month and in total, limit and remaining limit, free-tier flag and rate limit.
  • get_credits: Show total credits purchased and total credits used on the account. Needs a management key.
  • get_activity: Show daily usage per model and provider for the last 30 completed UTC days: requests, tokens and spend. Needs a management key.
  • get_generation: Look up metadata of one past OpenRouter request by its generation id: model, provider, token counts, cost and latency. Does not return prompt text.

BYOK key

You bring your own OpenRouter API key (some tools need a management 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

Live from the OpenRouter API (openrouter.ai) with a BYOK key; documentation: https://openrouter.ai/docs/api-reference/overview. 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. OpenRouter 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 account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

OpenRouter (BYOK) — Privacy Policy

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

What OpenRouter (BYOK) is. OpenRouter (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own OpenRouter data: Read OpenRouter model catalog and prices, providers, key limits, credits, activity and generation records with BYOK. You bring your own OpenRouter API key (some tools need a management key); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one OpenRouter 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 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 receives. The request we make on your behalf, including the key and the arguments, under OpenRouter's own terms and privacy policy. OpenRouter 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 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 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 (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 at any time to end all access.

Children. OpenRouter (BYOK) is a general-audience service operated by the adult using the assistant, under OpenRouter's own age rules.

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

Terms of service

Back to top

OpenRouter (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the OpenRouter (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. OpenRouter (BYOK) provides: Read OpenRouter model catalog and prices, providers, key limits, credits, activity and generation records with BYOK. 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 credentials and only access data you are allowed to access. OpenRouter's terms apply to your use of OpenRouter; 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. OpenRouter 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 returns, lightly trimmed; it may be incomplete, delayed or changed by OpenRouter. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your OpenRouter 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'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 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 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 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

OpenRouter (BYOK) support

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

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 (BYOK) never asks for them.

Get OpenRouter (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own OpenRouter API key (some tools need a management key). Create one at https://openrouter.ai/settings/keys, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to OpenRouter. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with OpenRouter.