Laboratory › Developers › Playground
Playground
The trade
Every page on this site is script-free. That is not a performance preference — it is the property that guarantees no qualifier can be hidden, collapsed, lazily loaded or re-rendered after you read it. An integrity test asserts that no page contains a script tag, and it runs against the deployed bytes, not just the local build.
An in-page request builder needs JavaScript. Adding it would either break that guarantee across the portal, or create one special page where it does not hold — and a single exception is how such a rule stops being load-bearing.
What we would get in exchange: a form that constructs unauthenticated GET requests. The same job
is done by curl, by a browser address bar, and by the copyable examples, none of which require trusting
this site with script execution.
It requires JavaScript on the page. Every page here is script-free, which is what guarantees no qualifier can be hidden, collapsed or re-rendered after load — an integrity test enforces it. Trading that for a request builder over unauthenticated GET endpoints is a bad trade when curl does the same job.
The contract it will honour
Written down now, while nothing depends on it, so it cannot be invented differently later under pressure to ship.
- Read-only public endpoints only; never an admin or private path.
- No credential in browser storage.
- Object version and digest visible in every response view, and demo data marked as such.
Explore it now, without a playground
Every endpoint is a GET you can open directly:
- /api/index.json — everything else is discoverable from here
- /api/claims.json — the scientific index, empty by design
- /api/demo/claims/demo-0001/v2.json — a full fixture record
- /api/demo/queries/open-evidence-debt.json — a bounded query
- /demo/bundles/demo-0001-v3.json — a portable record, including its withdrawal
PreviousWebhooks
NextVerification