Portkey (BYOK)

Portkey (BYOK) — connector documentation

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

What Portkey (BYOK) is for

Portkey (BYOK) lets an AI assistant read your own Portkey data through the Portkey API with a key you supply (Portkey API key). Read-only: 10 tools (list_prompts, list_configs, list_virtual_keys, list_guardrails, list_integrations, list_workspaces, get_requests_graph, get_cost_graph, get_tokens_graph, get_latency_graph). 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 api.portkey.ai. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Portkey. Portkey 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 prompt templates are saved in my Portkey workspace?"
• "What Portkey gateway configs exist?"
• "Which Portkey virtual keys are active and what are their limits?"
• "Which Portkey guardrails are active?"
• "Which LLM provider integrations are set up in Portkey?"
• "What workspaces does my Portkey organization have?"

What it does

• list_prompts: List saved prompt templates with slug, model, status and update time, optionally by collection, workspace or search text.
• list_configs: List gateway configs (routing, fallback and cache setups) with slug, status and update time.
• list_virtual_keys: List virtual keys with status, usage limit, rate limits and expiry (the provider secrets are never returned).
• list_guardrails: List guardrails with target, status, owner and update time, for a workspace or the organization.
• list_integrations: List provider integrations (connections to LLM providers) with slug, status and creation time.
• list_workspaces: List workspaces with slug, description, usage limits and rate limits. Needs an organization-level admin key.
• get_requests_graph: Get the number of gateway requests over time for a period as time buckets with a summary total, from the Portkey analytics API. Admin-level key needed.
• get_cost_graph: Get the cost of gateway requests (total and average per request) over time for a period as time buckets with a summary total, from the Portkey analytics API. Admin-level key needed.
• get_tokens_graph: Get the token usage (total and average per request) over time for a period as time buckets with a summary total, from the Portkey analytics API. Admin-level key needed.
• get_latency_graph: Get request latency in milliseconds (average, p50, p90, p99) over time for a period as time buckets with a summary total, from the Portkey analytics API. Admin-level key needed.

BYOK key

You bring your own Portkey Portkey API key (https://app.portkey.ai/api-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 api.portkey.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.

Notices

This connector reads only management and analytics data. It never sends LLM requests through Portkey.

Data sources

• https://portkey.ai/docs/api-reference/admin-api/introduction (the API this connector calls, with a BYOK key)

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

Built for: Worldwide. Languages: English.

Portkey (BYOK) — Privacy Policy

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

What Portkey (BYOK) is. Portkey (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Portkey data: Read your Portkey prompts, configs, virtual keys, guardrails, integrations, workspaces and usage analytics with your own API key. You bring your own Portkey Portkey API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Portkey 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 api.portkey.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 Portkey 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 Portkey receives. The request we make on your behalf, including the key and the arguments, under Portkey's own terms and privacy policy. Portkey acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Portkey 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 Portkey 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. Portkey (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 Portkey at any time to end all access.

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

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

Portkey (BYOK) — Terms of Service

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

1. The Service. Portkey (BYOK) provides: Read your Portkey prompts, configs, virtual keys, guardrails, integrations, workspaces and usage analytics 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 Portkey credentials and only access data you are allowed to access. Portkey's terms apply to your use of Portkey; 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 Portkey. Portkey 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 Portkey returns, lightly trimmed; it may be incomplete, delayed or changed by Portkey. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Portkey 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 Portkey'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; Portkey 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 Portkey 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 Portkey 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-portkey

Portkey (BYOK) support

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

• MCP endpoint: https://byok-portkey.connectorbay.com/mcp
• REST API: https://byok-portkey.connectorbay.com/openapi.json
• Live status: https://byok-portkey.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. Portkey (BYOK) never asks for them.