RightOS is privacy-preserving rights verification infrastructure by I-S3 (Japan). One API for store queues, clinic waiting, EV charging, events, and package pickup — without holding end-users' names or phone numbers. Embed via REST API, TypeScript/Python SDK, or MCP (18 tools for AI coding agents). Free sign-up, instant API key, first QR ticket in ~10 minutes. Globally uniform pricing — no sales negotiation. NOT a taxi or ride-hailing service. Verifies waiting order and access rights only.
No reviews yetBe the first to leave a review for RightOS
Hunter
📌
We built RightOS because vertical queue apps make you collect phone numbers and sign a new contract per industry.
Queue management should be infrastructure — one API across retail, clinics, EV, events, and pickup. Privacy by architecture, not a toggle. No end-user names or phone numbers.
AI agents can integrate today via MCP (18 tools) or OpenAPI — npx -y @i-s3/rightos-mcp
Try free (no credit card): https://rightos.i-s3.com/softwar...
Happy to answer questions about privacy-by-design, Policy Engine, or embedding in your stack.
Report
As a dev who'd actually try this, I'd love to see a sandbox/demo mode with mock endpoints and seeded data so you can stress-test queue logic without eating real API quotas while prototyping. Would also make the docs more hands-on.
Report
A webhook callback when a queue slot gets close would be huge for clinic and EV charging use cases — right now clients have to keep polling. Adding it alongside the SDK would save a lot of wasted requests.
As a dev who'd actually try this, I'd love to see a sandbox/demo mode with mock endpoints and seeded data so you can stress-test queue logic without eating real API quotas while prototyping. Would also make the docs more hands-on.
A webhook callback when a queue slot gets close would be huge for clinic and EV charging use cases — right now clients have to keep polling. Adding it alongside the SDK would save a lot of wasted requests.