Radius
Application platform for cloud-native applications that enables developers to define, deploy, and manage applications across multiple clouds and on-premises environments using a unified model.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Radius the way a machine reads it — 39 machine-readable artifacts across 27 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 — Radius scores 35.0/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). 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 Radius
Each block below is one kind of artifact we hold for Radius. 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 27
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.
Radius ApiVersions API
The ApiVersions API from Radius — 2 operation(s) for apiversions.
Radius Applications API
The Applications API from Radius — 3 operation(s) for applications.
Radius AwsCredentials API
The AwsCredentials API from Radius — 2 operation(s) for awscredentials.
Radius AwsPlanes API
The AwsPlanes API from Radius — 2 operation(s) for awsplanes.
Radius AzureCredentials API
The AzureCredentials API from Radius — 2 operation(s) for azurecredentials.
Radius AzurePlanes API
The AzurePlanes API from Radius — 2 operation(s) for azureplanes.
Radius ConfigurationStores API
The ConfigurationStores API from Radius — 2 operation(s) for configurationstores.
Radius Containers API
The Containers API from Radius — 2 operation(s) for containers.
Radius Environments API
The Environments API from Radius — 3 operation(s) for environments.
Radius Extenders API
The Extenders API from Radius — 3 operation(s) for extenders.
Radius Gateways API
The Gateways API from Radius — 2 operation(s) for gateways.
Radius Locations API
The Locations API from Radius — 2 operation(s) for locations.
Radius MongoDatabases API
The MongoDatabases API from Radius — 3 operation(s) for mongodatabases.
Radius Operations API
The Operations API from Radius — 4 operation(s) for operations.
Radius Planes API
The Planes API from Radius — 1 operation(s) for planes.
Radius PubSubBrokers API
The PubSubBrokers API from Radius — 2 operation(s) for pubsubbrokers.
Radius RabbitMQQueues API
The RabbitMQQueues API from Radius — 3 operation(s) for rabbitmqqueues.
Radius RadiusPlanes API
The RadiusPlanes API from Radius — 2 operation(s) for radiusplanes.
Radius RedisCaches API
The RedisCaches API from Radius — 3 operation(s) for rediscaches.
Radius ResourceGroups API
The ResourceGroups API from Radius — 2 operation(s) for resourcegroups.
Radius ResourceProviders API
The ResourceProviders API from Radius — 4 operation(s) for resourceproviders.
Radius Resources API
The Resources API from Radius — 1 operation(s) for resources.
Radius ResourceTypes API
The ResourceTypes API from Radius — 2 operation(s) for resourcetypes.
Radius SecretStores API
The SecretStores API from Radius — 5 operation(s) for secretstores.
Radius SqlDatabases API
The SqlDatabases API from Radius — 3 operation(s) for sqldatabases.
Radius StateStores API
The StateStores API from Radius — 2 operation(s) for statestores.
Radius Volumes API
The Volumes API from Radius — 2 operation(s) for volumes.
Scroll within the panel for all 27 ·
Open Collections 5
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).
Applications.Core Management APIs
OPEN COLLECTIONApplications.Dapr Resource Management APIs
OPEN COLLECTIONApplications.Datastores Resource Management APIs
OPEN COLLECTIONApplications.Messaging Resource Management APIs
OPEN COLLECTIONUniversal Control Plane Resource Management APIs
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Radius Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Radius Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Radius Finops
FINOPSSecurity Posture 2
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Radius — 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 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
← All providers · Data indexed from github.com/api-evangelist/radius · machine-readable index on apis.io