OpenRelay
OpenRelay is a Y Combinator-backed distributed GPU cloud for production AI inference — "the CDN of inference." It runs a global mesh of GPUs (RTX 4090/5090, A100, H100) that teams reach through a single API: rent dedicated GPU VMs with SSH and persistent volumes, stand up autoscaling inference clusters behind an endpoint, or call hosted open models via an OpenAI-compatible (and Anthropic Messages-compatible) API. Anyone can also join as a provider and earn on idle compute. The control-plane REST API (api.openrelay.inc) manages orgs, VMs, clusters, snapshots, billing, usage, transfers, provider nodes, batches, files, and webhooks, and is fully driveable from the first-party `orl` CLI — which also ships an official MCP server for agents. Traffic reroutes across healthy nodes in milliseconds, with pricing OpenRelay claims is up to 90% cheaper than the hyperscalers.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles OpenRelay the way a machine reads it — 24 machine-readable artifacts across 19 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OpenRelay scores 57.8/100 (developing), with a separate agent-readiness read of 61/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OpenRelay
Each block below is one kind of artifact we hold for OpenRelay. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 19
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
OpenRelay Inference API
OpenAI-compatible chat completions API (POST /v1/chat/completions) and, for supporting models, an Anthropic-compatible Messages API (POST /v1/messages). Drop-in: point the offic...
OpenRelay Account API
The signed-in user: profile, memberships, and first-time onboarding.
OpenRelay API Keys API
Programmatic access keys (vl_…) used to authenticate with this API.
OpenRelay Batches API
Batch inference jobs: submit a JSONL file of requests, poll status, and download results at a discounted rate. Served by the inference endpoint (inference.openrelay.inc). Batch ...
OpenRelay Billing API
Prepaid balance, saved cards, deposits, and auto-recharge.
OpenRelay Catalog API
Public catalog: GPU models, availability, pricing, templates, and locations.
OpenRelay Clusters API
Autoscaling inference clusters that serve a container image behind an endpoint.
OpenRelay Files API
Input and result files for the Batch API (JSONL, up to 200 MB and 50,000 records). Served by the inference endpoint (inference.openrelay.inc).
OpenRelay Internal API
Machine-to-machine endpoints used by platform infrastructure. Not part of the public API.
OpenRelay Organizations API
Organizations and their members. Most resources are scoped to an org.
OpenRelay Provider API
For GPU providers: applications, nodes, provisioning tokens, and earnings.
OpenRelay Registry Credentials API
Private container-registry credentials for pulling images.
OpenRelay Runners API
Managed GitHub Actions runner pools.
OpenRelay Snapshots API
Point-in-time VM snapshots and forking new VMs from them.
OpenRelay SSH Keys API
Org-level SSH public keys that can be attached to VMs.
OpenRelay Transfers API
Move resources between organizations you belong to.
OpenRelay Usage API
Current-period usage and cost breakdowns.
OpenRelay VMs API
GPU virtual machines: lifecycle, disks, SSH access, and console links.
OpenRelay Webhooks API
Subscribe to platform events with signed HTTP callbacks.
Scroll within the panel for all 19 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
openrelay-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Openrelay Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for OpenRelay — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/openrelay · machine-readable index on apis.io