REST API v1 - OrgX Docs

Start with the API quickstart. It reaches a visible 201 with one required body field and shows the receipt returned by the operation.

Core resources

Resource	Use it to	First operation
Work	Create and complete accountable work	`POST /work`
Initiatives	Organize related work	`POST /initiatives`
Decisions	Raise decisions for a human ruling	`POST /decisions`
Artifacts	Register produced work as evidence	`POST /artifacts`
Runs	Control agent runs	`POST /runs/{runId}/actions/{action}`
Lifecycle	Pause, resume, retry, or cancel nodes	`POST /lifecycle`
Receipts	Validate or import portable proof	`POST /agent-work-receipts/validate`
Processes	Record repeatable operating flows	`POST /operating-processes`
Handoffs	Transfer responsibility between stages	`POST /handoffs`
Events	Synchronize accepted changes	`GET /events/stream`
Projections	Read workspace activity and outcomes	`GET /projections/*`

The entity map documents each resource’s fields, lifecycle, complete operation set, and ID provenance — including what is deliberately not exposed.

Public utilities

POST /agent-work-receipts/validate validates a receipt without storing it.
POST /doctor/workload evaluates whether a workload needs persistent coordination, authority, and evidence.

Content Studio

Content Studio pricing, showcase, checkout, and Stripe callback operations are documented in their own section. They are separate from the accountable-work learning path above.

Machine contract

Use the generated operation pages for exact parameters, request examples, response examples, and status codes. Use the published OpenAPI document for client generation:

https://useorgx.com/api/v1/openapi.yaml

Compatibility routes remain callable during their migration window but are absent from the navigation and machine index. See Compatibility when maintaining an older integration.