The shared invoice trial is free and starts right away. For your own recurring workflow, request team setup. We agree the scope and terms with you before activation.
The shared trial needs no account. Team setup starts with an enquiry, not an automatic subscription.
Try the shared job, write a supported standard, or check a record.
Setting standards and checking records remain free. Your own deployment and model usage have their own costs.
For recurring work that has to prove itself to someone else. Fourteen days free.
A workflow is one standard in force: one recurring kind of work under one set of requirements. The fourteen days start when your first standard is signed. We count the trial as working once a recipient has checked a result.
The first five teams. Team for one workflow, plus us in the room. Cancel any month.
We set the first teams up by hand while self-serve billing is built.
Name the work, the person who reviews it, and the systems involved. We confirm supported checks, setup needs, and commercial terms with you.
Set limits, approvals, and evidence requirements. Review what is supported before signing. You can write one now in the advanced editor.
Configure the gateway for the agreed routes and check its behavior. Run a bounded job, review the exported evidence, and have your recipient check the result.
The open-source gateway sits between an agent and its tools. It reads the configured policy, checks calls on the routes you put behind it, and writes receipts. A tool call that bypasses it is outside that coverage. Team anchoring sends a digest to a public log; sharing an evidence file is a separate choice.
Read the gateway setup commands and deployment requirements. Comparing records and verifying a downloaded file can run locally in your browser.
For a team that has started, an evidence source (a CSV export, an API, or a signed file delivery) can be described so its records carry the source’s confirmation. A reviewer must confirm the mapping. Prepare a source connection.
One real question your team cannot close today, bounded to one period and one source. Week one fixes the standard with the person who must rely on the answer and connects one read-only source. Week two produces the proof, tests the evidence for staleness, gaps, and alteration, and ends in a signed decision: accept, reject, or request inspection. A signed “not established” is a valid outcome.
Historical, read-only evidence at a point in time. Continuous assurance is outside that engagement; enforcement on live routes is a separate step you configure and activate.
ScopeBlind stores the room’s names, agreement, sample records, actions and results, and runs its sandbox gate and ledger. Browser signing keys stay in their browsers.
The installed gateway evaluates configured tool calls and writes receipts locally. Credential isolation and coverage depend on your agent, hooks and destination setup.
Your agent’s model and tools have their own data paths. Optional reporting sends disclosed receipts to a hosted standard page; exports share the files you select.
Files opened in Verify are checked in your browser without uploading their contents. A local CLI check can also run offline once its software and files are available.
Publishing a standard or creating a hosted share sends the selected content to the service. Downloaded exports and proof-carrying links disclose their contents to whoever receives them.