There is no sandbox header. An X-Limitguard-Mode: sandbox header is ignored, so a request that sends it with a live key is a normal, paid call. Keys starting with lg_test_ are refused in production with 401 Test keys not accepted in production.
POST /v1/reports/entity (and the MCP get_compliance_report tool) refuses sandbox keys with 403: reports are built only from real checks.
Sandbox Behavior
Property
Behavior
Data sources
No real sources called (KVK, sanctions, VIES, etc.)
Responses
Deterministic mock data: the same input always gives the same output
HTTP 429{ "error": "Sandbox rate limit exceeded (10 req/min). Use a real API key for higher limits."}
The response includes a Retry-After: 60 header.
Use Cases
Scenario
Recommendation
First-time integration
Sandbox key
CI/CD automated tests
Sandbox key in an environment variable; it can never trigger a paid call
Frontend development
Sandbox key
Load testing
Sandbox key (10 requests per minute per IP); never load test production
Demo / prototype
Sandbox key
Middleware Execution Order
Sandbox detection runs before rate limiting and x402 payment verification. A sandbox request to an endpoint the sandbox covers skips the payment check and is never charged. Any other priced endpoint charges a sandbox key like a free key. A sandbox request over the limit of 10 requests per minute per IP is answered with a 429 by the sandbox step itself.
Transitioning to Production
When ready to use real data, replace the lg_sandbox_ key with an lg_live_ key from the dashboard or POST /v1/keys/create, or pay per call with x402.No other code changes required. The same endpoints, request format, and response structure apply in both modes.