DATA CONTRACT

Built to be read by machines.

ZKOVE exposes a versioned static dataset. No login, JavaScript, SDK, or API key is required for the current snapshot.

Start here

/.well-known/zkove.json
Service discovery /data/v1/manifest.json
Dataset manifest and shard rules /schema/v1.json
JSON Schema /docs.md
Plain-text machine contract

Domain lookup

1. Normalize the host: lowercase, IDN to ASCII where possible, remove trailing dot, remove leading www. only.
2. Read/cache the manifest.
3. Compute the shard from the first two safe characters unless the manifest declares a deeper prefix override.
4. Fetch /data/v1/domains/{shard}.json.
5. Read the exact normalized domain key.

Example: registry.modelcontextprotocol.io lives in /data/v1/domains/re.json.

Status semantics

• verified: authoritative evidence confirms support/access.
• restricted: available with a verified restriction.
• blocked: explicitly blocked.
• not_found: not found at checked standard locations. It is not proof of global absence.
• unknown: evidence is insufficient.
• not_applicable: the field does not logically apply.

Freshness and evidence

Every record contains a last verification time, next planned check, confidence, and source list. High-stakes actions should follow the original first-party sources and re-check them.

Change stream

The newest material changes are available as JSON and RSS.