CrawlCheck Skip to content

Menu

For agents

The door: what an agent should know before it acts on a site

Quickstart: ask before you act

MCP, curl, Python, OpenAI Agents, Claude tool use, LangChain

The signed answer about any domain, laid out for a person

How each named agent behaves on sites, from verified requests

Capability registry

What sites declare agents can do, and what was verified

Verify a record

Check any answer or bundle on your own machine

Before you act

One signed answer, no key.

Read, cite, connect or transact: ask first, verify the receipt offline, keep it with the action.

Start in a minute

For sites

The door: scan free, have it fixed, keep it fixed

The checks behind the audit, one at a time

Is your business record right where agents look?

Compare two sites

Two domains, side by side, same measurement

What search and answer engines read from a video

Browser extension

The second vantage point: from your own address, after JavaScript

The record on your phone, with receipts

Your site

Measured as agents see it.

A free A–F audit with every defect named, no account. Fix it, then prove it held.

Developers

The door: the API by lane, the specs, SDKs, keys and quotas

Every endpoint, with a worked example from production

Resolve protocol

The signed answer: what it holds, how to verify it

SDKs: npm and PyPI

Typed clients, the offline verifier, conformance fixtures

The Ed25519 keys every answer is signed with

Every finding the measurement can raise, with its revision

Run the suite against your own implementation

Data

The door: census, conduct, proof and datasets, each with a denominator

Signed decisions, scans and crawler visits, counted

Proof and timestamps

How every record is sealed and anchored

CC BY 4.0 snapshots and the archive

SEO and AI tools, measured

The vendors that measure sites, measured by the same rules

Registry: media kits, llms.txt, entity graphs

Verified machine-readable profiles of real organisations

Learn

The door: guides, findings and the glossary, from measurements

The scan, stage by stage, and what each grade means

How to check one thing, with the rate at which it fails

Dated cases from real scans, with the bytes behind them

Every term the product uses, defined

Who sends each agent, what it reads, how to verify it

Pricing Sign in

Glossary · Proof and provenance

daily seal

The once-a-day act of hashing every report produced that day into one root and anchoring that root in the Bitcoin blockchain through OpenTimestamps.

What daily seal does not show

It proves a record existed by that date in that exact form; it does not prove the record was correct, or that anyone read it.

Where daily seal comes up on this site

Our proofs said “pending” for 26 days. The anchoring was fine.Our daily seal wrote the receipt into the record and never went back for the completed path.

Terms this definition uses

anchoring · OpenTimestamps

Related terms in Proof and provenance

Showing a record existed at a date without asking anyone to trust us.

transparency log · signed tree head · inclusion proof · log witness · split-view attack · cite-as link · as-of answer · citation anchor · canonical origin · signed absence · threshold verdict · OpenTimestamps · anchoring · Content hash · Manifest tampering · C2PA · CAWG training and data mining assertion · content-addressed storage · Merkle tree · SHA-256 · byline · dateline · trust center

Questions about daily seal

What is daily seal?

The once-a-day act of hashing every report produced that day into one root and anchoring that root in the Bitcoin blockchain through OpenTimestamps.

What does daily seal not show or guarantee?

It proves a record existed by that date in that exact form; it does not prove the record was correct, or that anyone read it.

Which area of the glossary does daily seal belong to?

Proof and provenance: Showing a record existed at a date without asking anyone to trust us.

← SHA-256 · byline →

See it in the full glossary · 731 terms across 19 areas.