Sandbox and plans
What works without a plan, what a plan unlocks, and how to get a sandbox key.
Reads work without a plan
Reading works on any workspace: GET /workspace, brands, templates, jobs, assets and stats over REST, and the MCP read tools (readOnlyHint), which say so in their result. GET /workspace shows whether writes are allowed in plan.
Writes need a plan
Changing anything (creating or editing brands, generating pages, and every MCP tool that creates or changes something) needs a paid plan or a trial with a card on file. Without one those calls return 403 plan_required with the billing link in fix.url. Show the user fix.url and stop writing. A workspace created with create_workspace over MCP is read-only until you start a plan in the app.
Sandbox
A sandbox key starts with np_test_ and works on one shared demo workspace only, with low limits. It is for trying the API without a plan. To get one, Contact us for sandbox access.
| Limit | Sandbox value |
|---|---|
| Requests per key | 10 per minute |
| Credits per key | 30 per month |
| New pages in the sandbox | 10 per day, 1 job at a time |
Every sandbox response carries the header NeuroPage-Sandbox: true, and GET /workspace says sandbox: true. Other developers use the same workspace and can see what is in it, so do not send real lead data. A sandbox key never works on your own workspace.