> ## 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.

# Sandbox

> Use sandbox workspaces and test API keys for OrgX API reviews and CI.

Use a sandbox workspace for reviewer, CI, demo, and staging integrations. A
sandbox workspace keeps test initiatives, agent runs, decisions, and artifacts
separate from production work.

## Recommended Setup

1. Create or select a workspace used only for testing.
2. Generate an API key from **Settings** in that workspace.
3. Name the key after the integration, for example `stripe-review`.
4. Store the key as `ORGX_API_KEY` in your local environment or CI secret store.
5. Use deterministic test data and idempotency keys for write requests.

## Smoke Test

```bash theme={"dark"}
curl https://useorgx.com/api/client/bootstrap \
  -H "Authorization: Bearer $ORGX_API_KEY" \
  -H "Accept: application/json"
```

Expected result:

```json theme={"dark"}
{
  "ok": true,
  "data": {
    "workspace": {
      "id": "ws_test_123",
      "name": "API Sandbox"
    }
  }
}
```

## Data Safety

Sandbox workspaces still use real authentication and real authorization. The
difference is operational: the workspace is dedicated to test data, reviewers,
and automated checks.

Do not use a production workspace API key in public demos, external review
forms, or CI logs.

## Reviewer Notes

For API review submissions, provide:

* documentation URL: `https://docs.useorgx.com/docs/api/overview`
* base REST URL: `https://useorgx.com/api/client`
* hosted MCP URL: `https://mcp.useorgx.com/mcp`
* a sandbox workspace or reviewer login if hands-on testing is required