Sandbox

Steve's reference pages can execute requests against the hosted sandbox when the docs site is configured with a playground proxy.

What the playground uses

• A hosted sandbox deployment, not production.
• A server-side proxy that injects the sandbox demo API key.
• Strict allowlisting to documented /api/v1 routes only.
• IP-based rate limiting on the playground proxy.

Reset behavior

The hosted sandbox is reset every 2 hours.

Design your experiments with that in mind:

• treat the playground as disposable
• do not rely on submissions or review state surviving for long
• use clientSubmissionId values that are unique per run

What to expect

• Discovery endpoints are the best place to start: companies, workflows, and workflow versions.
• Session creation and submission run against the sandbox, but file uploads still go directly to R2 using pre-signed URLs.
• Downstream sync is configured for fake sandbox effects only.

Troubleshooting

• If the playground is hidden, the docs deployment is missing NEXT_PUBLIC_STEVE_PLAYGROUND_PROXY_URL.
• If a playground request returns 429, the proxy rate limit was hit. Wait for the reset window.
• If a workflow disappears, the sandbox reset probably reseeded a different state; reload the workflow list first.