Roku
Roku is the leading TV streaming platform in the U.S., Canada, and Mexico, offering a comprehensive operating system that powers smart TVs, streaming players, and audio devices. Roku provides a robust developer program for building channel apps, monetizing through Roku Pay, integrating analytics, and controlling devices via the External Control Protocol. The platform supports both BrightScript and SceneGraph frameworks for app development, and the Nabu Cloud developer cloud for managing remote test devices and channel builds.
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 Roku the way a machine reads it — 186 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 — Roku scores 59.5/100 (developing), with a separate agent-readiness read of 55/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 Roku
Each block below is one kind of artifact we hold for Roku. 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.
Roku BrightScript SDK
BrightScript is Roku's scripting language used to build apps for the Roku platform. The SDK provides a comprehensive component library with over 100 built-in objects covering UI...
Roku SceneGraph
SceneGraph is Roku's XML-based declarative UI framework for building rich, performant channel applications. It provides node components, animations, and a scene-based architectu...
Roku Search Feed
Roku Search Feed is a JSON feed format that publishers ingest to expose their catalog to Roku Search. The feed provides movies, series, episodes, short-form videos, TV specials,...
Roku Direct Publisher Feed
Roku Direct Publisher (RDP) feed is a JSON feed specification that allows non-technical publishers to populate channels by hosting a structured catalog of short-form videos, mov...
Roku Analytics
Roku Analytics provides performance reporting, audience metrics, and engagement data for Roku channel publishers. Reports are accessed through the Roku Developer Dashboard rathe...
Roku Authentication Framework
APIs and patterns for implementing user sign-in and authentication within Roku channels, including device-linking ("on-device authentication") and OAuth-style flows. The framewo...
Roku Apps API
Application listing, launching, and termination
Roku asyncapi API
The asyncapi API from Roku — 3 operation(s) for asyncapi.
Roku Billing API
Billing cycle and credit management
Roku builds API
The builds API from Roku — 2 operation(s) for builds.
Roku devices API
The devices API from Roku — 6 operation(s) for devices.
Roku Diagnostics API
Developer-mode diagnostics and performance counters
Roku Discovery API
Device discovery and metadata
Roku groups API
The groups API from Roku — 4 operation(s) for groups.
Roku healthz API
The healthz API from Roku — 2 operation(s) for healthz.
Roku Input API
Custom input event injection
Roku KeyPress API
Simulated remote-control key injection
Roku organisation-roles API
The organisation-roles API from Roku — 2 operation(s) for organisation-roles.
Roku organisations API
The organisations API from Roku — 10 operation(s) for organisations.
Roku personal-access-tokens API
The personal-access-tokens API from Roku — 4 operation(s) for personal-access-tokens.
Roku projects API
The projects API from Roku — 6 operation(s) for projects.
Roku Query API
Device, media, and TV state queries
Roku serviceaccounts API
The serviceaccounts API from Roku — 1 operation(s) for serviceaccounts.
Roku snapshots API
The snapshots API from Roku — 2 operation(s) for snapshots.
Roku Subscription API
Subscription lifecycle management
Roku users API
The users API from Roku — 4 operation(s) for users.
Roku Validation API
Transaction and refund validation
Scroll within the panel for all 27 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Roku GraphQL Schema
This document describes a conceptual GraphQL schema for the Roku streaming platform, covering the Roku Pay Web Services (billing, subscriptions, transaction validation), Externa...
GRAPHQLPricing 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.
Roku 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.
Roku 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.
Roku Finops
FINOPSFeatures 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.
Channel Development
BrightScript and SceneGraph frameworks for building Roku TV streaming channel applications.
Device Control
Local-network HTTP API (ECP) for discovery, key injection, app launching, and diagnostics.
Roku Pay
Server-to-server billing APIs for transaction validation, refunds, and subscription management.
Direct Publisher
JSON feed ingestion path for non-technical publishers to populate Roku channels.
Search Feed
Catalog feed ingestion that surfaces publisher content in Roku Search.
Nabu Cloud
Roku's developer cloud for managing remote test devices, snapshots, and builds.
Channel Store Monetization
Transactional and subscription monetization through ChannelStore and roChannelStore components.
Advertising Framework
Roku Advertising Framework (RAF) for monetizing video content with ads.
Scroll within the panel for all 8 ·
Semantic Vocabularies 4
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.
Roku Nabu Cloud Context
JSON-LDRoku Search Feed 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.
Roku API Rules
SPECTRALRoku API Rules
SPECTRALJSON Schema 58
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.
ActiveApp
JSON SCHEMAAppList
JSON SCHEMAApp
JSON SCHEMADeviceInfo
JSON SCHEMAMediaPlayer
JSON SCHEMAAgentStreamOption
JSON SCHEMAAWSRegion
JSON SCHEMABody_serviceaccounts-login_token
JSON SCHEMABuildOut
JSON SCHEMABuildSource
JSON SCHEMADeviceCreate
JSON SCHEMADeviceHistoryOut
JSON SCHEMADeviceInstanceInfo
JSON SCHEMADeviceOut
JSON SCHEMADeviceStart
JSON SCHEMADeviceStatus
JSON SCHEMADeviceType
JSON SCHEMADeviceUpdate
JSON SCHEMAGroupAddMember
JSON SCHEMAGroupCreate
JSON SCHEMAGroupMemberOut
JSON SCHEMAGroupOut
JSON SCHEMAGroupRoleOut
JSON SCHEMAGroupUpdate
JSON SCHEMAIceServer
JSON SCHEMAKubernetesStatus
JSON SCHEMAOIDCTokenResponseModel
JSON SCHEMAOrganisationMemberOut
JSON SCHEMAOrganisationOut
JSON SCHEMAOrganisationRegionOut
JSON SCHEMAOrganisationRoleOut
JSON SCHEMAPersonalAccessTokenCreate
JSON SCHEMAPersonalAccessTokenCreated
JSON SCHEMAPersonalAccessTokenOut
JSON SCHEMAPersonalAccessTokenRefresh
JSON SCHEMAPersonalAccessTokenStatus
JSON SCHEMAProjectCreate
JSON SCHEMAProjectGroupAdd
JSON SCHEMAProjectGroupOut
JSON SCHEMAProjectGroupUpdate
JSON SCHEMAProjectMemberAdd
JSON SCHEMAProjectMemberOut
JSON SCHEMAProjectOut
JSON SCHEMAProjectRoleOut
JSON SCHEMAProjectUpdate
JSON SCHEMAScopeOut
JSON SCHEMASnapshotCreate
JSON SCHEMASnapshotOut
JSON SCHEMASnapshotUpdate
JSON SCHEMAUserOut
JSON SCHEMACancelSubscriptionRequest
JSON SCHEMAIssueCreditRequest
JSON SCHEMARefundSubscriptionRequest
JSON SCHEMARefundValidation
JSON SCHEMASubscriptionResult
JSON SCHEMATransactionValidation
JSON SCHEMAUpdateBillCycleRequest
JSON SCHEMASearch Feed
JSON SCHEMAScroll within the panel for all 58 ·
JSON Structure 58
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.
External Control Protocol Active App Structure
JSON STRUCTUREExternal Control Protocol App List Structure
JSON STRUCTUREExternal Control Protocol App Structure
JSON STRUCTUREExternal Control Protocol Device Info Structure
JSON STRUCTUREExternal Control Protocol Media Player Structure
JSON STRUCTURENabu Cloud Agent Stream Option Structure
JSON STRUCTURENabu Cloud Awsregion Structure
JSON STRUCTURENabu Cloud Body Serviceaccounts Login Token Structure
JSON STRUCTURENabu Cloud Build Out Structure
JSON STRUCTURENabu Cloud Build Source Structure
JSON STRUCTURENabu Cloud Device Create Structure
JSON STRUCTURENabu Cloud Device History Out Structure
JSON STRUCTURENabu Cloud Device Instance Info Structure
JSON STRUCTURENabu Cloud Device Out Structure
JSON STRUCTURENabu Cloud Device Start Structure
JSON STRUCTURENabu Cloud Device Status Structure
JSON STRUCTURENabu Cloud Device Type Structure
JSON STRUCTURENabu Cloud Device Update Structure
JSON STRUCTURENabu Cloud Group Add Member Structure
JSON STRUCTURENabu Cloud Group Create Structure
JSON STRUCTURENabu Cloud Group Member Out Structure
JSON STRUCTURENabu Cloud Group Out Structure
JSON STRUCTURENabu Cloud Group Role Out Structure
JSON STRUCTURENabu Cloud Group Update Structure
JSON STRUCTURENabu Cloud Ice Server Structure
JSON STRUCTURENabu Cloud Kubernetes Status Structure
JSON STRUCTURENabu Cloud Oidctoken Response Model Structure
JSON STRUCTURENabu Cloud Organisation Member Out Structure
JSON STRUCTURENabu Cloud Organisation Out Structure
JSON STRUCTURENabu Cloud Organisation Region Out Structure
JSON STRUCTURENabu Cloud Organisation Role Out Structure
JSON STRUCTURENabu Cloud Personal Access Token Create Structure
JSON STRUCTURENabu Cloud Personal Access Token Created Structure
JSON STRUCTURENabu Cloud Personal Access Token Out Structure
JSON STRUCTURENabu Cloud Personal Access Token Refresh Structure
JSON STRUCTURENabu Cloud Personal Access Token Status Structure
JSON STRUCTURENabu Cloud Project Create Structure
JSON STRUCTURENabu Cloud Project Group Add Structure
JSON STRUCTURENabu Cloud Project Group Out Structure
JSON STRUCTURENabu Cloud Project Group Update Structure
JSON STRUCTURENabu Cloud Project Member Add Structure
JSON STRUCTURENabu Cloud Project Member Out Structure
JSON STRUCTURENabu Cloud Project Out Structure
JSON STRUCTURENabu Cloud Project Role Out Structure
JSON STRUCTURENabu Cloud Project Update Structure
JSON STRUCTURENabu Cloud Scope Out Structure
JSON STRUCTURENabu Cloud Snapshot Create Structure
JSON STRUCTURENabu Cloud Snapshot Out Structure
JSON STRUCTURENabu Cloud Snapshot Update Structure
JSON STRUCTURENabu Cloud User Out Structure
JSON STRUCTUREPay Web Services Cancel Subscription Request Structure
JSON STRUCTUREPay Web Services Issue Credit Request Structure
JSON STRUCTUREPay Web Services Refund Subscription Request Structure
JSON STRUCTUREPay Web Services Refund Validation Structure
JSON STRUCTUREPay Web Services Subscription Result Structure
JSON STRUCTUREPay Web Services Transaction Validation Structure
JSON STRUCTUREPay Web Services Update Bill Cycle Request Structure
JSON STRUCTURERoku Search Feed Structure
JSON STRUCTUREScroll within the panel for all 58 ·
Examples 10
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.
Scroll within the panel for all 10 ·
Security 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.
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.
Streaming Channel Development
Build full-screen TV streaming channels with BrightScript/SceneGraph and ship to the Roku Channel Store.
Subscription Video On Demand
Monetize video content with recurring subscriptions managed by Roku Pay.
Transactional Video On Demand
Monetize individual movie/episode purchases via the Channel Store and Roku Pay.
Free Ad-Supported Streaming TV
Free streaming with the Roku Advertising Framework.
TV Remote and Home Automation
Build mobile or hub-based remote-control apps that drive Roku devices via ECP.
Automated Channel Testing
Run channel certification tests on remote Roku test devices in Nabu Cloud.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Visual Studio Code
BrightScript language extension for VSCode with debugging and side-loading.
Selenium WebDriver
WebDriver-based automated channel testing.
npm
roku-deploy and roku-debug published as npm packages.
Sublime Text
BrightScript syntax-highlighting package.
GitHub
Source-of-truth for Roku-published samples, tooling, and the dev-doc OpenAPI spec.
Resources
Every other property we hold for Roku — 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
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 17
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 17 ·
Access & Security 3
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/roku · machine-readable index on apis.io