OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK)

OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) — connector documentation

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

What OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) is for

OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) lets an AI assistant read your own OpenRouter Admin data through the OpenRouter Admin API with a key you supply (OpenRouter management key (batch tools also accept a normal API key)). Read-only: 11 tools (list_api_keys, get_api_key, list_guardrails, get_guardrail, list_workspaces, get_workspace, list_workspace_budgets, list_presets, list_provider_keys, list_batches, get_batch). 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 Admin. OpenRouter Admin 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 of my OpenRouter API keys spent the most this month?"
• "How much of its limit has the OpenRouter key with a given hash used?"
• "Which OpenRouter guardrails limit my spending or restrict providers?"
• "What rules does a given OpenRouter guardrail enforce?"
• "What OpenRouter workspaces do I have and what are their default models?"
• "What are the default settings of my main OpenRouter workspace?"

What it does

• list_api_keys: List the API keys of the account (hash, label, disabled flag, spending limit, remaining limit and usage in USD per day, week and month). Secret key values are never returned. Needs a management key.
• get_api_key: Get one OpenRouter API key's metadata by its hash: limit, remaining limit and usage in USD, creation and last use time. Needs a management key.
• list_guardrails: List guardrails (spending limits and allowed or ignored models and providers, zero-data-retention enforcement) of a workspace. Needs a management key.
• get_guardrail: Get one guardrail's limits and model and provider rules by id. Needs a management key.
• list_workspaces: List workspaces with their default models, provider sort order and observability settings. Needs a management key.
• get_workspace: Get one workspace by id or slug: defaults, default guardrail and observability flags. Needs a management key.
• list_workspace_budgets: List the spending budgets of a workspace (limit in USD per reset interval). Needs a management key.
• list_presets: List saved presets (named model and routing configurations) with slug, status and designated version id. Needs a management key.
• list_provider_keys: List the provider keys you attached to OpenRouter (bring your own key): provider, label, fallback and required flags. Key secrets are never returned. Needs a management key.
• list_batches: List OpenRouter batch jobs with status, model, request counts and timestamps (no request or result content).
• get_batch: Get the status of one OpenRouter batch job: state, model, request counts and finish time (no results content).

BYOK key

You bring your own OpenRouter Admin OpenRouter management key (batch tools also accept a normal API key) (https://openrouter.ai/settings/management-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 Admin 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 Admin. OpenRouter Admin 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 Admin account.

Built for: Worldwide. Languages: English.

OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) — Privacy Policy

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

What OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) is. OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own OpenRouter Admin data: Read OpenRouter API key metadata and usage, guardrails, workspaces, budgets, presets, provider key settings and batch status with your own management key. You bring your own OpenRouter Admin OpenRouter management key (batch tools also accept a normal API key); the assistant sends it to us with each request.

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

Children. OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) is a general-audience service operated by the adult using the assistant, under OpenRouter Admin's own age rules.

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

OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) provides: Read OpenRouter API key metadata and usage, guardrails, workspaces, budgets, presets, provider key settings and batch status with your own management 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 Admin credentials and only access data you are allowed to access. OpenRouter Admin's terms apply to your use of OpenRouter Admin; 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 Admin. OpenRouter Admin 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 Admin returns, lightly trimmed; it may be incomplete, delayed or changed by OpenRouter Admin. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your OpenRouter Admin 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 Admin'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 Admin 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 Admin 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 Admin 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-admin

OpenRouter API keys, guardrails, workspaces, budgets and batches (BYOK) support

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

• MCP endpoint: https://byok-openrouter-admin.connectorbay.com/mcp
• REST API: https://byok-openrouter-admin.connectorbay.com/openapi.json
• Live status: https://byok-openrouter-admin.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 API keys, guardrails, workspaces, budgets and batches (BYOK) never asks for them.