Product screens recreated with synthetic data.
vendor: Acme Industrial invoice: INV-20841 amount: 12480.00 due: 2026-10-14
agentOS is the rule on a running workflow. A model step may draft an invoice, a ticket update, or a journal line. That draft is a proposal. It becomes a write only if every path from the model to the write passes a gate that is not the model — a person, or a keyword filter — and only if the write names a capability you put on the pipeline.
The capability list is short on purpose. A webhook is an https URL you declared, with the secret stored for the runtime, not in the prompt. A file write is a prefix. A dataset write is one dataset. A container is an image prefix you allowed. If a step tries to call something that is not on the list, the run stops. Prompt instructions are not the control.
When a write happens, the runtime records it: which pipeline, which block, which capability, which review allowed it, and a hash of the payload. You can answer “who posted this?” with “the runtime, after this approval,” not with “the model decided to.”
agentOS is not a chat widget, and it is not the screen where you name an agent. A coordinator block may call several Agent IO roles. This runtime still commits only after a non-model gate, inside a capability you declared. The in-console copilot can help you build a pipeline; it does not post to your ERP. Posting is this runtime.
Security review, finance, and the operator who will be asked, after the fact, why a number landed in the system of record. If a prompt is not an acceptable control, this is the product.
Platform, on every workflow you run in nQube. Production connectors and workflow runs start on Start.
Pricing →Synthetic example. Not a customer.
Extraction proposes vendor, amount, and due date. Invoices at or under $10,000 pass a keyword filter and the runtime posts them to the https endpoint you declared. Anything over that amount waits in Review. A person approves, edits, or rejects. Approval is the only way the large ones post. The secret that signs the request never enters the model. A month of this shape is a production workflow on Platform. Runs start on Start.
A write with no matching capability does not run, even if the prompt asks for it.
A second, ungated branch to the same write fails the graph. One approved path does not launder another.
Each write is a record: runtime, pipeline, capability, review, payload hash.
On the pipeline, list the systems a write may touch. Webhooks are https only. The signing secret is stored for the runtime, never in the block and never in the prompt.
An LLM step, a loop, or a model filter may draft the payload. That draft is not a commit.
Human review, or a keyword filter. A filter that itself asks a model is not a gate. Every path to a write needs one.
agentOS performs the write, meters it, and stores the commit record. The model does not hold the credential.
Platform Start is the self-serve canvas. A first pipeline we stand up with you is delivery, priced apart from the subscription.