METHODOLOGY

Evidence before certainty.

The useful question is not whether a website is “AI friendly.” It is what a machine can actually verify, where, under which restrictions, and when that fact was last checked.

What enters the ledger

ZKOVE prioritizes domains where an agent may need to read information, call a machine interface, authenticate, coordinate through an agent protocol, or transact. Ordinary brochure sites are not added merely to inflate the count.

Evidence order

1. Live canonical machine endpoint or protocol artifact.
2. Official first-party documentation, terms, or API documentation.
3. Authoritative protocol registry or standards source.
4. First-party announcement or changelog.
5. Third-party material only for discovery or corroboration.

Unknown is not no

A missing standard file does not prove that a capability does not exist elsewhere. ZKOVE therefore distinguishes not_found from unknown, and both from an explicit blocked or positive verified state.

Time is the asset

The current web can be re-crawled. The state of the web years ago usually cannot. ZKOVE keeps append-only observations when a domain changes so later records do not erase what was previously verified.

Adaptive checks

Fast-changing agent infrastructure is checked more frequently. Stable domains gradually move to longer intervals. This keeps the system useful without requiring a wasteful full-web scan every day.

Independence

Donations, sponsorships, future paid history access, or commercial licensing never affect whether a domain is included or what status it receives. ZKOVE does not add affiliate parameters or paid rankings.