AIScan.site

Is stripe.com AI agent ready? D · 41/100

Re-test this site

stripe.com

Lovable · 50% confidence
https://stripe.com/nl
D41 / 100
Grade D · Level 2ReadableWeak — agents will struggle with most tasks here.
Discoverability
100Content
59Bot Access
0Capabilities
0Commerce
0
Why we think this is Lovable (2 signals)
  • · /_next/static/ asset
  • · 'lovable' string in JS bundle

Scan history · 7 public scans of stripe.com

WhenScoreGradeSnapshot
Sep 2, 2026, 10:22 AM5c93917541/100DView →
Sep 2, 2026, 12:09 AM100a1d5741/100DView →
Aug 31, 2026, 3:17 AM96e3ec1441/100DView →
Aug 29, 2026, 2:07 PMd68c28b241/100DView →
Jul 22, 2026, 6:25 AM8b278c9b40/100DView →
Jul 5, 2026, 12:45 PM60eb80d740/100DView →
Jun 23, 2026, 12:16 PMfa850da435/100DView →
7 checks need fixing

6 failed · 1 partial out of 14 that apply to your site.

See top fixes

Fix automatically with AIScan

7 open checks (6 failing) can be handed to an AI agent: C1, C3, B2, P1, P4, M4, E2. Pick one route — each returns the full, check-by-check instructions.

Option A — Agent Skill (any runtime)
npx add-skill https://aiscan.site/aiscan-skill.json

Then ask your agent: “Fix the failing AI readiness checks for https://stripe.com/nl”.

Option B — Claude Code (CLAUDE.md)
curl -o CLAUDE.md https://aiscan.site/CLAUDE.md

Drop it in your project root, then ask Claude Code to fix the failing AIScan checks.

Option C — MCP client
https://aiscan.site/api/mcp

Tools: scan_website, get_fixes, get_grade. Call get_fixes { "url": "https://stripe.com/nl" }.

Option D — REST API
curl -s 'https://aiscan.site/api/public/scan?url=https%3A%2F%2Fstripe.com%2Fnl'

Returns every check with its complete fix guide.

Verify: Re-scan at https://aiscan.site after applying fixes, or run npx aiscan-cli https://stripe.com/nl. Individual checks that need a specific probe list it in their own guide.

Quick Wins

Top 3 fixes ranked by score impact

  • 01Fail

    Markdown content negotiation

    +8 pts if fixed

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    See full details
  • 02Fail

    Machine-readable pricing

    +6 pts if fixed

    Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.

    See full details
  • 03Fail

    Explicit AI bot rules

    +5 pts if fixed

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    See full details
Hand-off prompt for your coding agent7 issues
You are helping me raise my AIScan.site agent-readiness score.

Site: https://stripe.com/nl
Platform: lovable (50% confidence)
AIScan score: 41/100 — Level 2 (Readable)
Rubric: v2026.08.2

Please implement the fixes below. Where a file already exists (e.g. `public/robots.txt`, `public/llms.txt`), edit it; otherwise create it. After each change, briefly explain what you did so I can verify in the next scan.

### Failing checks
- **[C1] Markdown content negotiation** — FAIL
  - Evidence: Accept: text/markdown → 200 (text/html; charset=utf-8)
  - Fix: Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.
- **[M4] Machine-readable pricing** — FAIL
  - Evidence: no JSON-LD Offer found on /pricing or the homepage
  - Fix: Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.
- **[B2] Explicit AI bot rules** — FAIL
  - Evidence: 0 known AI agent(s) addressed in robots.txt
  - Fix: Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.
- **[C3] Structured HTML (title, meta, JSON-LD, single H1)** — PARTIAL
  - Evidence: h1: 2, title: true, meta description: true, JSON-LD: true
  - Fix: Ensure a single <h1>, <title>, meta description, and schema.org JSON-LD.
- **[P1] API Catalog (RFC 9727)** — FAIL
  - Evidence: 404 at /.well-known/api-catalog
  - Fix: Publish /.well-known/api-catalog linking to your OpenAPI descriptions.
- **[P4] OAuth discovery metadata** — FAIL
  - Evidence: auth-server: 404, protected-resource: 404
  - Fix: Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.
- **[E2] Machine-readable API description** — FAIL
  - Evidence: no /openapi.json, /api/openapi.json or swagger document found
  - Fix: Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.

### Constraints
- Do not change visible UI or copy.
- Keep changes additive and reversible.
- Prefer static files in `public/` over server routes when possible.
- For `llms.txt`, generate a real index of the site's most important pages.

How this score is calculated

Every check earns points against a weight. We divide the points you earned by the points that actually apply to a Lovable — so checks that don't apply never drag you down.

Essential
25 / 37 pts

Baseline every site should meet.

Recommended
9 / 28 pts

Strong signals most sites benefit from.

Bonus earned
0 signals

Emerging standards. Can only add points.

Not counted (7): B1, B3, P2, P3, M1, M3, E5 — either not applicable to this site profile or optional and not yet adopted. Expand any check to see the exact evidence we based it on.

Discoverability

100

Can agents find your pages? robots, sitemaps, llms.txt.

5

Content

59

Can agents read your content cleanly? Markdown, structured data.

211

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · C1

    What we found

    Accept: text/markdown → 200 (text/html; charset=utf-8)

    How to fix it

    Serve text/markdown when the client sends Accept: text/markdown, or publish /index.md.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Serve text/markdown on Accept negotiation

    When a client sends Accept: text/markdown, return a markdown rendering of the same content. The simplest path is to publish parallel .md files (e.g. /about → /about.md) and rewrite based on the Accept header.

    Test it

    curl -H "Accept: text/markdown" https://yoursite.com/
    Fix in ChatGPT Fix in Claude

