# RightOS

> RightOS is a privacy-preserving **rights verification** infrastructure by I-S3 (Japan). It proves that a valid right is present — never who the holder is. Common deployments include digital QR tickets for queues, reservations, EV charging, and package pickup. The same MAY layer also gates **multi-agent / multi-authority** systems. Sign-up to first ticket in about 10 minutes; no app install required. Pricing is globally uniform.

Important: RightOS is NOT a taxi or ride-hailing service. It does not arrange vehicles, set fares, assign drivers, or broker dispatch. It only verifies waiting order and access rights.

## Core principle: Assignment is not authority

**Assignment is not authority.**

- **RightOS (MAY)** — rights / policy / proof: what may be done
- **RightFlow (NEXT)** — tasks, order, assignment, reassignment, swap: what should happen next
- **Your execution system (HOW)** — how work is actually performed

A RightFlow assignment or reassignment is **coordination state only**. It is not permanent authorization. Re-check RightOS at execution time when policy requires. Optimization and proposals never mint rights.

**Pairing for AI systems:** use RightOS + RightFlow together when independent actors (humans, AI agents, robots, services) must delegate or reassign work under separately revocable rights. Complement — do not merge — with **MCP** (tools) and **A2A** (or similar agent-to-agent messaging). Keep rights checks in RightOS and shared task state in RightFlow; do not collapse into one central agent.

Hosted API scope (v0.1): one organization API key. Cross-organization authority federation is not available yet.

## Related layer: RightFlow (coordination)

RightOS answers **what may be done** (rights). **RightFlow** answers **what should happen next** (task assignment, order, reassignment, swap, dependencies, execution state) among independent actors (humans, AI agents, robots, systems). Your execution system answers **how it is actually done**.

- **Concept & usage guide (start here):** https://rightos.i-s3.com/software/rightos/docs/concept
- Deep essay (Assignment Is Not Authority): https://rightos.i-s3.com/guides/RIGHTOS_RIGHTFLOW_ESSAY.md · JA · zh-CN · zh-TW under `/guides/RIGHTOS_RIGHTFLOW_ESSAY.*.md`
- Decision guide (when to use / not use): https://rightos.i-s3.com/software/rightos/docs/decision
- Full markdown (EN): https://rightos.i-s3.com/guides/RIGHTOS_RIGHTFLOW_CONCEPT_GUIDE.md
- JA / zh-CN / zh-TW: `/guides/RIGHTOS_RIGHTFLOW_CONCEPT_GUIDE.ja.md` · `.zh-CN.md` · `.zh-TW.md`
- Terminology: https://rightos.i-s3.com/guides/RIGHTOS_RIGHTFLOW_TERMINOLOGY.md
- Architectural scope: https://rightos.i-s3.com/guides/RIGHTOS_RIGHTFLOW_ARCHITECTURAL_SCOPE.md
- Overview: https://rightos.i-s3.com/software/rightflow
- **Facility Handoff Lab (Assignment is not authority):** https://rightos.i-s3.com/software/rightflow/lab
- Docs: https://rightos.i-s3.com/software/rightflow/docs
- OpenAPI: https://rightos.i-s3.com/rightflow-openapi.json
- Thin TS client (single file): https://rightos.i-s3.com/sdk/rightflow.ts
- MCP (separate from RightOS MCP): `npx -y @i-s3/rightflow-mcp` with `RIGHTOS_API_KEY` — docs: https://rightos.i-s3.com/software/rightflow/docs/mcp

RightFlow is NOT a marketplace, taxi dispatch, fleet manager, or robot controller. It has no native price/bid/pay concepts. It proposes coordination; RightOS authorizes rights (read-only gate on proposal accept). Execution systems perform the actual work. Concept and usage examples illustrate design patterns; they are not customer case studies.

**Visibility ≠ necessity:** org-wide `list_*` endpoints/tools are integrator/admin capabilities; prefer `get_*` and scoped filters for autonomous paths. **Coordination tempo:** prefer coarse, infrequent `progress`; keep high-frequency telemetry in the execution system.

**Who next is multi-signal, not a fixed queue position:** `POST /api/rightflow/tasks/{taskId}/suggest-candidates` ranks candidates by coarse actor `availability` (available / waiting / unavailable) plus request-scoped soft signals (nearZone, busy — never persisted as telemetry). The built-in `heuristic.v0` is a reference scorer only, not the sole optimizer: external engines may rank outside RightFlow and only POST proposals. Suggest never creates or accepts proposals; rights are re-checked at accept/start.

