1. Sandbox fixtures — deterministic sample responses
The sandbox serves deterministic, schema-valid sample responses for representative REST operations as plain static JSON. Start at the index:fixture URL. Fetching a fixture returns the exact envelope shape the production endpoint returns, wrapped with the request metadata:
- Deterministic — fixtures are generated from the published OpenAPI examples (
scripts/generate-sandbox-fixtures.mjs) and only change when the API contract changes. Safe to snapshot in CI. - Schema-valid — every
response.bodyvalidates against the operation’s response schema in openapi.json. - Clearly synthetic — every fixture carries
"sandbox": true. Never treat fixture payloads as live data.
2. Anonymous, quota-free discovery on the live MCP server
The production MCP server athttps://worldmonitor.app/mcp lets you explore the full tool surface with no auth and no daily-quota consumption:
tools/list— the live tool inventory (compressed descriptions)describe_tool— full definition for any tool, including its output schemaprompts/list/prompts/get— pre-built workflow templatesresources/list— read-only resources (the seed-meta freshness resource is fully anonymous)
https://www.worldmonitor.app/docs/mcp is entirely public — search and read this documentation over MCP with no key at all.
3. A read-only data surface
Every data operation in the REST API and every MCP data tool is read-only: there is no call an agent can make againstapi.worldmonitor.app that mutates production data. The only mutating surfaces are account-scoped (API-key management, alert rules, notification channels) and require an authenticated session — they are deliberately absent from the sandbox.
Going live
- Issue a key at worldmonitor.app/pro and send it as
X-WorldMonitor-Key: wm_<40-hex>(or use OAuth 2.1 withscope=mcp). - Swap the fixture URL for the
productionUrlfrom the sandbox index — the envelope shape is identical. - Mind the rate limits and honor
Retry-Afteron 429.
