Methodology changelog
Every Scovant rating names the scoring model that produced it. A new model id means the method changed, not the site: compare two ratings only when they carry the same model. Each entry lists the models it introduced and the open-source Scovant Core release, if any.
Before 2026-10-02 the headline number was the Legacy Compatibility score (R1). R1 results keep their own model ids and are never rescored.
- Scovant Core 0.26.0
MCP endpoint detection reads real discovery evidence and AI Catalog server cards; owner checkout overrides apply to the checkout rules.
Technical Readiness:R2.1@7b46d2ed7f8bAgent Readiness:R2.1@50cf3e1d892e - Scovant Core 0.25.0
UCP checked against the official v2026-08-25 profile. The five UCP rules read the profile as the protocol's published business-profile schema defines it: lowercase transports, the dev.ucp.shopping.checkout capability, optional public signing keys. An HTML page served at /.well-known/ucp counts as no profile, and a profile declaring a later release than the one we check against is not measured.
Technical Readiness:R2.1@b0fe0dbf407bAgent Readiness:R2.1@082c77e580b6 - Scovant Core 0.20.1
On a SaaS site an add-to-cart or "buy now" control no longer counts as a product catalog: it sells a licence or a subscription, so a SaaS homepage is not asked for Product schema.
Technical Readiness:R2.1@7389c208c89eAgent Readiness:R2.1@4fe0c1811776 - Scovant Core 0.20.0
Rules apply by capability: product, offer and price rules apply only to a site with a product catalog, shipping and returns only to one that sells physical goods, checkout rules only to one that checks out. A rule that does not apply is not applicable instead of failed.
Technical Readiness:R2.1@939b502f6bc2Agent Readiness:R2.1@360d6b734b2e - Scovant Core 0.15.0
LLMS-SUPPLY-001 is retired: it judged packages merely named in prose and could not fire on real pages. No rating moves.
Technical Readiness:R2.1@67df90af85b0Agent Readiness:R2.1@5f7ebc816d3f - Scovant Core 0.12.0
The citability rule moves into Scovant Core. Outcomes are unchanged.
Technical Readiness:R2.1@08870acf35adAgent Readiness:R2.1@713d966d6cc9 - Scovant Core 0.11.0
The trust rules (returns policy, shipping information, citation metadata) and the llms.txt instruction-supply checks move into Scovant Core. Outcomes are unchanged.
Technical Readiness:R2.1@f63b48c203ffAgent Readiness:R2.1@ad54bd110311 - Scovant Core 0.10.0
The MCP, WebMCP, UCP, agent-payments and JavaScript-only-content rules move into Scovant Core. Outcomes are unchanged.
Technical Readiness:R2.1@a1cfa12d5385Agent Readiness:R2.1@fe02007e1dfe - Scovant Core 0.9.0
The structured-data and consistency rules (Product and Offer schema, price, availability, variants, headings, semantic HTML, page token cost, price and entity consistency) move into Scovant Core. Outcomes are unchanged.
Technical Readiness:R2.1@f611b402341fAgent Readiness:R2.1@682abbc4e288 - Scovant Core 0.8.0
The discoverability rules (AI-crawler policy in robots.txt, llms.txt, sitemap, Content-Signal, markdown for agents, link headers, crawl graph) run in the open-source Scovant Core. A check that failed on our side, such as a timeout or a server error, is recorded as not measured instead of as a finding.
Technical Readiness:R2.1@374ecc462a56,R2.1@0fe185be5a70Agent Readiness:R2.1@7f052630d16d,R2.1@633d6051a03c Agent Readiness (R2) replaces the Legacy Compatibility score (R1) as the headline number, with Technical Readiness beside it. Every rule reports pass, fail, not applicable or not measured, and each rating states how much of the site it could measure.
Technical Readiness:R2.1@3d6ec103cc71Agent Readiness:R2.1@51145f3d00a8
Machine-readable: /api/public/scoring/changelog