An open receipt any agent can write and anyone can check.
An agent saying “done” is a claim. A receipt records what was asked, what the agent was allowed to do, what it did, the evidence, and whether a person accepted it. Write it locally. Validate it without an account. Import it only when a person authorizes a shared ledger.
Place in the record
A receipt records the claim. Acceptance records the ruling.
OrgX keeps completion, verification, and human acceptance as separate states. The receipt carries what ran and the evidence it produced. The shared record adds the owner ruling and the next action.
- 01The agent completes the workIntent, authority, actions, artifacts, and evidence are recorded.
- 02The verifier checks the published barA pass or hold cites the exact rule and evidence used.
- 03The owner accepts or returns itThe human ruling stays distinct and becomes context for the next run.
Emission quickstart
Build locally, then emit JSON.
Install the public TypeScript package, construct a receipt with your runtime's own identifiers, then validate the resulting JSON here or through the public API.
Published SDK 0.3.0 and package sourcenpm install @useorgx/[email protected]
# emit receipt.json from your runtime
curl -X POST https://useorgx.com/api/v1/agent-work-receipts/validate \
-H 'content-type: application/json' \
--data-binary @receipt.jsonDownloadable conformance examples
Inspect a complete example.
Run a local receipt check, inspect a historical handoff failure and recovery, and see why a valid receipt can still await human acceptance.
Open the three reproducible proof packagesValidate an Agent Work Receipt
receipt.json
Account-free conformance check · not persisted · 256 KB maximum
5,876 characters
Contract boundary
Free emission. Paid assurance.
The open receipt does not require OrgX identifiers, storage, or authentication. Hosted OrgX becomes useful when people need a shared work graph, approval gates, verification, replay, reputation, or cost-to-outcome attribution.
- Local emission
- No account
- Validation
- No persistence
- Hosted import
- Workspace auth
- Public proof
- Human approval
Three-team proof cohort
Pressure-test the receipt on real agent delivery.
The pilot tracks emitter diversity, evidence completeness, verification, human acceptance, observed outcomes, and cost. Raw partner data stays private; a case study or public gallery entry requires an explicit human publication decision.