# OrgX Docs

> Build accountable AI work with a published REST API, SDKs, and MCP integrations.

- [Build accountable work with OrgX](https://docs.useorgx.com/docs/home.md): Connect AI tools to shared organizational context or build accountable work into your product with the OrgX API.
- [What OrgX does](https://docs.useorgx.com/docs/introduction.md): OrgX keeps AI-delivered work connected to human decisions, evidence, and receipts.
- [Core concepts](https://docs.useorgx.com/docs/concepts.md): Six concepts explain the OrgX work record: Work, Decision, Artifact, Receipt, Process, and Event.
- [Connect your AI tools](https://docs.useorgx.com/docs/guides/toolkit.md): Connect OrgX to Claude, Cursor, Codex, VS Code, ChatGPT, OpenClaw, or another MCP client.
- [Product quickstart](https://docs.useorgx.com/docs/quickstart.md): Connect one AI tool, confirm its workspace context, and create visible work.
- [Pick up where you left off](https://docs.useorgx.com/docs/guides/synthetic-data-trial.md): Recover a decision, its evidence, and what would change it in a fresh conversation. Try it with example data and no local installation.
- [Wizard CLI](https://docs.useorgx.com/docs/guides/wizard-cli-onboarding.md): Complete reference for the @useorgx/wizard CLI — onboarding, MCP config, auth, surfaces, plugins, and workspace management.
- [OpenClaw Plugin Setup](https://docs.useorgx.com/docs/guides/openclaw-plugin-setup.md): Connect the OrgX OpenClaw plugin using secure browser pairing or a manual API key.
- [ChatGPT Integration](https://docs.useorgx.com/docs/guides/chatgpt-integration.md): Give ChatGPT organizational memory and human approval workflows through OrgX MCP.
- [MCP Client Setup](https://docs.useorgx.com/docs/guides/cursor-mcp-setup.md): Connect OrgX MCP from ChatGPT, Cursor, Claude, VS Code, and other remote MCP clients.
- [Integrations](https://docs.useorgx.com/docs/guides/integrations.md): Connect supported native integrations or external MCP providers to OrgX.
- [Agent Quickstart](https://docs.useorgx.com/docs/agent-ops/agent-quickstart.md): Establish an MCP connection and verify it with a safe, read-only call.
- [Agent Recipes](https://docs.useorgx.com/docs/agent-ops/agent-recipes.md): Small, reviewable MCP request patterns for orienting, inspecting, and resolving OrgX work.
- [Failure Playbooks](https://docs.useorgx.com/docs/agent-ops/failure-playbooks.md): Error recovery strategies for common MCP tool failures.
- [Tool profiles](https://docs.useorgx.com/docs/agent-ops/tool-profiles.md): Choose a focused MCP tool surface for a client or workflow.
- [How OrgX Works](https://docs.useorgx.com/docs/platform/architecture.md): A high-level overview of how OrgX turns goals into scoped, reviewable work across MCP clients, Mission Control, and connected tools.
- [Agents](https://docs.useorgx.com/docs/platform/agents.md): Canonical OrgX agent domains, selection logic, and why specialist routing improves outcomes.
- [Skills](https://docs.useorgx.com/docs/platform/skills.md): Reusable instructions that help compatible AI clients follow OrgX workflows and produce reviewable work.
- [Artifacts](https://docs.useorgx.com/docs/platform/artifacts.md): Recorded outputs of OrgX work, with available source links, review state, evidence, and verification.
- [Decisions](https://docs.useorgx.com/docs/platform/decisions.md): The human-in-the-loop checkpoint where you approve, reject, or guide agent work.
- [API quickstart](https://docs.useorgx.com/docs/api/quickstart.md): Create visible, accountable work with one required body field in under five minutes.
- [API overview](https://docs.useorgx.com/docs/api/overview.md): Start with work and receipts, then add organization, processes, events, and projections as your integration grows.
- [Authentication](https://docs.useorgx.com/docs/api/authentication.md): Use one server-side API key across authenticated workspace operations.
- [API clients](https://docs.useorgx.com/docs/api/clients.md): Call OrgX REST API v1 from JavaScript or Python with the same create-and-complete workflow.
- [Idempotency](https://docs.useorgx.com/docs/api/idempotency.md): Retry OrgX mutations safely with the Idempotency-Key header.
- [Errors](https://docs.useorgx.com/docs/api/errors.md): Handle one structured JSON error envelope across OrgX REST API v1.
- [Pagination](https://docs.useorgx.com/docs/api/pagination.md): Continue event and collection reads with the cursor returned by the API.
- [Versioning](https://docs.useorgx.com/docs/api/versioning.md): OrgX REST API v1 uses the /api/v1 namespace; portable schemas carry their own schema version.
- [Testing safely](https://docs.useorgx.com/docs/api/sandbox.md): Use a dedicated OrgX workspace and key for development, CI, and integration review.
- [Observability](https://docs.useorgx.com/docs/api/observability.md): Correlate OrgX API requests, retries, and event consumption.
- [REST API v1](https://docs.useorgx.com/docs/api/public-api.md): The supported OrgX REST resources, their purpose, and the best place to begin.
- [Create work](https://docs.useorgx.com/docs/api-reference/work/create.md): Create a visible work item with one required body field.
- [Complete work](https://docs.useorgx.com/docs/api-reference/work/complete.md): Complete work with evidence and receive its completion receipt.
- [Create an initiative](https://docs.useorgx.com/docs/api-reference/initiatives/create.md): Create an initiative with its first workstream and backlog.
- [List events](https://docs.useorgx.com/docs/api-reference/events/list.md): Read accepted workspace events in cursor order.
- [Prepare current context or safely rebootstrap a prior capsule](https://docs.useorgx.com/docs/api-reference/projections/prepare-current-context-or-safely-rebootstrap-a-prior-capsule.md): Returns freshly authorized context. Workspace capsule sources share a database snapshot; entity packs can include separate goal-frame reads. Opt into delivery_mode=delta for exact byte reconstruction against an acknowledged context version. Unknown bases rebootstrap. Transport identity never grants…
- [Get the Work Ledger](https://docs.useorgx.com/docs/api-reference/projections/get-the-work-ledger.md): Get work, evidence, and receipt totals for a time range.
- [Get process adoption](https://docs.useorgx.com/docs/api-reference/projections/get-process-adoption.md): Get behavioral and self-reported adoption measures for one process.
- [Get process value](https://docs.useorgx.com/docs/api-reference/projections/get-process-value.md): Get the evidence and outcomes attributed to one process.
- [Get metered usage](https://docs.useorgx.com/docs/api-reference/projections/get-metered-usage.md): Get immutable usage records and their current billing eligibility.
- [Read a domain controller status projection](https://docs.useorgx.com/docs/api-reference/controllers/read-a-domain-controller-status-projection.md): Returns the workspace-scoped shadow controller projection, including its latest run, signal, result, and audit linkage when available.
- [Reconcile one domain controller in shadow mode](https://docs.useorgx.com/docs/api-reference/controllers/reconcile-one-domain-controller-in-shadow-mode.md): Produces a typed shadow proposal candidate or no-op. A proposal is atomically admitted as a pending human Decision with canonical decision.proposed evidence and a neutral reconciliation Receipt. It grants no execution or policy authority.
- [List operating processes](https://docs.useorgx.com/docs/api-reference/operating-processes/list-operating-processes.md): List the workspace processes your team has proposed, confirmed, or activated.
- [Propose an operating process](https://docs.useorgx.com/docs/api-reference/operating-processes/propose-an-operating-process.md): Propose a process from observed work and return its first revision for review.
- [Get an operating process](https://docs.useorgx.com/docs/api-reference/operating-processes/get-an-operating-process.md): Get one process with its current revision, lifecycle state, and evidence references.
- [Confirm an operating process](https://docs.useorgx.com/docs/api-reference/operating-processes/confirm-an-operating-process.md): Confirm that a proposed process represents how the workspace intends to operate.
- [Activate an operating process](https://docs.useorgx.com/docs/api-reference/operating-processes/activate-an-operating-process.md): Activate a confirmed process so new work can flow through it.
- [Get the operating map](https://docs.useorgx.com/docs/api-reference/operating-map/get-the-operating-map.md): Get the workspace map of processes, stages, handoffs, and supporting evidence.
- [List handoffs](https://docs.useorgx.com/docs/api-reference/handoffs/list-handoffs.md): List responsibility transfers in the workspace.
- [Create a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/create-a-handoff.md): Create a responsibility transfer between two stages of work.
- [Get a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/get-a-handoff.md): Get one handoff and its current lifecycle state.
- [Claim a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/claim-a-handoff.md): Assign a queued handoff to the current actor.
- [Return a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/return-a-handoff.md): Return a claimed handoff to the queue.
- [Escalate a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/escalate-a-handoff.md): Escalate a handoff when it needs another owner or a faster response.
- [Cancel a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/cancel-a-handoff.md): Cancel a handoff that no longer needs action.
- [Fulfill a handoff](https://docs.useorgx.com/docs/api-reference/handoffs/fulfill-a-handoff.md): Fulfill a claimed handoff and record the result evidence.
- [List events](https://docs.useorgx.com/docs/api-reference/events/list-events.md): Read accepted workspace events in cursor order. Use the returned cursor to continue.
- [List missions](https://docs.useorgx.com/docs/api-reference/episodes/list-missions.md): List missions through the compatibility read available at this endpoint.
- [List discovery runs](https://docs.useorgx.com/docs/api-reference/discovery-runs/list-discovery-runs.md): List completed process-discovery runs.
- [Discover processes](https://docs.useorgx.com/docs/api-reference/discovery-runs/discover-processes.md): Analyze connected company signals and return process candidates with source evidence.
- [Get a discovery run](https://docs.useorgx.com/docs/api-reference/discovery-runs/get-a-discovery-run.md): Get one discovery result with its process candidates and evidence limits.
- [Propose a discovered process](https://docs.useorgx.com/docs/api-reference/discovery-runs/propose-a-discovered-process.md): Turn one discovered process candidate into a proposal for workspace review.
- [Import a receipt](https://docs.useorgx.com/docs/api-reference/receipt-import/import-a-receipt.md): Validate and store a portable Agent Work Receipt in the selected workspace.
- [Get receipt validation metadata](https://docs.useorgx.com/docs/api-reference/receipt-validation/get-receipt-validation-metadata.md): Get the supported receipt schema, limits, and a runnable example.
- [Validate a receipt](https://docs.useorgx.com/docs/api-reference/receipt-validation/validate-a-receipt.md): Validate a portable Agent Work Receipt without storing it.
- [Get workload diagnosis metadata](https://docs.useorgx.com/docs/api-reference/workload-diagnosis/get-workload-diagnosis-metadata.md): Get the workload diagnosis request schema and a runnable example.
- [Diagnose a workload](https://docs.useorgx.com/docs/api-reference/workload-diagnosis/diagnose-a-workload.md): Score a workload across time, agents, systems, authority, and accountability.
- [Estimate Content Studio work](https://docs.useorgx.com/docs/api-reference/content-studio/estimate-content-studio-work.md): Calculate the price and delivery range for a Content Studio request.
- [List Content Studio examples](https://docs.useorgx.com/docs/api-reference/content-studio/list-content-studio-examples.md): Browse completed Content Studio examples.
- [Create a Content Studio checkout](https://docs.useorgx.com/docs/api-reference/content-studio/create-a-content-studio-checkout.md): Create a secure checkout session for an accepted Content Studio estimate.
- [Receive Stripe events](https://docs.useorgx.com/docs/api-reference/content-studio/receive-stripe-events.md): Receive signed payment events from Stripe and update the matching order.
- [List work](https://docs.useorgx.com/docs/api-reference/work/list-work.md): List the work items you own in a workspace, newest first.
- [Create work](https://docs.useorgx.com/docs/api-reference/work/create-work.md): Create a work item and return its receipt. Send only a title to place it in the workspace Inbox, or supply a complete initiative hierarchy when you need precise placement.
- [Complete work with evidence](https://docs.useorgx.com/docs/api-reference/work/complete-work-with-evidence.md): Complete work and record its evidence and receipt.
- [Get a work item with its concurrency tokens](https://docs.useorgx.com/docs/api-reference/work/get-a-work-item-with-its-concurrency-tokens.md): Read one work item you own, together with the `concurrency` block that `POST /work/{taskId}/complete` accepts.
- [Create an initiative](https://docs.useorgx.com/docs/api-reference/initiatives/create-an-initiative.md): Create an initiative in one of three forms, discriminated by body shape:
- [Read an initiative, optionally with its full tree](https://docs.useorgx.com/docs/api-reference/initiatives/read-an-initiative-optionally-with-its-full-tree.md): Poll half of the scaffold loop. `include=tree` returns workstreams, milestones, and tasks with dependency edges, agent assignments, and estimates, assembled from one batched query set. `include=launches` lists launch summaries when they are available; otherwise it returns an empty list with an expla…
- [Generate a reviewable initiative plan proposal](https://docs.useorgx.com/docs/api-reference/initiatives/generate-a-reviewable-initiative-plan-proposal.md): Run the planning pipeline synchronously over your title, prompt, and optional explicit workstreams, and persist an immutable, digest-addressed proposal — agent assignments with confidence and rationale, milestone/task expansion, effort and budget estimates, and the generation receipt. No workstream,…
- [Read a stored initiative plan proposal](https://docs.useorgx.com/docs/api-reference/initiatives/read-a-stored-initiative-plan-proposal.md): Retrieve a proposal for review or diff. The returned `proposal_digest` is exactly the value a commit must echo. Status is one of proposed, instantiated (with `instantiated_initiative_id`), or expired.
- [List artifact types](https://docs.useorgx.com/docs/api-reference/artifacts/list-artifact-types.md): List the artifact types `POST /artifacts` accepts. Use a `type_code` from this list as the `artifact_type` when you register produced work.
- [List artifacts](https://docs.useorgx.com/docs/api-reference/artifacts/list-artifacts.md): List registered artifacts in a workspace, newest first.
- [Register an artifact](https://docs.useorgx.com/docs/api-reference/artifacts/register-an-artifact.md): Register a produced piece of work against the entity it belongs to. One of `artifact_url` or `external_url` is required. The target entity determines the workspace. Statuses that assert a human ruling (`approved`, `rejected`) are refused on this path; an automated reviewer records `eval_passed` inst…
- [List artifacts for one entity](https://docs.useorgx.com/docs/api-reference/artifacts/list-artifacts-for-one-entity.md): List the artifacts registered against a single entity, newest first.
- [Get an artifact](https://docs.useorgx.com/docs/api-reference/artifacts/get-an-artifact.md): Read one artifact with its entity relationships.
- [List decisions](https://docs.useorgx.com/docs/api-reference/decisions/list-decisions.md): List workspace decisions with their shape, urgency, and resolution state. Resolution itself happens in the OrgX app under a signed-in human.
- [Raise a decision](https://docs.useorgx.com/docs/api-reference/decisions/raise-a-decision.md): Create a decision request for a human ruling. Automated callers raise and read decisions; approving or declining stays a signed-in human action, recorded with lifecycle history.
- [Read one decision](https://docs.useorgx.com/docs/api-reference/decisions/read-one-decision.md): Poll a single decision by id. This is the read an automated caller waits on after raising a decision: it reports `status`, the resolution fields once a human has ruled, the `blocking` ids the decision is holding up, and the current `attention` request.
- [Ask a human to look at a decision](https://docs.useorgx.com/docs/api-reference/decisions/ask-a-human-to-look-at-a-decision.md): Raise or refresh attention on a pending decision and receive a poll handle. Use it when work is blocked and a person needs to rule: carry the option you would pick, why, and what it costs to wait.
- [Rule on a decision](https://docs.useorgx.com/docs/api-reference/decisions/rule-on-a-decision.md): Record a human ruling: `approved`, `adjusted` (approved with modifications captured in `resolution_context`), or `archived` (superseded or no longer relevant).
- [Control an agent run](https://docs.useorgx.com/docs/api-reference/runs/control-an-agent-run.md): Apply one control action to an agent run: `pause`, `resume`, `cancel`, or `rollback` (rollback takes a `checkpointId`). Each action is validated against the run's current state, so repeating an already-applied action is safe.
- [Pause, resume, retry, or cancel a work node](https://docs.useorgx.com/docs/api-reference/lifecycle/pause-resume-retry-or-cancel-a-work-node.md): Apply one lifecycle action to an initiative, workstream, milestone, task, or run you own. Actions cascade sensibly — pausing an initiative pauses its active runs. Each action is validated against current state, so repeating an already-applied action is safe.
- [Claim a duplicate-trigger fingerprint](https://docs.useorgx.com/docs/api-reference/deduplication/claim-a-duplicate-trigger-fingerprint.md): Claim a durable fingerprint for an event so local and cloud triggers reacting to the same signal fire once. The fingerprint derives from `source`, `event_key`, and the optional `initiative_id`; the first claimant wins until the claim expires or is released. The store fails closed — when it is unavai…
- [Describe the calling credential](https://docs.useorgx.com/docs/api-reference/credential/describe-the-calling-credential.md): Resolve who the calling credential is, which workspaces it reaches, and what it may do.
- [List the API error codes](https://docs.useorgx.com/docs/api-reference/api-discovery/list-the-api-error-codes.md): Every error code the API emits, with the status it carries, whether repeating the request can succeed, what happened, and what to do about it.
- [Get request schemas for v1 operations](https://docs.useorgx.com/docs/api-reference/api-discovery/get-request-schemas-for-v1-operations.md): JSON Schema for the request bodies the API enforces, generated from the same validators the handlers parse with, so the published shape matches the enforced shape.
- [Get the closed vocabularies](https://docs.useorgx.com/docs/api-reference/api-discovery/get-the-closed-vocabularies.md): The closed value sets the API enforces, read from the same constants the handlers validate against. A value absent here is a value the runtime rejects.
- [Preview or execute an initiative launch](https://docs.useorgx.com/docs/api-reference/launches/preview-or-execute-an-initiative-launch.md): Turn a committed plan into running work. This is the one operation on the API that spends your provider budget, so it is deliberately two calls.
- [Read a launch with its jobs, runs, receipts, and spend](https://docs.useorgx.com/docs/api-reference/launches/read-a-launch-with-its-jobs-runs-receipts-and-spend.md): The state of one launch: which targets dispatched, the runs they produced, the reservation receipts backing them, spend reserved and settled so far, and any decision currently blocking the initiative.
- [Stop a launch and release its spend reservation](https://docs.useorgx.com/docs/api-reference/launches/stop-a-launch-and-release-its-spend-reservation.md): The kill switch. In one call it releases the spend reservation, cancels the launch's queued and running jobs and runs, and restores the initiative status this launch promoted — and reports each count separately so you can see what actually stopped.
- [Entity map](https://docs.useorgx.com/docs/api/entities/overview.md): Every REST resource, every operation on it, where its IDs come from, and what is honestly not exposed — on one page.
- [Workspace](https://docs.useorgx.com/docs/api/entities/workspace.md): The tenant boundary: how workspace_id is resolved, where to read it, and which operations accept or require it.
- [Work item](https://docs.useorgx.com/docs/api/entities/work-item.md): The task resource behind POST /work and POST /work/{taskId}/complete — wire fields, versions, and where every referenced ID comes from.
- [Initiative](https://docs.useorgx.com/docs/api/entities/initiative.md): The initiative resource: scaffold and read it through /api/v1/initiatives, use the compatibility adapter for older full-field clients, and place work under it.
- [Decision](https://docs.useorgx.com/docs/api/entities/decision.md): The decision resource: raise decisions over REST, read their state, and understand why resolution is deliberately human-only.
- [Artifacts](https://docs.useorgx.com/docs/api/entities/artifact.md): Register work against an OrgX entity, read it back, and keep machine verification separate from human acceptance.
- [Agent run](https://docs.useorgx.com/docs/api/entities/run.md): The agent-run resource: read runs, control them with pause/resume/cancel/rollback actions, and submit their execution receipts.
- [Operating process](https://docs.useorgx.com/docs/api/entities/operating-process.md): The operating-process resource and its spec revisions: propose, confirm, and activate repeatable workflows with expected-version control.
- [Handoff](https://docs.useorgx.com/docs/api/entities/handoff.md): The handoff resource: transfer responsibility between stages with a six-state machine, idempotent writes, and expected-version control.
- [Discovery run](https://docs.useorgx.com/docs/api/entities/discovery-run.md): The discovery-run resource: evidence-gated workflow discovery, its process cards, and the propose step that feeds operating processes.
- [Ledger event](https://docs.useorgx.com/docs/api/entities/ledger-event.md): The event resource behind GET /events/stream: the envelope fields, cursor pagination, and the SSE lease for push delivery.
- [Receipt](https://docs.useorgx.com/docs/api/entities/receipt.md): The receipt resources: portable agent-work receipts you can validate and import, and the execution receipts OrgX records for completed work.
- [Episode](https://docs.useorgx.com/docs/api/entities/episode.md): A read-only mission view for clients that use the episode resource name.
- [Projections](https://docs.useorgx.com/docs/api/entities/projections.md): The four derived read resources — work ledger, adoption, value case, and meter usage — with their parameters and freshness metadata.
- [Content Studio API](https://docs.useorgx.com/docs/api/content-studio.md): Estimate, browse, and purchase Content Studio deliverables.
- [Stripe callback](https://docs.useorgx.com/docs/api/webhooks.md): Handle OrgX Content Studio payment callbacks from Stripe.
- [OrgX MCP](https://docs.useorgx.com/docs/api/mcp-protocol.md): Give every MCP-compatible assistant shared workspace context, accountable execution, and reviewable proof.
- [MCP Tools Reference](https://docs.useorgx.com/docs/api/mcp-tools.md): Reference for the current OrgX MCP tools and migration aliases.
- [MCP and REST parity](https://docs.useorgx.com/docs/api/mcp-rest-parity.md): Every orgx_* MCP tool mapped to the REST route(s) it calls — and an honest list of what each surface has that the other does not.
- [OpenClaw Plugin MCP Tools](https://docs.useorgx.com/docs/api/openclaw-plugin-mcp-tools.md): Code-generated reference for the OpenClaw plugin MCP bridge, including scoped domain availability.
- [Security & Privacy](https://docs.useorgx.com/docs/resources/security.md): How OrgX scopes access, records accountable work, and separates public progress from private model reasoning.
- [Availability](https://docs.useorgx.com/docs/resources/roadmap.md): Current OrgX products and integration paths.
- [FAQ](https://docs.useorgx.com/docs/resources/faq.md): Answers about OrgX capabilities, developer surfaces, access, and data boundaries.
- [LLM-ready documentation](https://docs.useorgx.com/docs/resources/llm-ingestion.md): Give an AI assistant the smallest authoritative OrgX source for the task.

## OpenAPI Specs

- [v1](/docs/openapi/v1.yaml)

## Optional

- [GitHub](https://github.com/useorgx)