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 — 43 machine-readable artifacts across 1 API, 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 47.9/100 (developing), with a separate agent-readiness read of 41/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from OpenRelay's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/openrelay/"
title="OpenRelay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/openrelay.svg"
alt="OpenRelay Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/openrelay/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/openrelay/"
title="OpenRelay on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/openrelay/card.svg"
alt="OpenRelay Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
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 ·
Open Collections 19
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONOpenRelay Account API
OPEN COLLECTIONOpenRelay Account API Keys API
OPEN COLLECTIONOpenRelay Account Batches API
OPEN COLLECTIONOpenRelay Account Billing API
OPEN COLLECTIONOpenRelay Account Catalog API
OPEN COLLECTIONOpenRelay Account Clusters API
OPEN COLLECTIONOpenRelay Account Files API
OPEN COLLECTIONOpenRelay Account Internal API
OPEN COLLECTIONOpenRelay Account Organizations API
OPEN COLLECTIONOpenRelay Account Provider API
OPEN COLLECTIONOpenRelay Account Registry Credentials API
OPEN COLLECTIONOpenRelay Account Runners API
OPEN COLLECTIONOpenRelay Account Snapshots API
OPEN COLLECTIONOpenRelay Account SSH Keys API
OPEN COLLECTIONOpenRelay Account Transfers API
OPEN COLLECTIONOpenRelay Account Usage API
OPEN COLLECTIONOpenRelay Account VMs API
OPEN COLLECTIONOpenRelay Account Webhooks API
OPEN COLLECTIONScroll 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 Server
Official Model Context Protocol server shipped inside the OpenRelay CLI (orl). It exposes the entire OpenRelay control-plane REST API to Claude and other MCP clients as tools, e...
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 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/openrelay · machine-readable index on apis.io
This is an independent, third-party profile of OpenRelay, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.