Anthropic spend limits, service accounts, roles, federation and plugins (BYOK)
Read your Anthropic organization's spend limits, service accounts, RBAC groups and roles, workload identity federation and plugins with your own Admin API key
Read your RunPod pods, serverless endpoints, templates, network volumes and billing history with BYOK
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_podsget_podlist_endpointslist_templateslist_network_volumesget_pod_billingRunPod (BYOK) lets an AI assistant read your own RunPod data through the RunPod API with a key you supply (API key). Read-only: 8 tools (list_pods, get_pod, list_endpoints, list_templates, list_network_volumes, get_pod_billing, get_serverless_billing, get_network_volume_billing). 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 rest.runpod.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by RunPod. RunPod and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the RunPod API (rest.runpod.io) with a BYOK key; documentation: https://docs.runpod.io/api-reference-v2/billing/get-pod-billing-history.md. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
8 tools, grouped by job. Every one is read-only or compute-only.
https://byok-runpod.connectorbay.com/mcpThree ways in, the same 8 tools.
https://byok-runpod.connectorbay.com/mcpPOST https://byok-runpod.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-runpod.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at console.runpod.io).RunPod (BYOK) lets an AI assistant read your own RunPod data through the RunPod API with a key you supply (API key). It is a hosted MCP server with 8 tools such as List pods, Get pod, List endpoints, List templates, List network volumes, Get pod billing, published by Unify Dynamics LLC. It is independent and not affiliated with RunPod.
Add the MCP endpoint https://byok-runpod.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-runpod.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-runpod.json.
Yes: this is a bring-your-own-key connector. Create a API key at https://console.runpod.io/user/settings and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Anthropic organization's spend limits, service accounts, RBAC groups and roles, workload identity federation and plugins with your own Admin API key
Read your Apify account and limits, Actors, runs, tasks, datasets and Store listings with BYOK; it never starts an Actor run
Read your Appetize cloud-streamed iOS and Android app builds, tags, sessions and usage with your own API token
Read your AppSignal error and performance samples, deploy and custom markers, metrics and deploy statistics with your own personal API token
Read your AppVeyor CI projects, builds, build history and deployment environments with BYOK
Read your Are.na profile, channels, blocks, followers, feed and notifications with your own personal access token
https://byok-runpod.connectorbay.com/mcpPOST https://byok-runpod.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-runpod.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-runpod.connectorbay.com/health · Tool schemas: https://byok-runpod.connectorbay.com/tools.jsonRunPod (BYOK) lets an AI assistant read your own RunPod data through the RunPod API with a key you supply (API key). Read-only: 8 tools (list_pods, get_pod, list_endpoints, list_templates, list_network_volumes, get_pod_billing, get_serverless_billing, get_network_volume_billing). 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 rest.runpod.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by RunPod. RunPod 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:
list_pods: List your RunPod pods with status, image, GPU type and count, vCPU and memory, hourly cost and last start time. Environment variables are not returned.get_pod: Get one RunPod pod by id: status, image, GPU, memory, disk sizes, hourly cost and start times.list_endpoints: List your RunPod serverless endpoints with GPU types, worker scaling settings, timeouts and template id.list_templates: List your RunPod templates (container image, disk sizes, serverless flag). Add include_public to see public ones.list_network_volumes: List your RunPod network volumes with name, size in GB and data center.get_pod_billing: Show RunPod pod billing history: amount billed, billed time and disk, grouped by GPU type or pod, in time buckets.get_serverless_billing: Show RunPod serverless billing history: amount billed and billed time, grouped by endpoint, pod or GPU type, in time buckets.get_network_volume_billing: Show RunPod network volume storage billing history in time buckets.You bring your own RunPod API key (https://console.runpod.io/user/settings). 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 rest.runpod.io 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.
Live from the RunPod API (rest.runpod.io) with a BYOK key; documentation: https://docs.runpod.io/api-reference-v2/billing/get-pod-billing-history.md. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by RunPod. RunPod 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 RunPod account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What RunPod (BYOK) is. RunPod (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own RunPod data: Read your RunPod pods, serverless endpoints, templates, network volumes and billing history with BYOK. You bring your own RunPod API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one RunPod 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 rest.runpod.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If RunPod 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 RunPod receives. The request we make on your behalf, including the key and the arguments, under RunPod's own terms and privacy policy. RunPod acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer RunPod 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 RunPod 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. RunPod (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 RunPod at any time to end all access.
Children. RunPod (BYOK) is a general-audience service operated by the adult using the assistant, under RunPod's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the RunPod (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-runpod.connectorbay.com/mcphttps://byok-runpod.connectorbay.com/openapi.jsonWhen 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. RunPod (BYOK) never asks for them.