Scan Results: https://docs.stripe.com

Vanity URL: scan.glintbase.xyz/stripe-scan

Leaderboard New Scan

52/100

Agent Readiness Score

AI-Friendly Docs

Parseable by AI models but has high token usage or lacks standard machine-readable hooks.

Share on X LinkedIn

Category Breakdown

discoverability10 / 25

readability20 / 25

token_efficiency0 / 15

execution12 / 25

structural10 / 10

Detailed Findings

📊

discoverability

10/25

llms.txt

llms-full.txt

↳ AI Agent Fix Prompt

Create an llms-full.txt file at the root of my documentation site.
This should contain the entire documentation merged into a single Markdown file.

Link Header (API Catalog)

↳ AI Agent Fix Prompt

Add a Link HTTP header to my homepage pointing to my API catalog or machine-readable documentation.
Format: Link: <https://api.example.com/catalog>; rel="api-catalog"

📊

readability

20/25

All checks passed — this category is agent-ready.

📊

token_efficiency

0/15

AI Agent Fix Prompt

My documentation is returning excessive HTML to AI agents.
Implement server-side content negotiation in my app.

When a request includes the header 'Accept: text/markdown',
return ONLY the technical content as clean Markdown.

Strip completely: navigation menus, footers, cookie banners,
sidebar links, breadcrumbs, social sharing buttons,
interactive widgets, and any HTML not containing technical content.

The response should contain only:
- Page title as H1
- Section headings as H2/H3
- Body text
- Code blocks with language tags
- Parameter tables
- No HTML tags, no CSS, no scripts

📊

execution

12/25

This category was analyzed using structural heuristics. Results reflect your documentation's observable patterns.

📊

structural

10/10

All checks passed — this category is agent-ready.