> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# REST API v1

> The supported OrgX REST resources, their purpose, and the best place to begin.

Start with the [API quickstart](/docs/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](/docs/api/entities/overview) 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](/docs/api/content-studio). 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:

```text theme={"dark"}
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](/docs/api/compatibility)
when maintaining an older integration.