Skip to main content
A sandbox key lets you build and test direct API integrations before funding live calls. It checks authentication and request validation and returns simulated billing headers. It makes no provider requests, moves no credits, and creates no call history.
Use sandbox for request handling and automated tests. Verify provider-specific content with a live call before launch.

Create a key

In your enterprise workspace, open API Keys → Workspace keys, select Create key, and choose Sandbox. Store the returned lcrsb_… value; it is shown once. Sandbox keys support rotation and expiry through the same key-management tools as other workspace keys.

Make a test call

Make a sandbox call
Check the response: The balance never changes.

What you can test

Selected providers return approximate fixtures. Other registered providers return a generic sandbox response. These responses are unsuitable for verifying a provider-specific parser.

What needs a live connection

Use a funded connection for Recipes, live-quoted MPP and x402 services, provider content, and real payment behavior. Sandbox keys cannot access management APIs or MCP.
Sandbox does not detect reusing an idempotency key for a different request. Live calls do.
Sandbox tests leave no balances or test users to retire. If you create live test identities, follow Clean up integration tests.