Scan your site's authority for AI agents

The scan scores that across six dimensions from observable signals only. You raise your score by publishing the signal, not by asserting you are good. It runs in your browser — nothing is sent anywhere.

Scan a site now See the product family

Where KYE™ sits — SiteTrust, Cloudflare, KYE™

Three different jobs on the agent-readable web. They complement, they don't compete:

The red line — never a truth score. KYE™ Site Authority™ asserts only verifiable facts: evidenced · governed · disclosed · authority-exists. It never outputs a truth score, a trust score, or a "true/false" verdict about a site or its operator. Privacy-by-design: the scan evaluates only public, site-published signals — never your visitors' browsing data.

Run the scan

Tick the signals your site publishes — or load KYE™'s own published set to see a fully-disclosed authoritative posture over signals you can fetch and confirm yourself. Each row names the observable signal and what publishing it attests.

Contact

Your request goes to the KYE Protocol™ team, and a receipt with a reference number is emailed to you.

Name Email Organisation Topic Message I agree to the privacy policy. Send

Your Site Authority Score

Site Authority (0–100)

This is an OBSERVED score — a client-side heuristic over the signals you ticked, with no registry backing. A VERIFIED score is a registry-backed KYE™ Site Authority Registry™ record: a canonical site UUID, a Evidence Pack™, and a WORM change-history ledger ("archive.org for authority, not snapshots"). Observed is a snapshot; verified is authority.

The six dimensions

Your gaps — the signals to publish next

Each gap names a concrete, observable signal that was absent and what publishing it would attest. Closing a gap is a verifiable act, not a claim.

Claim your KYE™ Site Authority™ record

Turn this observed snapshot into a public, lookup-able, registry-backed record with an embeddable badge. Claiming goes through the same Universal Engagement Rail every KYE™ applicant uses — you choose exactly what to share.

Claim your KYE™ Site Authority™ record

The scan runs entirely client-side (scorer ); nothing leaves your browser until you choose to claim a record.

The registry + the embeddable badge

A verified record is published to the KYE™ Site Authority Registry™ — a Directory projection anyone can look up by the site's canonical UUID. The site UUID is the canonical kye:<class>:<trust-domain>:<subclass>:<local> ID (reused, never forked). Each record carries a public record page and the embeddable badge:

<script src="https://kyeprotocol.com/assets/site-badge.js"
        data-kye-site-id="kye:site:kyeprotocol-com:web:root"
        data-badge="standard"></script>

The badge renders the live registry posture and links to the public record — it never out-lives the record (Authority Finality™). A revoked or expired record flips the badge off. Its machine-readable metadata is honest by construction: {kye_site_id, entity, authority_status, agent_readiness_score, publishing_authority_score, last_verified, evidence_registry} — never a truth score.

What's verified today, and what's next

P1 ships the real scanner, the seeded registry, and the badge — and it tells you honestly what runs now versus what is deferred. We never fake a capability.

• Today (P1) The scan runs the real, deterministic scoring engine over the signals you submit or over KYE™'s own published set — six dimensions, specific gaps, honest observed-vs-verified labelling, a seeded registry, the embeddable badge, and a public record page.
• Phase 2 A browser extension and a live, SSRF-safe scan of an arbitrary remote domain (fetching that site's llms.txt / robots.txt / metadata server-side) — declared honestly as deferred external runtime rather than faked.

Canonical KYE™ surfaces referenced on this page: KYE Protocol™ · Universal Engagement Rail.