CrawlCheck
Data · north star

Decisions to outcomes

verified agent actions backed by a fresh signed Resolve record, by action type, with false positives, disputes, unknowns and reversals counted. Last 30 days. Counts only: no caller, domain or agent is named.

The funnel

Signed decisions issued617
…resting on a fresh, measured answer277
counted since 2026-10-10
Receipts checked by the receiving site83
…and accepted by it25
Outcomes reported by agents9
…tied to the receipt they acted on1

By action

ActionDecisionsReceipts checked
read53939
cite100
connect230
transact451
administer00

Decisions: block 28 · warn 506 · require confirmation 54 · allow 19 · unsupported 10.

Where CrawlCheck was wrong

Allowed, then the site refused the agent0
Blocked, then the agent got through0
Outcomes that disagreed with Resolve0
Findings withdrawn on appeal0%

Only outcomes that name the receipt they acted on (decision_sha256) are placed. allowed_then_refused: CrawlCheck said allow and the site refused or challenged the agent. blocked_then_got_through: CrawlCheck said block and the agent reported success. Both are counted against CrawlCheck.

Per day

DayDecisionsReceipts checkedOutcomes
2026-10-12100
2026-10-115040
2026-10-10245259
2026-10-0911610
2026-10-082900
2026-10-07159530
2026-10-061700

Decisions are signed preflight receipts CrawlCheck issued; receipts checked are CrawlCheck-Receipt headers a receiving site looked up; outcomes are what agents reported after acting (POST /api/v1/outcome). Our own monitoring probes are never counted. Counts only: no caller, domain or agent is stored with these numbers.

Signed JSON: /api/v1/north-star · report an outcome: POST /api/v1/outcome with decision_sha256 · all metrics: /metrics.