v1.0.0 · 34 rules · 1,000 sites scanned

CI for AI agents — for whoever's arriving.

UCP-awareMCP-awarellms.txt

Whether you ship the site or you ship the agent, Scovant gives both sides one comparable number.

&
◈
Defenders · Site owners

Is your site ready for AI agents?

Scovant scans, scores, and monitors your web presence for AI-agent compatibility.

  • ✓Continuous scoring · 34 rules
  • ✓Simulation replays for real flows
  • ✓Webhook on every deploy
  • ✓Public Verified badge for your footer
Scan your site free
https://
◎
Explorers · Agent builders

Don't waste tokens on a broken site.

Pre-flight any URL against the Scovant database before you launch an agent at it.

  • →Compatibility profile in one call
  • →See score, sims, known issues
  • →Free Compatibility API (soon)
  • →Webhook when target sites change
Check a target site
https://
Live AI-readiness scan

Sites losing AI agents — right now.

A live look at popular sites that AI agents struggle with. Each one is leaving automated traffic on the table. Scan yours free and see where you stand.

Live · refreshed every 6 hours
Want a card on this page?Pass the scan to qualify.
For agent builders

Pre-flight any URL against our database.

Check a target site's compatibility profile before your agent burns tokens on a broken checkout. Free, no signup, public data.

scovant://
Recent lookups
What you get back
# GET /v1/compat/blackwing602.com
{
"score": 92,
"verdict": "agent_ready",
"last_scanned_at": "...",
"known_issues": 0,
"recommended_action": "proceed"
}
The problem

Your site was built for people.
AI agents are showing up anyway.

By 2027, a third of e-commerce conversions will route through an AI agent. Today, almost half of them fail somewhere between "find the product" and "complete the purchase" — and your team has no idea where.
47%
of agent checkout attempts fail
Internal benchmark, 1,000 sites
$1.8B
in lost agent-driven GMV in 2025
Estimated · Gartner / Scovant
2 / 5
product pages have no usable structured data
Crawl of Alexa top 50,000
How it works

Three things, in order.

Run all three or just one. Most teams start with Scan, add Simulate when they see the score, and add Monitor when they're tired of getting paged on Sunday.
01◇

Scan.

Crawl the site, parse structured data, evaluate 34 compatibility rules across 7 categories including Universal Commerce Protocol. The same rules every time, so scores are comparable.

02◈

Simulate.

Drive a real browser through your buy / search / signup flows. An agent attempts what a human would. Where it breaks, you see why.

03◉

Monitor.

Hook up your deploy webhook. Every release is scanned. The second a regression appears, your team hears about it.

Compatibility score

One number your whole team understands.

Out of 100, weighted across up to seven categories — UCP and Citability count only where they apply. Every scan recomputes from scratch — no decay, no recency bias, no magic. The score on Monday is comparable to the score in Q3.

DiscoverabilityCan agents find this page? Robots, sitemap, crawl budget.
Structured dataSchema.org, Open Graph, microdata. The agent's context window.
ConsistencyCanonical, titles, headings. The site speaks with one voice.
ActionabilityForms, buttons, CTAs all targetable. Labels are real labels.
Trust signalsPrivacy, refund, contact, ownership. The agent says yes to checkout.
UCPUniversal Commerce Protocol profile so agents can transact, not just browse.
CitabilityHow readily AI search engines can quote your content. Content sites only.
Compatibility · scan #248
87/ 100
Strong, with a few rough edges.
+5
vs baseline
20 / 24
rules passed
421ms
median scan
CI for agents

Catch regressions before you ship.

Set a baseline. Wire up your deploy webhook. Every commit runs a full Scovant pass; we compare to baseline and ping the team when anything drops. Same way you catch broken tests — but for compatibility.

github actionscurlany ci pipeline
# from any CI or deploy step
curl -X POST scovant.com/api/ci/trigger \
-H "Authorization: Bearer $SCOVANT_TOKEN" \
-d '{"site_id":"<uuid>"}'
Score · last 60 days
acme.com · production
87
↑ +15 from start
May 7
Score dropped 14 pts after deploy 4f12a2. Hotfix shipped 3 days later.
Agent Fix Plan

Ship the fixes, not just the findings.

One credit turns your latest scan into a remediation plan: every issue, severity-ordered, with a concrete fix — enriched for your specific stack. It's plain Markdown with a shareable URL. Read it, hand it to your team, or pipe it straight into a coding agent and let it apply the fixes.

markdownpublic urlagent-readable
# the plan is a file — feed it to your coding agent
curl -s scovant.com/api/public/fix-plan/8fKq…w2.md \
| claude -p "apply these fixes to our site"
fix-plan.md12 issues · generated from scan · public link
# Agent Fix Plan — acme.com
## 1. Bot protection blocks agents · critical
Your WAF challenges every non-browser request. Allow the ScovantBot Verified Bot — or agents never reach the checkout you built.
## 2. Offer data missing · high
Product pages carry no machine-readable price. Add to your Product JSON-LD:
"offers": {"@type": "Offer", "price": "29.99", "priceCurrency": "USD"}
## 3. llms.txt absent · low
Publish /llms.txt so agents find your canonical content without crawling…
Pricing

Pay only for what you simulate.

Four credit packs, from $9 to $99. Every scan, simulation, and fix plan costs 1 credit — start with 3 welcome credits on the free plan.

Find out in 12 seconds.

Scan your site now — welcome credits included, no card required. We'll grade your site, surface the top issues, and you'll know more about agent compatibility than 90% of teams shipping today.