# ScreenRig

> ScreenRig is an agent-operated digital-signage service: an agent uses the CLI and REST API to upload content, assemble a looping playlist, pair a browser screen, and observe the result.

Status: prerelease localhost v1. Last-reviewed: 2026-08-14. API contract: OpenAPI 0.2.0.

Start here: build the source-checkout CLI, start the local stack, create an account, open the browser Player, pair its six-character code, upload/publish an application, create and assign a playlist, then follow durable events. The complete CLI-to-API-to-Player lifecycle is verified on a three-replica localhost stack. The public ScreenRig marketing and documentation site is live and verified over HTTPS. The ScreenRig service API, Player, release hosts, protected content delivery, and full production application stack remain undeployed and unverified; npm packages remain unpublished. This is not an uptime, SLA, customer, or traffic claim.

This file follows the llms.txt convention/proposal. It is a curated orientation index, not a crawler-control file, access-control mechanism, ranking signal, or availability guarantee. Crawl policy is expressed by https://screenrig.ai/robots.txt.

Source priority: OpenAPI for HTTP schema; CLI `--help` for commands; capabilities/version/status for observed runtime availability; architecture for design intent; prose pages last.

Credential realms are not interchangeable: account bearer credentials belong only on the CLI/account API; pairing, paired-device, and runtime cookies stay on the trusted Player origin; placement capability is short-lived and scoped to one application placement; launch tickets and release-grant cookies authorize one exact release host. Never put an account bearer in a URL, browser storage, Player, uploaded application, log, or event.

## Start and operate

- [Homepage as Markdown](https://screenrig.ai/index.md): exact contract, prerequisites, verified quickstart, workflow, and trust boundary.
- [Product and operator docs](https://screenrig.ai/docs.md): when to use ScreenRig, local operation, recovery, and deferred boundaries.
- [Agent skill page](https://screenrig.ai/skill.md): how and when to load the skill.
- [Downloadable SKILL.md](https://screenrig.ai/skill/SKILL.md): operative agent instructions.
- [Implementation status](https://screenrig.ai/status.md): dated readiness evidence, not uptime.

## API and protocols

- [API reference as Markdown](https://screenrig.ai/docs/api.md): five-minute workflow, auth realms, semantics, problems, and complete endpoint inventory.
- [Raw OpenAPI 3.1 YAML](https://screenrig.ai/docs/api/openapi.yaml): authoritative HTTP paths and schemas, API version 0.2.0.
- [Raw OpenAPI 3.1 JSON](https://screenrig.ai/docs/api/openapi.json): deterministic JSON representation of the same contract.
- [RFC 9457 problem registry YAML](https://screenrig.ai/docs/api/problems.yaml): stable ScreenRig problem codes and statuses.
- [RFC 9457 problem registry JSON](https://screenrig.ai/docs/api/problems.json): deterministic JSON representation.
- [Readiness JSON](https://screenrig.ai/status/status.json): static implementation-readiness record.

## More context

- [Expanded ScreenRig context](https://screenrig.ai/llms-full.txt): CLI, architecture, security, runtime, limits, and deferred behavior.
- [Docs-specific agent index](https://screenrig.ai/docs/llms.txt): high-signal documentation entry points.
- [Expanded docs context](https://screenrig.ai/docs/llms-full.txt): consolidated operator and API semantics.
- [Markdown sitemap](https://screenrig.ai/sitemap.md): machine-readable public documentation map.

Boundaries: Android `standard`, `managed`, and `amazon` source, its exact-origin Player integration, and native manifest-authorized content cache are implemented and pass unit/lint/debug/R8 release/Player matrices. Instrumentation is blocked without KVM; no personal Pixel, managed physical device, or Amazon Signage Stick was validated; there is no app-store publication or general offline-playback guarantee. MCP, billing/payments, screenshot capture, email recovery, and a management dashboard are deferred. Protected release, media, and K/V delivery requires current screen-manifest authority. ScreenRig is not public file hosting.