Loading workspace
A framework-neutral record of what was requested, who acted, what authority they had, what changed, and whether the result was verified. Emit it locally. Validate it without an account. Import it only when a human authorizes a shared ledger.
Place in the record
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.
Emission quickstart
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.
Package source and TypeScript examplenpm 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
receipt.json
Account-free conformance check · not persisted · 256 KB maximum
5,876 characters
Contract boundary
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.
Three-team proof cohort
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.