Siteline

History

We welcome the category we helped define.

Siteline began scanning websites for AI agent usability in March 2026, before the category had a name. This page is the receipts: a timeline where every date is anchored to a versioned changelog entry, a git hash, or an external URL you can check yourself. No claim on this page is unverifiable.

Timeline

  • 2026-03-19 — Siteline goes live. The repository starts fresh that day (first commit 26de9bc, “Initial AIReady scanner scaffold”) and version 1.0.0 ships the same day: 4-pillar SNAP scoring (Signal, Navigate, Absorb, Perform) and the public REST API (changelog).
  • 2026-03-22 — Version 2.0.0: dynamic OG images, PDF export, MCP server, batch scanning, remediation tiers (changelog).
  • 2026-03-26 — Version 2.1.0: the two-layer scoring model. SNAP fundamentals set the floor; Agentic Enablement caps the grade (changelog).
  • 2026-04-17 — Cloudflare publishes isitagentready.com (blog published_at: 2026-04-17), bringing protocol-presence checks for agent-web standards to the category. A serious signal that the problem is real.
  • 2026-05-18 — Versions 2.2.0–2.4.0: promise-relative Layer 2 with commerce-gated Transactability, Standards Library v1 (RFC 8288 Link headers, RFC 9727 api-catalog, OAuth discovery, MCP server-card, Web Bot Auth), and the F1 probe-evidence ledger (changelog).
  • 2026-05-30 — Version 2.6.0: security hardening release; SSRF validation covers IPv4-mapped private IPv6 (changelog).
  • 2026-07-07 — Version 3.0.0: the composite scan. Every Siteline report now carries an attributed Cloudflare Agent Readiness baseline panel (informational, never feeds the grade) alongside Siteline’s SNAP quality judgment and open-standards conformance checks (Graceful Boundaries, GuideCheck). Grade-integrity fixes land in the same release (changelog).

The category today

Agent-readiness scanning now has real momentum, and that is good for everyone whose site needs to work for agents. Tools we track and respect:

  • Is It Agent Ready (Cloudflare) — protocol-presence checks across 21 standards in five categories. Its baseline now appears, attributed, inside every Siteline report.
  • Hard2Bit AI Scanner — agent-readiness scoring with a security angle.
  • SiteSpeakAI Agent Readiness Scanner — readiness checks oriented to chatbot and voice deployment.
  • Agent Checker — sends a live agent through a site and reports where it gets stuck.

Where Siteline differs: Cloudflare and presence checkers tell you the files exist. Siteline tells you whether they help an agent, and whether you conform to the open standards agents rely on. Content-validated probes, task-completion analysis, anti-cloaking detection, a per-probe evidence ledger, and standards conformance — not just file presence.

Why it works the way it does

  • Two-layer scoring. Presence checks alone reward empty files. SNAP fundamentals set a floor from observed usability; Agentic Enablement caps the grade based on the quality of dedicated machine resources. The versioned rubric history is public in the API changelog.
  • Promise-relative judgment. A portfolio site and a store make different promises to an agent. Commerce sites carry a Transactability purpose at a higher bar; a static site is never penalized for not being a store.
  • Passive-only scanning. The scanner never triggers rate limits, never attempts transactions, and never sends credentials. What it cannot verify passively, it labels as passive evidence and says so.
  • Detection precision. A signal feeds the score only when it is strong enough to be trusted; everything else is reported as informational. Wrong grades are worse than missing checks.