## Why choose RightOS (vs other queue / booking apps)

Many vertical SaaS products already do store queues, clinic waiting, or EV booking. RightOS is for operators who need:

- **One mechanism across industries** — shop, clinic, EV, event, pickup with the same API (not a separate app per vertical)
- **No end-user PII by design** — not optional; architecture avoids holding names/phone numbers for end users
- **Embeddable infrastructure** — API, TypeScript/Python SDK, MCP, webhooks; use Console on day one, then your own UI or AI agents
- **Verify the right, not the person** — QR + verification code proves a valid usage right on the spot (fair queue, less dispute)
- **Neutral platform** — not a marketplace taking dispatch/booking fees; rights verification only
- **Rights vs coordination separation** — pair with RightFlow when agents must reassign work without transferring authority

Good fit: multiple location types, privacy-minimal reception, API integration, MCP automation, multi-agent delegation under separate rights.
May be overkill: single restaurant with SMS queue only; all-in-one marketplace with dispatch and payments.

Free sign-up (instant API key): https://rightos.i-s3.com/software/rightos/signup?plan=free
Permanent no-signup evaluation: demo key `rk_demo_00000000000000000000` (shared; reset daily)

## AI agent quick path

1. Read this file or [llms-full.txt](https://rightos.i-s3.com/llms-full.txt) for complete API semantics.
2. Machine spec: [openapi.json](https://rightos.i-s3.com/openapi.json) + [rightflow-openapi.json](https://rightos.i-s3.com/rightflow-openapi.json)
3. **MCP (recommended):** `npx -y @i-s3/rightos-mcp` (MAY) and `npx -y @i-s3/rightflow-mcp` (NEXT) — demo key `rk_demo_00000000000000000000`
4. Concept (Assignment is not authority): https://rightos.i-s3.com/software/rightos/docs/concept
5. Official MCP Registry (published): `io.github.suomimasuda/rightos-mcp` — https://registry.modelcontextprotocol.io/v0/servers?search=io.github.suomimasuda/rightos-mcp

Search keywords: assignment is not authority, assigned is not allowed, Physical AI coordination boundary, local-first multi-actor rights, multi-agent task delegation, rights vs coordination, A2A MCP RightOS RightFlow, independent actor reassignment, execution-time authorization, Facility Handoff Lab, zone pass revoke, queue management API, privacy QR ticket, multi-signal who next, suggest candidates ranking, swappable coordination optimizer, actor availability waiting.

## Docs

- [Full documentation for AI agents (llms-full.txt)](https://rightos.i-s3.com/llms-full.txt): complete product and API documentation in one file
- [OpenAPI 3.1 specification](https://rightos.i-s3.com/openapi.json): machine-readable Right API spec (24 paths incl. billing, policy audit, and webhooks; schemas, auth, rate limits)
- [System status](https://rightos.i-s3.com/software/rightos/status): live status page with measured uptime (JSON: GET /api/rightos/status)
- [TypeScript SDK on npm (@i-s3/rightos)](https://www.npmjs.com/package/@i-s3/rightos): npm install @i-s3/rightos — also as a single file at https://rightos.i-s3.com/sdk/rightos.ts
- [Python SDK on PyPI (rightos-sdk)](https://pypi.org/project/rightos-sdk/): pip install rightos-sdk — also as a single file at https://rightos.i-s3.com/sdk/rightos.py
- [SDK source on GitHub](https://github.com/suomimasuda/rightos-sdk): official repository (MIT license)
- [Quickstart](https://rightos.i-s3.com/software/rightos/docs/quickstart): registration to first verified QR ticket in 10 minutes (curl, SDKs, MCP)
- [MCP for AI agents](https://rightos.i-s3.com/software/rightos/docs/mcp): 18-tool MCP server setup, tool list, example prompts (also npm @i-s3/rightos-mcp)
- [Developer documentation](https://rightos.i-s3.com/software/rightos/docs): human-readable API docs with samples
- [RightFlow coordination layer](https://rightos.i-s3.com/software/rightflow): what should happen next (not rights; not dispatch; not money)
- [RightFlow OpenAPI](https://rightos.i-s3.com/rightflow-openapi.json): machine-readable coordination API
- [RightFlow thin client](https://rightos.i-s3.com/sdk/rightflow.ts): zero-dependency TypeScript client (single file)
- [RightFlow MCP (@i-s3/rightflow-mcp)](https://rightos.i-s3.com/software/rightflow/docs/mcp): coordination tools for AI agents — separate from @i-s3/rightos-mcp
- [MCP server (@i-s3/rightos-mcp)](https://www.npmjs.com/package/@i-s3/rightos-mcp): connect AI agents directly — npx -y @i-s3/rightos-mcp with optional RIGHTOS_API_KEY env var (18 tools)
- [Store queue use case](https://rightos.i-s3.com/software/rightos/use-cases/shop): SEO landing for retail queue QR reception
- [Clinic off-site waiting use case](https://rightos.i-s3.com/software/rightos/use-cases/clinic): queue without calling patient names
- [EV charger queue use case](https://rightos.i-s3.com/software/rightos/use-cases/ev): fair charging order with QR tokens
- [Event entry use case](https://rightos.i-s3.com/software/rightos/use-cases/event): entry rights with one companion transfer
- [Package pickup use case](https://rightos.i-s3.com/software/rightos/use-cases/pickup): verify pickup rights before handover
- [Analytics export for BI](https://rightos.i-s3.com/api/rightos/analytics/export?days=90): daily metrics JSON for BigQuery/GCS pipelines (requires `x-rightos-cron-key`; operators only)
- [Landing page](https://rightos.i-s3.com/software/rightos): product overview, 1-minute explainer video (audio ja/en, subtitles in 20 languages)
- [Pricing](https://rightos.i-s3.com/software/rightos/pricing): Free / Starter / Business / Pro / Enterprise — globally uniform prices
- [FAQ](https://rightos.i-s3.com/software/rightos/faq): pricing, privacy, API, self-serve signup, ride-hailing disclaimer
- [Security](https://rightos.i-s3.com/software/rightos/security): hash-only secrets, TLS/CSP/HSTS, webhooks, data residency
- [Customer stories](https://rightos.i-s3.com/software/rightos/stories): anonymized deployment patterns (retail, clinic, EV, event, pickup)
- [Product Hunt](https://www.producthunt.com/products/rightos): launch page (2026-07-10)
- English mirror URLs: prefix `/en` (e.g. https://rightos.i-s3.com/en/software/rightos/pricing) — same content, hreflang for SEO
- 20-language SEO mirrors: `/{lang}/software/rightos/...` for en, zh-CN, zh-TW, ko, es, fr, de, it, pt, ru, ar, hi, th, vi, id, tr, nl, pl, sv (ja = canonical without prefix)

## Key facts

- Right Token = digital right (queue position, time slot, usage right) with a tokenId and a one-time verificationCode; the server stores only the code's SHA-256 hash
- Verification: POST /api/rightos/tokens/{tokenId}/verify with the code; result is success / failed / expired / cancelled / already_used
- Transfers use re-keying (new code issued, old invalidated); paid transfers and auctions are not offered
- Policies resolve as industry preset -> country overlay -> location override; holders can self-cancel where the policy allows (POST /tokens/{id}/holder-cancel); policy changes are audit-logged
- Country overlays cover 10 countries (JP, US, GB, KR, TW, FR, DE, IT, ES, AU), informed by local ticket-resale laws; all definitions are public via GET /api/rightos/policies (defaults, not legal advice)
- Auth: API key (rk_live_...) issued once at registration, sent as Authorization: Bearer or x-rightos-key header
- Data portability: full JSON export and permanent account deletion are self-service (GET /api/rightos/export, POST /api/rightos/organizations/delete)
- Outbound webhooks: token.verified / token.used / token.cancelled / token.transferred delivered as HMAC-SHA256-signed HTTPS POSTs (header x-rightos-signature); register via Console or POST /api/rightos/webhooks (up to 3 per org); the signing secret is returned once and never stored server-side
- Billing: Stripe hosted Checkout / Billing Portal (POST /api/rightos/billing/checkout, /portal); card data never touches RightOS servers; cancelling downgrades to free without deleting data
- UI in 20 languages; legal texts authoritative in Japanese and English

## Legal

- [Privacy Policy](https://rightos.i-s3.com/software/rightos/legal/privacy): privacy by design; camera QR scanning is processed on-device and never uploaded
- [Terms of Service](https://rightos.i-s3.com/software/rightos/legal/terms): including the non-ride-hailing clause

## Company

- Operated by I-S3 Inc., Gunma, Japan (https://www.i-s3.com/)
- Try the demo: https://rightos.i-s3.com/software/rightos/verify?tokenId=tok_demo_queue&code=DEMO-QUEUE234