Trying Attest without an account
The developer landing page runs real checks on a demo token: the examples on the page, and a few sentences of your own, with no account, no key and nothing charged. What the demo allows and where it stops.
Last updated 12 September 2026
Trying Attest without an account
The panel on the front page of developer.quorumtech.ch sends real requests to Attest. Every example on it is a request and the response the service really gave, captured and re-run repeatedly before it was printed. Choose "Run this check" and the same request goes to api.quorumtech.ch now, and the answer replaces the recorded one. The "Your text" tab checks a claim of your own against text you paste.
What the demo is
The page holds no key of yours and asks for none. It mints a demo token through its own server, bound by hash to exactly the examples it prints, and sends the requests from your browser with that token. A demo token spends no credits and needs no account: its checks are metered under Quorum's own demo tenant and never billed.
The allowance per token:
- 20 checks in 30 minutes, the examples and your own text together.
- 5 of them on your own text, up to 20,000 characters of claim and evidence together.
- One claim per request, with the evidence in the request. Batches, drafts, bulk checks and MCP are not available to a demo token.
When the checks are spent, every button on the page turns into the way to keep going: a developer account, which starts with 250 credits for linking a card, nothing charged.
Reading the result
The response panel prints what a caller reads first: the verdict, the span ids it rests on, audit.referentialIntegrity, and the provenance block with the measurement hash that lets the check be replayed later. In the request beside it, the cited sentences are marked in place, so the verdict can be checked against the evidence in seconds. "Run it in your terminal" shows the exact request with the live token, as a curl command, so it can be sent from a shell while the token lasts.
A re-run can land on a different verdict from the recorded one. Hosted inference is not bit-reproducible. Where the sweep behind an example did not agree with itself, the page says so above the button, with the tally.
Where it stops
Nothing you paste is kept, on this page or anywhere in Attest. The demo is bounded on the API side: a pace on how many tokens are minted, a cap per token, and a budget for the whole demo each day, after which the page says so and opens again at midnight UTC.
To check your own documents at length, or from your own code, create a developer account and use the playground on these pages or an API key.
Related articles
Fetch a page in one call
The same work as the extract call, with the request held open until the page is done and the Markdown returned directly.
Watch an extraction
Server-sent events for one job: its state now, every change after it, and the finished page. Closes when the job does.
Read an extraction's progress
One frame of a job's state without its Markdown, for a progress bar that should not carry a page's text with every poll.
Collect an extraction
Poll a job that answered 202. Returns its state while it runs and the Markdown once it is done.
Still need help?
Ask Quincy in the chat bubble below, or write to support@quorumtech.ch and we will help you directly.