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

RunPod (BYOK)

Read your RunPod pods, serverless endpoints, templates, network volumes and billing history with BYOK

Unify Dynamics LLC

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

Try asking

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

Which of my RunPod pods are running and what do they cost per hour?
Tools called
list_pods
What is the status of my RunPod pod xedezhzb9la3ye?
Tools called
get_pod
Which serverless endpoints do I have on RunPod and how are they scaled?
Tools called
list_endpoints
Which RunPod templates have I saved?
Tools called
list_templates
How big are my RunPod network volumes and where are they?
Tools called
list_network_volumes
How much did I spend on RunPod pods this month by day?
Tools called
get_pod_billing

About

RunPod (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.

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 podsList your RunPod pods with status, image, GPU type and count, vCPU and memory, hourly cost and last start time.
  • Get podGet one RunPod pod by id: status, image, GPU, memory, disk sizes, hourly cost and start times.
  • List endpointsList your RunPod serverless endpoints with GPU types, worker scaling settings, timeouts and template id.
  • List templatesList your RunPod templates (container image, disk sizes, serverless flag).
  • List network volumesList your RunPod network volumes with name, size in GB and data center.
  • Get pod billingShow RunPod pod billing history: amount billed, billed time and disk, grouped by GPU type or pod, in time buckets.
  • Get serverless billingShow RunPod serverless billing history: amount billed and billed time, grouped by endpoint, pod or GPU type, in time buckets.
  • Get network volume billingShow RunPod network volume storage billing history in time buckets.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-runpod.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-runpod.connectorbay.com/mcp
RESTPOST https://byok-runpod.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-runpod.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 in the X-Upstream-Key header (get one at console.runpod.io).
  • Ask a question; the agent picks the right tool and answers from the live data.

RunPod connector: questions and answers

What is the RunPod connector?

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.

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

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.

Do I need a RunPod account or API key?

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.

Is RunPod read-only?

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

Is the RunPod 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

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

Live · MCP + REST8 tools

Apify (BYOK)

Read your Apify account and limits, Actors, runs, tasks, datasets and Store listings with BYOK; it never starts an Actor run

Live · MCP + REST11 tools

Appetize (BYOK)

Read your Appetize cloud-streamed iOS and Android app builds, tags, sessions and usage with your own API token

Live · MCP + REST10 tools

AppSignal (BYOK)

Read your AppSignal error and performance samples, deploy and custom markers, metrics and deploy statistics with your own personal API token

Live · MCP + REST10 tools

AppVeyor (BYOK)

Read your AppVeyor CI projects, builds, build history and deployment environments with BYOK

Live · MCP + REST7 tools

Are.na (BYOK)

Read your Are.na profile, channels, blocks, followers, feed and notifications with your own personal access token

Live · MCP + REST12 tools

Documentation

Back to top

RunPod (BYOK) — connector documentation

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

What RunPod (BYOK) is for

RunPod (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:

  • "Which of my RunPod pods are running and what do they cost per hour?"
  • "What is the status of my RunPod pod xedezhzb9la3ye?"
  • "Which serverless endpoints do I have on RunPod and how are they scaled?"
  • "Which RunPod templates have I saved?"
  • "How big are my RunPod network volumes and where are they?"
  • "How much did I spend on RunPod pods this month by day?"

What it does

  • 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.

BYOK key

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.

Data 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.

What it is not

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.

Privacy policy

Back to top

RunPod (BYOK) — Privacy Policy

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.

Terms of service

Back to top

RunPod (BYOK) — Terms of Service

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

  1. The Service. RunPod (BYOK) provides: Read your RunPod pods, serverless endpoints, templates, network volumes and billing history 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 RunPod credentials and only access data you are allowed to access. RunPod's terms apply to your use of RunPod; 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 RunPod. RunPod 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 RunPod returns, lightly trimmed; it may be incomplete, delayed or changed by RunPod. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your RunPod 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 RunPod'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; RunPod 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 RunPod 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 RunPod 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-runpod

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

Get RunPod (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own RunPod API key. Create one at https://console.runpod.io/user/settings, 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 RunPod. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with RunPod.