sk_ntl_sandbox_…, ak_ntl_sandbox_…).
The simulation actions listed below are available on every surface:
SDKs
Point the client at the sandbox and put your agent’s sandbox key inNATURAL_API_KEY. Your integration code is unchanged; client.simulations acts as the counterparty.
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 athttps://mcp.sandbox.natural.com. Connect it like the production server, alongside it if you want both:
invite_customer creates a synthetic test customer with pending invitations instead of emailing a real person. Below are the tools that are sandbox-only:
Organizations with issued cards also see these sandbox-only tools:
The SDKs and CLI don’t have methods for issued-card simulations yet.
list_payment_requests and cancel_payment_request work on the Sandbox MCP server too. Listing reads your requests; cancellation withdraws an open request you sent. The payment-request simulations act as the test payer, fulfilling or declining your outgoing request. They do not replace requester cancellation.