The rules
We take the path of the page address, in lower case, and use the first row whose words it contains, from the top. For example https://news.example.org/2026/11/live-link-roastery has live-link in its path. The column you read depends on the mode of the check: with text, or a link check without.
| Path contains | With text | Link check | Details |
|---|---|---|---|
live-link | VERIFIED_LIVE | LINK_LIVE | 200; one link rel="sponsored nofollow"; explicit "Sponsored" label in the headline area |
rel-absent | VERIFIED_LIVE | LINK_LIVE | 200; link with rel_raw: null |
no-label | VERIFIED_LIVE | LINK_LIVE | 200; disclosure.present known false |
no-text or no-link | LIVE_NO_FINGERPRINT | LIVE_NO_LINK | 200 |
not-live | NOT_LIVE | NOT_LIVE | 404 |
unverifiable | UNVERIFIABLE | UNVERIFIABLE | http_status unknown, reason robots_disallowed |
flip | alternates VERIFIED_LIVE / LIVE_NO_FINGERPRINT per monitor run | LINK_LIVE / LIVE_NO_LINK | gives silent_removal and newly_verified |
| anything else | sha256(url)[0] % 4 → live-link, no-text, not-live, unverifiable | same |
The time on each page, fetched_at, is the time the check was made. The matched text is the first 12 words of the text you sent. The link points to your own domain. Other sample values, such as the anchor text, are placeholders.
What test mode never does
- It never fetches a page and never starts the checking engine.
- It never charges. There is no hold and no ledger entry, and the balance endpoint says
not_charged. - It never counts in anything we publish about live checks.
- It never shows a live object to a test key, or the reverse.
How the pieces behave
Checks
POST /checks answers 202 with the check queued. About two seconds later, and within five, it is completed, with its events and webhooks. Poll as you would for a live check.
Monitors
A test monitor runs when you create it and when you call POST /monitors/{id}/run, which exists for test keys only. It does not follow its schedule. A page whose path contains flip changes on each run, which gives you silent_removal and newly_verified changes to build against.
A change looks like this:
JSON
{
"id": "chg_0Lr8KxA4jK6cAz8qX3sYhF",
"object": "monitor_change",
"livemode": false,
"monitor_id": "mon_0Lr8KtV3gH5bZy7pW2rXgE",
"check_id": "chk_0Lr8KsM9dE4zXv6oU1qWfD",
"previous_check_id": "chk_0Lr8KpQ2aB3xYw5nT7pUeC",
"url": "https://news.example.org/2026/11/live-link-roastery",
"kind": "silent_removal",
"before": {
"verdict": "LINK_LIVE",
"http_status": {
"known": true,
"value": 200
},
"rel_summary": {
"known": true,
"value": "sponsored nofollow"
},
"disclosure_present": {
"known": true,
"value": true
}
},
"after": {
"verdict": "LIVE_NO_LINK",
"http_status": {
"known": true,
"value": 200
},
"rel_summary": {
"known": true,
"value": null
},
"disclosure_present": {
"known": true,
"value": false
}
},
"created_at": "2026-11-02T09:30:03Z"
}Reports
A test report has sample: true, costs nothing and has no PDF (pdf.status is unavailable, with the code test_mode_sample). Its share page shows a band on every page saying that no page was fetched and that it is not a proof report.
Releases
A test release is never ordered, charged or sent to anyone. It moves through its states about every 30 seconds, so you can build against each state. A premium release stops at draft_ready until you approve it or ask for changes.
Webhooks
Test events are signed and delivered exactly like live ones, to the endpoints you made in test mode.
Try it
Follow the quickstart, or run a test check in the console. The docs page never sends a request for you.