Radio Browser
Radio Browser is a free, community-driven directory of internet radio stations. The project publishes a public REST API exposing the full catalog of stations along with category aggregates (countries, states, languages, tags, codecs), click counting, voting, and station submission. Mirrors are discovered through a round-robin DNS pool (all.api.radio-browser.info) and the canonical server software (radiobrowser-api-rust) is released under AGPL-3.0, so anyone can self-host an additional mirror.
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 Radio Browser the way a machine reads it — 40 machine-readable artifacts across 4 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 — Radio Browser scores 46.6/100 (developing), with a separate agent-readiness read of 39/100 (agent aware). 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 Radio Browser
Each block below is one kind of artifact we hold for Radio Browser. 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 4
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.
Radio Browser Categories API
Aggregated counts of countries, languages, tags, codecs, and states.
Radio Browser Interactions API
Click counting, voting, and station submission.
Radio Browser Service API
Server stats, mirror discovery, and configuration.
Radio Browser Stations API
Browse, search, and list radio stations.
Open Collections 1
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).
Radio Browser API
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.
Rate 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.
Radio Browser Rate Limits
RATE LIMITSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Round-Robin Mirror Pool
Servers discovered via DNS resolution of all.api.radio-browser.info; clients pick a healthy mirror and fall back as needed.
Multiple Response Formats
JSON, XML, CSV, M3U, PLS, XSPF, and TTL output for nearly every read endpoint.
Faceted Browse
List stations by country, country code, state, language, tag, or codec with station counts per facet.
Continuous Stream Health Checks
Stations are automatically pinged to verify their stream is reachable; results power lastcheckok and broken-station endpoints.
Community Curation
Anyone can submit a station via POST /json/add; clicks and votes feed station popularity rankings.
Open Source Server (AGPL-3.0)
The radiobrowser-api-rust server is open source; operators can self-host an additional mirror.
Geo Coordinates
Stations carry optional geo_lat/geo_long for map-based discovery.
Prometheus Metrics
Each mirror exposes /metrics in Prometheus exposition format for operational observability.
Scroll within the panel for all 8 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Radio Browser Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Radio Browser API Rules
SPECTRALRadio Browser API Rules
SPECTRALJSON Schema 3
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
JSON Structure 2
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Radio Browser Category Structure
JSON STRUCTURERadio Browser Station Structure
JSON STRUCTUREExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
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.
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.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Internet Radio Player Apps
Power desktop, mobile, and web players that let users browse the directory and play streams.
Voice Assistant Skills
Back Alexa/Google/Home Assistant skills that play "play jazz radio from France" requests by searching the directory.
Smart Speaker Integrations
Embedded firmware (e.g. AirMusic, Hama, internet radio hardware) ships Radio Browser as a station source.
Music Discovery Research
Researchers analyze the catalog to study global radio programming, language distribution, and genre tagging.
Streaming Health Dashboards
Use the /json/checks data to build dashboards showing global radio stream uptime.
Editorial Curation
Editors use vote/click data to surface trending stations by country, language, or genre.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Home Assistant
Multiple custom components and the built-in Radio Browser integration use the API for station selection.
VLC / Media Players
Media player extensions consume the API to populate radio station catalogs.
Self-Hosted Mirrors
Operators run radiobrowser-api-rust to add to the all.api.radio-browser.info pool.
Public APIs Directory
Listed in public-apis/public-apis under the Music category.
Solutions 2
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Hosted Community API
The free, hosted, AGPL-licensed Radio Browser mirror network — the default for most apps.
Self-Hosted Mirror
Run radiobrowser-api-rust on your own infrastructure for guaranteed throughput, isolated data, or private catalogs.
Resources
Every other property we hold for Radio Browser — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 10
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 10 ·
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
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/radio-browser · machine-readable index on apis.io