Bot Access

0

Are AI crawlers explicitly allowed or blocked?

1

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · B2

    What we found

    0 known AI agent(s) addressed in robots.txt

    How to fix it

    Add explicit allow/deny rules for GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Add explicit User-agent blocks

    Don't rely on User-agent: * alone. Address each major AI crawler so your policy is unambiguous.

    Recommended block

    User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: Applebot-Extended
Allow: /
    Fix in ChatGPT Fix in Claude

Capabilities

0

Can agents do things? APIs, auth, MCP, Agent Skills.

3

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P1

    What we found

    404 at /.well-known/api-catalog

    How to fix it

    Publish /.well-known/api-catalog linking to your OpenAPI descriptions.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Publish an API catalog (RFC 9727)

    # Add to your homepage HTTP response headers
Link: </.well-known/api-catalog>; rel="api-catalog"

# And serve a JSON document at /.well-known/api-catalog:
{
  "links": [
    { "href": "/openapi.json", "rel": "service-desc", "type": "application/openapi+json" }
  ]
}
    Fix in ChatGPT Fix in Claude

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · P4

    What we found

    auth-server: 404, protected-resource: 404

    How to fix it

    Publish RFC 8414 / RFC 9728 metadata at the /.well-known/oauth-* endpoints.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Publish OAuth discovery metadata

    If your API supports OAuth, serve RFC 8414 metadata at /.well-known/oauth-authorization-server and/or RFC 9728 at /.well-known/oauth-protected-resource.

    Fix in ChatGPT Fix in Claude

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · E2

    What we found

    no /openapi.json, /api/openapi.json or swagger document found

    How to fix it

    Publish an OpenAPI 3.1 document at /openapi.json and reference it from /.well-known/api-catalog as a service-desc link.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Publish an OpenAPI 3.1 description

    Serve it at /openapi.json (or /openapi.yaml). Describe every public endpoint, its parameters, and its response schema.

    Advertise it

    Reference it from /.well-known/api-catalog as a service-desc link and from a Link response header.

    Link: </openapi.json>; rel="service-desc"; type="application/json"

    Content sites can skip this

    If you expose no programmatic API, this check is informational and costs you nothing.

    Fix in ChatGPT Fix in Claude

Commerce

0

Can agents transact? Catalogs, checkout, agentic commerce.

1

  • Your site is missing this right now, so AI agents can't use it. The fix below is what to change.

    ID · M4

    What we found

    no JSON-LD Offer found on /pricing or the homepage

    How to fix it

    Publish schema.org Offer / AggregateOffer JSON-LD on your pricing page with price, priceCurrency and the billing period, so an agent can answer "what does this cost?" without scraping prose.

    This is a Lovable project

    Edit files directly in the Lovable editor, or ask Lovable AI to apply these changes. Static files like robots.txt, llms.txt, and .well-known/* belong in the public/ folder — they're served from the site root automatically.

    Add Offer JSON-LD to your pricing page

    One block per plan (or one AggregateOffer covering the range) so an agent can answer "what does this cost?" without reading prose.

    Example

    <script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Pro",
  "offers": {
    "@type": "Offer",
    "price": "12.00",
    "priceCurrency": "USD",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "price": "12.00",
      "priceCurrency": "USD",
      "billingDuration": 1,
      "billingIncrement": 1,
      "unitCode": "MON"
    },
    "availability": "https://schema.org/InStock",
    "url": "https://example.com/pricing"
  }
}
</script>

    Keep it truthful

    The structured price must match the price a human sees; agents will quote it.

    Fix in ChatGPT Fix in Claude
Share the result

Share as a social image

Download a 1200×630 social card or post straight to X, LinkedIn or Facebook — sized for every feed.

AIScan share card — stripe.com graded D
Post on X Share on LinkedIn Share on Facebook

Tip: for X and LinkedIn, upload the downloaded PNG with your post so the card shows in the feed. Posts that include just the link will still preview AIScan.site.

Showcase your grade

Embed your AIScan badge

Drop this badge into your site footer, GitHub README, or docs. It links back to a fresh scan of stripe.com on AIScan.site.

AIScan.site grade D
HTML
<!-- AIScan.site agent-readiness badge -->
<a href="https://aiscan.site/?u=https%3A%2F%2Fstripe.com%2Fnl" target="_blank" rel="noopener" title="Agent-Readiness Grade D (41/100) — AIScan.site">
  <img src="https://aiscan.site/api/public/badge.svg?score=41&grade=D&host=stripe.com" alt="AIScan.site Grade D — 41/100" width="240" height="64" loading="lazy" />
</a>
Markdown
[![AIScan.site Grade D — 41/100](https://aiscan.site/api/public/badge.svg?score=41&grade=D&host=stripe.com)](https://aiscan.site/?u=https%3A%2F%2Fstripe.com%2Fnl)

Create a free account to track this site over time

  • Save scan history
  • See score trends
  • Re-scan anytime
Sign up free Already have an account? Sign in →

Dig deeper

Scan any site from Telegram
Open in Telegram

stripe.com is built on Lovable. AI-agent readiness for Lovable apps walks through the same checks on that platform.

Scan any site from Telegram
Open in Telegram

This page always shows the most recent public scan for stripe.com.

Browse all public scansScan your site