Request a sandbox (test) key by email — the endpoint behind the form at worthune.com/sandbox

Emails a wk_ key on the sandbox plan: the whole model catalog (2000 runs a day) and up to 5 stored households at a time (25 in all) over REST, MCP and the SDKs for 30 days, 300 stored-household calls an hour, Monte Carlo up to 1000 paths, 2 webhook endpoints, no white-label surfaces, narration and mapping drafts only on the caller's own model (a narrator or extractor model assigned at /api/v1/model-policy, or x-model-key over REST). The key is delivered by email, never in the response. One sandbox organization per inbox (aliases fold): a fresh key can be requested from the first day of the current key's last 7 days, 3 keys in all, and the current key keeps working until it expires. This is the form's endpoint: it needs the reCAPTCHA token the browser form obtains, so a bare JSON call answers 403 — a person requests the key once at worthune.com/sandbox, then any client uses it. Every well-formed, in-limit request answers the same 202 whether a key was issued or not: an inbox that already holds a plan, has used its keys, or is not yet in its renewal window is told why by email, never in the response, so the endpoint does not reveal who is a customer. Rate-limited per address (5 an hour), per inbox (1 a day, aliases folded), per company domain (10 a day; shared public mailboxes exempt) and site-wide (200 a day); the inbox, domain and site-wide counters are spent only when an email actually went out.