Mitosis Sandbox / Test Environment
Mitosis runs a full sandbox at https://dev.mitosislabs.ai that mirrors every production surface — the REST API, the MCP servers, the OpenAPI spec, and the dashboard. Use it to exercise integrations without touching production data: data there is disposable and nothing you do on the sandbox has billing side effects.
Base URLs
| Surface | Production | Sandbox |
|---|---|---|
| API index | https://mitosislabs.ai/api/v1 | https://dev.mitosislabs.ai/api/v1 |
| OpenAPI spec | https://mitosislabs.ai/openapi.json | https://dev.mitosislabs.ai/openapi.json |
| Product MCP server | https://mitosislabs.ai/api/mcp | https://dev.mitosislabs.ai/api/mcp |
| Docs MCP server | https://mitosislabs.ai/api/mcp/docs | https://dev.mitosislabs.ai/api/mcp/docs |
| Dashboard | https://mitosislabs.ai | https://dev.mitosislabs.ai |
The OpenAPI spec lists both hosts in its servers array and carries a machine-readable x-sandbox extension with these URLs.
Verify you are on the sandbox
The API index self-identifies its environment, so an agent can confirm it landed on the sandbox rather than a production mirror before making any write:
curl -s https://dev.mitosislabs.ai/api/v1
The response includes:
{
"environment": "sandbox",
"sandbox": {
"baseUrl": "https://dev.mitosislabs.ai/api/v1",
"description": "Sandbox mirror of every production API and MCP route: disposable data, no billing side effects."
}
}
Production returns "environment": "production" from the same route. If you are writing an agent that can perform destructive or billable operations, check this field first and refuse to run test suites against a host that reports production.
What is mirrored
- Every REST route under
/api/v1(pricing, status, skills, search, jobs, batch) plus the authenticated Backups API (/api/snapshots). - Every MCP route — the product server (cortex_* memory tools behind OAuth 2.1 plus the public tools) and the docs server.
- Checkout flows run against Stripe test mode on the sandbox: test cards work, real cards are never charged.
- Auth: API keys and OAuth clients created on the sandbox are scoped to it; production keys do not work on the sandbox and vice versa.
Pointing your tools at the sandbox
- REST / SDK: swap the base URL from
https://mitosislabs.aitohttps://dev.mitosislabs.ai. - MCP clients: register
https://dev.mitosislabs.ai/api/mcpinstead of the production server URL. miCLI:mi config --office-manager https://m.dev.mitosislabs.aipoints the CLI at the sandbox backend; runmi config --office-manager https://m.mitosislabs.aito switch back.
Data lifecycle
Sandbox data is disposable. It is not backed up, may be reset at any time, and must never contain real customer data. Treat anything you create there as gone tomorrow.
Related
- Agent auth walkthrough
- Machine-readable pricing
- llms.txt — index of every machine surface
Looking for the docs index? Browse all guides.