Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Render Metrics (BYOK) — connector documentation

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

What Render Metrics (BYOK) is for

Render Metrics (BYOK) lets an AI assistant read your own Render Metrics data through the Render Metrics API with a key you supply (API key). Read-only: 8 tools (get_cpu, get_memory, get_http_requests, get_http_latency, get_bandwidth, get_instance_count, get_disk_usage, get_active_connections). 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.render.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Render Metrics. Render Metrics 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:

  • "How much CPU did my Render service use in the last hour?"
  • "How much memory does my Render service use?"
  • "How many requests did my Render web service get, by status code?"
  • "What is the p99 latency of my Render service?"
  • "How much bandwidth did my Render service use this hour?"
  • "How many instances did my Render service run (autoscaling)?"

What it does

  • get_cpu: Get CPU usage time series (cores) for services, Postgres or Key Value resources, optionally per instance and aggregated by AVG, MAX or MIN.
  • get_memory: Get memory usage time series (bytes) for services, Postgres or Key Value resources.
  • get_http_requests: Get HTTP request counts over time for a service, aggregated by status code or host and optionally filtered by host.
  • get_http_latency: Get HTTP request latency over time for a service at a quantile (for example 0.99), optionally filtered by host and path.
  • get_bandwidth: Get outbound bandwidth use over time for a service.
  • get_instance_count: Get the number of running instances of a service over time.
  • get_disk_usage: Get disk usage over time (bytes) of a service's persistent disk or a Postgres database.
  • get_active_connections: Get the number of active database connections over time for Postgres or Key Value resources.

BYOK key

You bring your own Render Metrics API key (https://dashboard.render.com/settings#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.render.com 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 Render Metrics API (api.render.com) with a BYOK key; documentation: https://api-docs.render.com/reference/get-cpu. 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 Render Metrics. Render Metrics 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 Render Metrics account.

Built for: Worldwide. Languages: English.