Skip to main content
To start with the sandbox environment in Natural, get a sandbox key (sk_ntl_sandbox_…, ak_ntl_sandbox_…) by switching the dashboard to Sandbox. Simulation actions, the counterparty side of each flow, are first-class on every surface:

SDKs

Point the client at the sandbox and put your agent’s sandbox key in NATURAL_API_KEY. Your integration code is unchanged; client.simulations acts as the counterparty.
Both SDKs expose the full simulation surface. TypeScript names methods in camelCase, Python in snake_case:

CLI

Export a sandbox key and the sandbox base URL; every command then runs against the sandbox:
--base-url works per command if you prefer not to export NATURAL_BASE_URL.
natural login signs into production. Against the sandbox, authenticate with a sandbox key.

MCP

Natural runs a sandbox peer of the hosted MCP server at https://mcp.sandbox.natural.com. Connect it exactly like the production server, alongside it if you like:
The sandbox peer exposes every production tool. On this peer, invite_customer creates a synthetic test customer with pending invitations instead of emailing a real person. Below are the tools that are sandbox-only: