Ready with a few material gaps

83/ 100

B
Grade: 70
Agent readiness
Board average 77 Scanned 17 hours ago

Every outstanding fix in one prompt for your coding agent. Rescan →

Task

What does dodopayments.com do and how do I use it? A fetch-only agent finds out.

12 fetches8 found4 missing

⋯home

/robots.txt⋯/sitemap.xml
/llms.txt⋯/llms-full.txt
/pricing
/docs
/openapi.json
mcp.json⋯MCP initialize
/privacy · /terms

⋯404 probe

every path the scanner fetched · replayed deterministically, no LLM

Evaluator notes

A fetch-only agent reached dodopayments.com over HTTPS in 219 ms and identified it from its title as “Billing & Payments Platform for AI-First Companies | Dodo Payments”. Little of the page survives without JavaScript, so a fetch-only agent sees mostly an empty shell. It found pricing and docs. It looked for an OpenAPI spec and an MCP server and found none.

Critical access needs attention

Whether an ordinary agent can enter, read, and operate the public site.

✓
Agents can reach the site
Crawler access and bot defenses.
4 / 4 passed
~
Core content is available
Useful content remains accessible without a fragile browser-only path.
1 / 2 passed
✓
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
2 / 2 passed
✓
Controls are understandable
Forms and interactive controls expose usable names and structure.
2 / 2 passed

Fix these gaps first

Critical access gaps come first, then the biggest remaining points.

01
OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts
02
Meta description 50–160 charactersMetadata
Add a meta description between 50 and 160 characters.
+5 pts
03
Twitter/X card type setShareable
Add <meta name="twitter:card" content="summary_large_image">.
+3 pts
04
Content readable without JavaScriptCritical access
Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
+3 pts
05
Agent manifest (MCP, A2A or ai-plugin)Agent-ready
Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
+2 pts

Audit the checks behind the score

Grouped by what they measure. Not-applicable checks are excluded from scoring.

Crawlable5 of 5 passed · 19/19 pts›

✓Served over HTTPS5/5
https://dodopayments.com/
✓Responds in under 1.5s5/5
219 ms to first byte
✓robots.txt present2/2
# ---------------------------------------------------------------------- # Searc…
✓sitemap.xml present2/2
/sitemap.xml → 200
✓Homepage is indexable5/5
HTTP 200

Metadata6 of 7 passed · 19/24 pts›

✓Title tag 10–70 characters5/5
"Billing & Payments Platform for AI-First Companies | Dodo Payments" (66)
✕Meta description 50–160 characters0/5
"The Billing & Payments Platform for AI-First Companies. From credit-based billing and usage metering…" (180)
→ Add a meta description between 50 and 160 characters.
✓Canonical URL set3/3
https://dodopayments.com/
✓Exactly one H14/4
1 × <h1>: "The Billing & Payments Platform for AI-First Companies"
✓Mobile viewport set3/3
width=device-width, initial-scale=1
✓Language declared2/2
<html lang="en">
✓Favicon declared2/2
/favicon.svg

Shareable2 of 3 passed · 11/14 pts›

✓Open Graph title, description and image8/8
title, description, image
✕Twitter/X card type set0/3
no twitter:card
→ Add <meta name="twitter:card" content="summary_large_image">.
✓Links to X or LinkedIn3/3
36 social link(s)

Converts3 of 3 passed · 17/17 pts›

✓Clear call to action8/8
12 CTA(s), e.g. "Download as SVG"
✓Pricing page linked6/6
→ /pricing
✓HTML under 2 MB3/3
330 KB of HTML

Measured1 of 1 passed · 6/6 pts›

✓Analytics installed6/6
detected: googletagmanager.com

Agent-ready15 of 19 passed · 32/46 pts›

✓Structured data (JSON-LD)4/4
@type: Organization, WebSite, WebPage, SoftwareApplication
✓Machine-readable pricing3/3
Offer / Product in JSON-LD
✓llms.txt present1/1
/llms.txt → 200, 4000+ chars
✓llms-full.txt present1/1
/llms-full.txt → 200
✓AI crawlers allowed in robots.txt2/2
none of 9 known AI crawlers blocked
✓No noai / TDM reservation2/2
no opt-out signals
✓Serves markdown on request1/1
Accept: text/markdown → text/markdown; charset=utf-8
✕OpenAPI spec discoverable0/7
no /openapi.json or /.well-known/openapi.json
→ Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
✕Agent manifest (MCP, A2A or ai-plugin)0/2
no manifest at /.well-known/{mcp,agent,ai-plugin}.json
→ Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
✓Docs or API link from the homepage3/3
homepage links to docs / API
✕Content readable without JavaScript0/3
28,883 chars of visible text, 8.5% of HTML
→ Server-render the key copy; a fetch-only agent sees none of what JavaScript paints later.
✓Semantic landmarks (main, single H1)3/3
<main> present, 1 × <h1>
✓Images have alt text2/2
184/184 images have alt
—Form fields are labelledn/a
✓Descriptive link text2/2
0/255 links say "click here" / "learn more"
✓Agent-friendly 404s2/2
nonexistent path → HTTP 404
✕Trust pages (privacy, terms, security)0/2
none of /privacy, /terms, /security respond
→ Serve /privacy and /terms at those paths; agents deciding whether to use you look for them.
✓Organization schema complete2/2
Organization has name, url, logo, sameAs, description
✓llms.txt says what you are and links out2/2
4000+ chars, has H1, has links
✓Contact route discoverable2/2
mailto:, /contact or /support link found

APIn/a›

—Spec parses and declares a versionn/a
—Operations have summaries and operationIdsn/a
—Error responses documentedn/a
—Auth scheme declaredn/a
—Versioned paths or serversn/a
—Spec within a model context budgetn/a

MCPn/a›

—Server answers initializen/a
—Tools listedn/a
—Tools carry descriptionsn/a
—Tool parameters have schemasn/a

Score history

83 17 hours ago
85 yesterday
85 yesterday

Fixed something? Scan again.

One scan per site every 10 minutes. Snapshot 2026-08-24T08:20:06.601Z.

← Back to the board