ScreenCloud
ScreenCloud is a cloud digital signage platform that turns any screen into a managed display for content, dashboards, and apps. Its developer surface is the ScreenCloud Studio API - a single public GraphQL endpoint (bearer-token authenticated, region-specific, copied from the DEVELOPER tab in Studio) that lets you automate anything you can do in Studio by hand - pairing and managing screens, building playlists and channels, uploading media and files, casting content, installing and configuring signage apps, and exporting playback logs and QR metrics. ScreenCloud also runs a Developer Platform / App framework for building custom HTML/JavaScript signage apps that can be published (with approval) to the App Store. There is no documented public WebSocket API - the Studio API is request/response GraphQL over HTTPS.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles ScreenCloud the way a machine reads it — 13 machine-readable artifacts across 6 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 — ScreenCloud scores 29.1/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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 ScreenCloud
Each block below is one kind of artifact we hold for ScreenCloud. 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 6
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.
ScreenCloud Studio Screens API
GraphQL operations for managing screens - pair and depair devices (pairScreen, depairScreen), list and search screens (allScreens, screen, screenByDeviceId, searchScreen), organ...
ScreenCloud Studio Playlists API
GraphQL operations for building and maintaining playlists - the ordered sequences of content shown on screens. Create, update, and delete playlists (createPlaylist, updatePlayli...
ScreenCloud Studio Media and Files API
GraphQL operations for uploading and organizing the media library - images, videos, and documents. Create and manage files (createFile, updateFileById, deleteFileById) and folde...
ScreenCloud Studio Channels and Casts API
GraphQL operations for channels - the multi-zone layouts that compose playlists, apps, and media into a single screen experience - and for casting. Create, update, publish, and ...
ScreenCloud Studio Apps API
GraphQL operations for signage apps and their instances - list the app catalog and categories (allApps, allAppCategories, appBySlug), create and configure app instances (createA...
ScreenCloud Studio Playback Logs API
GraphQL operations for proof-of-play and engagement reporting - fetch and export what played on which screen and when (getPlaybackLogs, exportPlaybackLogs), query logs and scree...
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).
ScreenCloud Studio API (GraphQL)
OPEN COLLECTIONGraphQL 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.
ScreenCloud Studio API (GraphQL)
ScreenCloud is a cloud digital signage platform. Its documented public developer
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.
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.
Screencloud 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.
Screencloud 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.
Resources
Every other property we hold for ScreenCloud — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/screencloud · machine-readable index on apis.io