Sandbox
A test key for the whole platform
The keyless engine at /try runs a household without storing anything. A sandbox key adds what a plan adds — households you keep, with ids, versions, decisions, bulk import, signed webhooks and the console — so you can build the integration before you pay for it.
Worthune is built for United States households and is hosted in the United States. Its models apply US federal and state rules, and we do not currently support customers or client households outside the US. If you are outside the US, write to support@worthune.com before you buy.
What the key opens
- Every model in the catalog, over REST and the MCP server — model runs are never metered; the sandbox has a ceiling of 2,000 a day.
- Up to 5 stored households at a time (25 in all): create, patch, project (Monte Carlo up to 1,000 paths), decide, the picture, the decision history, bulk import, 2 webhook endpoints, the customer console and the usage dashboard.
- Both SDKs, with offline record verification.
What it does not
- White-label tenant configuration and embed tokens, which are on Launch and Growth.
- Verified narration and mapping drafts on our model key — over REST, send your own as the
x-model-keyheader and both work; over MCP those two tools are on Launch and Growth. - More than 5 active households, more than 300 stored-household calls an hour, or more than 30 days: the key expires, and 14 days later the sandbox's data is removed.
One sandbox per inbox (aliases fold to one). A fresh key can be requested during the current key's last week, up to 3 keys in all; the current key keeps working until it expires. When you are ready, Launch keeps the same organization and its households.