ROX OS
rox os

The same API the interface uses.

Every screen of ROX OS is a call you can make yourself, with an API key from your account, header X-ROX-Key.

API

CallWhat it does
POST /api/workloadUpload a circuit or a problem file; recognised, with qubits, depth, two-qubit gates.
POST /api/planThe forecast table: one row per machine — queue, QPU, regime, sealed price. Read only.
POST /api/sealWrite the sealed preregistration (SHA-256). Nothing is sent.
POST /api/submitApprove the run. Simulator: free. Real machines: typed JA, owner role.
GET /api/status · GET /api/resultState (planned → sealed → approved → sent → analyzing → done) and the Tafel.
GET /api/edge/<machine>The edge: ratio over depth, both arms, from the last measured ladder.
GET /api/releaseThe public register, no key needed.

ROX MCP

Placeholder. Agents call ROX OS as a tool: plan, seal, run, read the Tafel — the same endpoints, wrapped as a Model Context Protocol server. Coming with the next phase.

Docs, GitHub, status

HomeROX OSThe lawProofSolutionsPricingDevelopersCompanyResearchOrderDenkerLegal © 2026 Kasprzak Capital Brain Investment in Commercial Enterprises and Management — FZCO · Dubai