AgenticWebScore
Scan

rubric v0.7 · scanned

stripe.com

34.9 BB L1 Basic Web Presence 11/51 checks passed

40 checks to fix. Open the fix list

Fix list

The files below list the 40 checks to fix. Each comes with the change to make and a shell command that repeats its measurement. Paste the prompt into the agent you already use, or download the bundle.

report.json
34.9
out of 100

BB thin L1 · Basic Web Presence

The site is reachable, but there are no agent-specific signals.

Held at this level by ai-rules and 2 more — the requirements for L2 Bot-Aware are not all met. Levels are cumulative: a high score does not skip one.

11/51 checks passed

Scan record

Target
https://stripe.com
Scanned
Requests
138
Duration
10.4s
Confidence
99% · high
Rubric
rubric v0.7

Fingerprint

e3ff6c7b07fd… verify this record

full hash

e3ff6c7b07fdf13092aea36e6e42f37ed4b907a54edbc48fb78ca7511de3e48b

Page as an agent receives it

Words
1892
Est. tokens
2554
Markup
687.5 KB
Language
en-PL

“Stripe | Financial Infrastructure to Grow Your Revenue”

Score unchanged since the last scan

Measured 3 hours ago. Previously 34.9/100 (BB) as of 12 October 2026, with the same check outcomes. After you ship a fix, press Re-scan now. A check that now passes adds its points to the score.

The current rubric evaluates 2 of its 61 checks against a clock: security-txt and status-page. They can change with no change to the site. A response slower than 12 s is reported as not measured, so the same bytes served slowly can move the score and the fingerprint.

Site profile could not be confirmed

Because we could not confirm the site profile, no profile-specific check was scored and none was turned into a recommendation. 9 profile-specific checks were reported as out of scope, not as failures. A missed optimisation is cheaper than an instruction that wastes your time. Declare the site profile and re-scan to have them measured.

  • · Two profiles are too close to separate: api (4) and saas (4), margin 0 < 2.
  • · Profile-scoped checks were not scored rather than guessed at.

Signal scores

  • API platform 4
  • SaaS 4
  • Marketplace 3
  • Services 2
  • E-commerce 1

By dimension

Weighted within each tier pool. Commerce checks are in scope: commerce path (/products).

Scores by dimension
Dimension Score Pass Partial Missing Not scored
Protocol Discovery 25% 16.7 1 4 9 3
Content Accessibility 22% 54.5 6 1 5 3
Discoverability 20% 40.9 3 1 7 0
Bot Access Control 18% 17.9 1 2 5 0
Commerce Protocols 15% 21.7 0 2 4 4

All 61 checks

Passed 11

  • Homepage open to agent access — HTTP 200 text/html; charset=utf-8 with 704020 bytes and 1892 words of visible text.

    If an agent cannot read your site, every other check is moot. Cloudflare began blocking AI crawlers by default in 2025, with signed agents routed separately.

    Observation

    HTTP 200 · text/html; charset=utf-8 · 704020 bytes · 413 ms · final https://stripe.com/en-pl
    id
    reachable
    weight
    3
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • robots.txt with agent directives — 3 groups, 21 rules, 2 named agent groups (ia_archiver, rogerbot), Sitemap declared.

    The front door for agent traffic (RFC 9309).

    Observation

    HTTP 200 · text/plain; charset=utf-8 · 643 bytes · 297 ms · Sitemap: https://stripe.com/sitemap/sitemap.xml User-agent: ia_archiver Allow: /docs/api Allow: /docs/api$ Disallow: /docs Disallow: /docs$…
    id
    robots-txt
    weight
    2
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 9309

    Reproduction command and full detail →

  • /llms.txt published and well-structured — H1 "Stripe", blockquote summary, 31 H2 sections with 308 markdown links, 69923 bytes. The scan requested 7 links it names, and each answered 2xx. Not requested: 36 links on another origin and 264 same-origin links (the scan samples up to 6).

    The most widely adopted contract for making a site legible to agents. In the curated corpus we measured, 46% of sites published one and the average quality score was 37 out of 100 — adoption is not the same as usefulness.

    Observation

    HTTP 200 · text/plain; charset=utf-8 · 69923 bytes · 341 ms · headings: Stripe | Payments | Connect | Payment Links | Checkout | Elements | Billing | Invoicing | Tax | Atlas | Terminal | Rada…
    id
    llms-txt
    weight
    3
    points
    1.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    llmstxt.org

    Reproduction command and full detail →

  • Title and summary metadata — Title is 54 characters (band 50-60) and description is 148 characters (band 120-160).

    This is how an agent learns what a page is about without opening it.

    Observation

    title(54): Stripe | Financial Infrastructure to Grow Your Revenue | description(148): Stripe is a financial services platform that helps all types of businesses accept payments, build flexible billing models and manage money movement.
    id
    meta
    weight
    2
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • JSON-LD structured data — 1 JSON-LD block parsed with a schema.org @context declaring WebSite (7 @types in total).

    The entity type becomes unambiguous to a machine. Without authoritative data, an agent answers from whatever it can scrape.

    Observation

    blocks: 1 total, 1 non-empty, 1 parsed; schema.org @context: yes; @types: WebSite, Organization, Person, ImageObject, ContactPoint, Place, PostalAddress
    id
    jsonld
    weight
    3
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org

    Reproduction command and full detail →

  • Language declaration and multilingual access — html lang="en-PL" with 89 hreflang alternates, all with absolute hrefs plus a self-reference and x-default.

    A wrong language tag makes an agent misread the content.

    Observation

    html lang="en-PL"; alternates: x-default -> https://stripe.com/, en-us -> https://stripe.com/, es-us -> https://stripe.com/es-us, zh-us -> https://stripe.com/zh-us, en-ae -> https://stripe.com/ae, de-at -> https://stripe.com/at, en-at -> https://stripe.com/en-at, en-au -> https://stripe.com/au, nl-be -> https://stripe.com/nl-be, fr-be -> https://stripe.com/fr-be, de-be -> http…
    id
    lang
    weight
    1
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • Content that needs no JavaScript — 12911 characters of static text and 2 H1s are in the HTML before any JavaScript runs.

    If content is only produced client-side, the page is empty for agents that do not run JavaScript.

    Observation

    static characters: 12911; H1 in static HTML: 2; characters inside noscript: 0; markup characters: 702748
    id
    no-js-fallback
    weight
    2
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • Per-page content separation (no SPA fallback) — Homepage and /about ship different titles ("Stripe | Financial Infrastructure to Gr…" vs "About Us | Stripe") and different main text (12% word overlap).

    A catch-all route returning the same skeleton for every URL makes pages indistinguishable to an agent.

    Observation

    compared / vs /about; titles "Stripe | Financial Infrastructure to Grow Your Re…" / "About Us | Stripe"; skeleton 24%; main-text word overlap 12%; main text 2070 characters
    id
    spa-fallback
    weight
    2
    points
    1.00
    standard
    Experimental — An early convention that may still change shape.

    Reproduction command and full detail →

  • Responsive markup — viewport content "width=device-width, initial-scale=1, viewport-fit=cover" sets width=device-width and leaves zoom unrestricted.

    Agent browsers mostly run at mobile scale.

    Observation

    viewport meta: width=device-width, initial-scale=1, viewport-fit=cover; media queries on the page: 0
    id
    viewport
    weight
    1
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • security.txt (RFC 9116) — security.txt at /.well-known/security.txt declares 1 Contact and an Expires 2026-12-31T23:59:00.000Z in the future. Not scored: its Policy URL is on hackerone.com, which this scan does not request.

    Provides a responsible disclosure channel for agent-related security incidents.

    Observation

    Contact: https://hackerone.com/stripe Expires: 2026-12-31T23:59:00.000Z Acknowledgments: https://hackerone.com/stripe/thanks Preferred-Languages: en Canonical: https://stripe.com/.well-known/security.txt Policy: https://hackerone.com/stripe#overview Hiring: h…
    id
    security-txt
    weight
    1
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 9116

    Reproduction command and full detail →

  • Documentation reachable — Documentation is reachable at /en-pl/guides/best-practices-for-launching-and-scaling-platform-payments (homepage anchor) and returns HTTP 200 text/html with 4130 readable words.

    An agent needs documentation to complete an integration on its own.

    id
    docs
    weight
    1
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <!-- Homepage <head>: tell agents where the public docs are -->
<link rel="service-doc" href="/docs/" type="text/html">

<!-- Homepage body: a real link, so crawlers and users both find it -->
<a href="/docs/">Documentation and API reference</a>

    Reproduction command and full detail →

Partial 10

  • Canonical and hreflang discipline — Canonical points at /en-pl, not the homepage URL that was reached (/).

    An agent needs one consistent URL per important page.

    Observation

    https://stripe.com/en-pl
    id
    canonical
    weight
    2
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <link rel="canonical" href="https://example.com/">
<link rel="alternate" hreflang="en" href="https://example.com/">
<link rel="alternate" hreflang="de" href="https://example.com/de/">
<link rel="alternate" hreflang="x-default" href="https://example.com/">

    Reproduction command and full detail →

  • Semantic heading structure — 2 H1 elements on one page while the rest of the outline (5 H2s, 25 H3s) is well formed.

    A single H1 and a consistent H2 structure let the content be split correctly.

    Observation

    outline: H1 H1 H2 H3 H3 H3 H3 H3 H3 H2 H2 H3 H3 H3 H3 H3 H4 H4 H4 H3 H4 H4 H4 H4 H4 H4 H4 H4 H4 H4 H3 H4 H4 H4 H2 H3 H3 H4 H4 H4 H3 H4 H4 H4 H2 H3 H3 H3 H3 H3 H3 H3 H3 H3 H4 H4 H4
    id
    headings
    weight
    2
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.
    standards
    WCAG 2.2

    Fix

    <main>
  <h1>Agent readiness for e-commerce teams</h1>
  <p>A five-dimension audit of how well a store serves autonomous AI agents.</p>

  <section>
    <h2>What we measure</h2>
    <p>Discovery, content, bot access, protocol and commerce signals.</p>

    <h3>Structured data</h3>
    <p>Entity types an agent can quote without having to guess.</p>
  </section>

  <section>
    <h2>How the score works</h2>
    <p>Fifty-two weighted checks, graded from C to AAA.</p>
  </section>
</main>

    Reproduction command and full detail →

  • Named AI bot rules in robots.txt — 0 of 18 named AI bots addressed: the only 10 robots.txt rules sit in the User-agent: * group.

    Naming agent crawlers explicitly is the first step to being visible in agent traffic.

    Observation

    Sitemap: https://stripe.com/sitemap/sitemap.xml User-agent: ia_archiver Allow: /docs/api Allow: /docs/api$ Disallow: /docs Disallow: /docs$ Disallow: /bitcoin/refund Disallow: /sources/refund Disallow: /sources/sepa_mandate Disallow: /sour…
    id
    ai-rules
    weight
    2
    points
    0.50
    standard
    Draft — A published specification that is not yet ratified.
    standards
    RFC 9309

    Fix

    # robots.txt - named AI agents, each with a rule of its own.
User-agent: OAI-SearchBot
Allow: /
User-agent: ChatGPT-User
Allow: /
User-agent: Claude-User
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: GPTBot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: *
Allow: /
Sitemap: https://example.com/sitemap.xml

    Reproduction command and full detail →

  • Crawl rate declaration — Crawl-delay: 2s appears only under User-agent: rogerbot, which names no AI crawler and no wildcard, so 0 of 1 declared Crawl-delay line applies.

    Cloudflare's Verified Bots policy drops AI crawlers that ignore crawl-delay.

    Observation

    Sitemap: https://stripe.com/sitemap/sitemap.xml User-agent: ia_archiver Allow: /docs/api Allow: /docs/api$ Disallow: /docs Disallow: /docs$ Disallow: /bitcoin/refund Disallow: /sources/refund Disallow: /sources/sepa_mandate Disallow: /sour…
    id
    crawl-delay
    weight
    1
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    # robots.txt - a crawl rate inside the group it applies to.
User-agent: *
Crawl-delay: 1

User-agent: OAI-SearchBot
Crawl-delay: 1

User-agent: GPTBot
Crawl-delay: 10

    Reproduction command and full detail →

  • Structured pricing information — No structured offer is present in the homepage JSON-LD and the only price signal is prose copy reading "$1.9".

    An offer without a price cannot be compared by an agent — you drop out of consideration.

    id
    pricing-structured
    weight
    2
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/Offer

    Fix

    {
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Agent Readiness Audit",
  "offers": {
    "@type": "Offer",
    "price": "490.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceSpecification": {
      "@type": "UnitPriceSpecification",
      "price": "490.00",
      "priceCurrency": "USD"
    }
  }
}

    Reproduction command and full detail →

  • Service/product scope machine-readable — Homepage JSON-LD carries only 2 generic Organization or WebSite nodes across 2 model types, so what is offered and to whom is not readable.

    An agent must be able to answer "what does this site offer, and to whom".

    id
    service-schema
    weight
    2
    points
    0.50
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    {
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Agent readiness audit",
  "serviceType": "Website agent-readiness audit and remediation",
  "provider": { "@type": "Organization", "name": "Example Inc.", "url": "https://your-domain.example" },
  "areaServed": [{ "@type": "Country", "name": "United States" }],
  "audience": { "@type": "BusinessAudience", "name": "E-commerce and SaaS teams" }
}

    Reproduction command and full detail →

  • Structured contact information — Homepage JSON-LD declares 1 organization node with 0 contact details while the page itself carries 0 plain-text contact signals.

    An agent must know where to reach you before starting a transaction, or when something fails.

    id
    contact
    weight
    1
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/Organization

    Fix

    {
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Inc.",
  "url": "https://your-domain.example",
  "contactPoint": [
    {
      "@type": "ContactPoint",
      "contactType": "technical support",
      "email": "agents@your-domain.example",
      "telephone": "+1-555-0100",
      "availableLanguage": ["en"]
    }
  ]
}

    Reproduction command and full detail →

  • Service status and changelog feed — A status document is advertised at /status (HTTP 200) but the homepage advertises 0 Atom or RSS changelog feeds.

    An agent should be able to learn about outages and API changes in a machine-readable way.

    id
    status-page
    weight
    1
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <!-- Homepage <head>: advertise machine-readable status and history -->
<link rel="alternate" type="application/atom+xml" title="Service status"
      href="/status/feed.atom">
<link rel="alternate" type="application/atom+xml" title="Changelog"
      href="/changelog/feed.atom">

<!-- Homepage body: links a user (or a crawler) can follow -->
<a href="/status/">Service status</a>
<a href="/changelog/">Changelog</a>

    Reproduction command and full detail →

  • Agent payment standard support (AP2/ACP/x402/UCP) — Exactly one agent-payment signal (agent-purchase grant stated on /pricing); the 3 readable payment and policy pages name no second standard, manifest or agent-purchase wording.

    The least-implemented surface in the rubric. Accepting an agent payment means choosing a standard and changing a checkout, which is a business decision most sites have not made yet.

    Observation

    paths read: 3/8; standards: none
    id
    payment-protocols
    weight
    3
    points
    0.70
    standard
    Draft — A published specification that is not yet ratified.
    standards
    AP2, ACP, x402, UCP

    Reproduction command and full detail →

  • Agent traffic measurement — No analytics vendor signature among the 8 checked appears in the homepage source, so nothing about the agent channel can be attributed.

    If agent traffic is not measured separately, the channel's return is invisible and never funded.

    Observation

    homepage 704020 bytes; vendors: none; markers: events.carousel.agentic, agentic commerce, and more.","m…
    id
    agent-analytics
    weight
    1
    points
    0.50
    standard
    Draft — A published specification that is not yet ratified.

    Reproduction command and full detail →

Missing 30

  • sitemap.xml valid and current — sitemap.xml answered HTTP 404 with 370299 bytes.

    The primary URL discovery source for agent crawlers.

    Observation

    HTTP 404 · text/html; charset=utf-8 · 370299 bytes · 347 ms
    id
    sitemap-xml
    weight
    2
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-01-15</lastmod>
  </url>
  <url>
    <loc>https://example.com/docs/quickstart</loc>
    <lastmod>2026-01-15</lastmod>
  </url>
</urlset>

    Reproduction command and full detail →

  • Discovery via Link response headers — No Link header on the homepage response (HTTP 200, 704020 bytes).

    RFC 8288 Link headers let an agent find your discovery resources without parsing HTML.

    Observation

    HTTP 200 · text/html; charset=utf-8 · 704020 bytes · 413 ms · final https://stripe.com/en-pl
    id
    link-headers
    weight
    2
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 8288

    Fix

    # nginx: advertise discovery resources on the homepage response.
add_header Link '</llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="alternate"; type="application/xml"' always;

# Raw header, one comma-separated field:
Link: </llms.txt>; rel="describedby"; type="text/plain", </sitemap.xml>; rel="alternate"; type="application/xml"

    Reproduction command and full detail →

  • DNS-AID discovery record — 0 SVCB records and 0 TXT records resolve at _index._agents.stripe.com and _agent.stripe.com.

    Lets agents read discovery information over DNS without an HTTP round trip. Cloudflare added it to its readiness checklist.

    Observation

    DNS-AID names queried for SVCB and TXT records: _index._agents.stripe.com and _agent.stripe.com
    id
    dns-aid
    weight
    2
    points
    0.00
    standard
    Experimental — An early convention that may still change shape.

    Fix

    ; DNS-AID (draft-mozleywilliams-dnsop-dnsaid)
_index._agents.example.com. 3600 IN SVCB 1 agent-index.example.com (
    alpn="h2"
    port=443
    well-known=agent-card.json
)

assistant.example.com. 3600 IN SVCB 1 . (
    alpn="mcp,h2"
    port=443
    well-known=agent-card.json
    cap=https://example.com/.well-known/agent-card.json
)

    Reproduction command and full detail →

  • /llms-full.txt expanded context — Not published (HTTP 404) and not linked from /llms.txt.

    Lets an agent take in the full context in a single request instead of walking the site step by step.

    Observation

    HTTP 404 · text/html; charset=utf-8 · 370299 bytes · 343 ms
    id
    llms-full
    weight
    1
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    # In /llms.txt, under Docs:
- [Full context](https://example.com/llms-full.txt): Every key page as one document

# /llms-full.txt
# Example Inc - full context

> Complete text of the pages an agent needs, in a single request. Regenerated on deploy.

## https://example.com/ (Home)

Example Inc runs a payments API for marketplaces. Production traffic is served from three regions.

## https://example.com/pricing (Pricing)

Starter is $0 for 1,000 calls per month. Growth is $99 for 100,000 calls.

    Reproduction command and full detail →

  • AGENTS.md with the required sections — Not found (HTTP 404, 370299 bytes).

    The instruction file for coding and operations agents. It fails more often than any other check in the curated corpus we measured, and the usual reason is not a missing file but a file without the sections an agent needs.

    Observation

    HTTP 404 · text/html; charset=utf-8 · 370299 bytes · 219 ms
    id
    agents-md
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    # AGENTS.md

## Project overview
Example Inc is a payments API for marketplaces. Docs: https://example.com/docs

## Setup and build
- `pnpm install`
- `pnpm dev` -> http://localhost:3000
- `pnpm build`

## Testing
- `pnpm test`; lint and types: `pnpm lint && pnpm typecheck`

## Conventions
- TypeScript strict mode; no `any` in exported signatures.
- Public API routes live in `src/routes/api/`.

## Security and contact
- Never commit secrets; use `.env.local`.
- Report vulnerabilities to security@example.com.

    Reproduction command and full detail →

  • /sitemap.md markdown site map — Not found (HTTP 404, 370299 bytes).

    Lets an agent read your site structure as markdown in a single file. Adoption is still very low, so this is an early-mover advantage.

    Observation

    HTTP 404 · text/html; charset=utf-8 · 370299 bytes · 207 ms
    id
    sitemap-md
    weight
    1
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    # Sitemap

- [Home](https://example.com/): What Example Inc does and who it is for
- [Quickstart](https://example.com/docs/quickstart): First API call in five minutes
- [API reference](https://example.com/docs/api): Every endpoint and response field
- [Pricing](https://example.com/pricing): Plans, limits and overage rates
- [Status](https://example.com/status): Live service status and incident history
- [Contact](https://example.com/contact): Sales and support routes

    Reproduction command and full detail →

  • Markdown content negotiation — The homepage answered Accept: text/markdown with Content-Type text/html; charset=utf-8 (HTTP 200), so the HTML document is served to every client.

    Agents can request a markup-free version with "Accept: text/markdown", which cuts token cost.

    Observation

    status: 200; content-type: text/html; charset=utf-8; vary: accept-encoding; markdown body: no
    id
    markdown-negotiation
    weight
    3
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 9110

    Fix

    // server.js - one URL, two representations (RFC 9110).
import express from 'express';
import { readFile } from 'node:fs/promises';

const app = express();
app.use(async (req, res, next) => {
  if (req.method !== 'GET') return next();
  res.vary('Accept'); // the HTML response must carry this too
  if (req.accepts(['text/html', 'text/markdown']) !== 'text/markdown') return next();
  try {
    const file = `public${req.path.replace(/\/$/, '/index')}.md`;
    res.type('text/markdown').send(await readFile(file, 'utf8'));
  } catch {
    next(); // no markdown twin for this path: fall back to HTML
  }
});
app.use(express.static('public'));
app.listen(3000);

    Reproduction command and full detail →

  • FAQ / question-answer schema — No FAQPage entity among 1 parsed JSON-LD block on the homepage.

    Question-and-answer content is the type agents quote most.

    Observation

    @types: WebSite, Organization, Person, ImageObject, ContactPoint, Place, PostalAddress
    id
    faq-schema
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    schema.org/FAQPage

    Fix

    <script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What does an agent readiness audit measure?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Fifty-two checks across discovery, content, bot access, protocol and commerce, each scored and paired with a fix."
      }
    }
  ]
}
</script>

    Reproduction command and full detail →

  • Breadcrumb / navigation schema — No BreadcrumbList entity among 1 parsed JSON-LD block on the homepage.

    Helps an agent make sense of where a page sits in your site.

    Observation

    @types: WebSite, Organization, Person, ImageObject, ContactPoint, Place, PostalAddress
    id
    breadcrumb
    weight
    1
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    schema.org/BreadcrumbList

    Fix

    <script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.example.com/" },
    { "@type": "ListItem", "position": 2, "name": "Checks", "item": "https://www.example.com/checks" },
    { "@type": "ListItem", "position": 3, "name": "Structured data", "item": "https://www.example.com/checks/jsonld" }
  ]
}
</script>

    Reproduction command and full detail →

  • Prominent summary block — The first 1000 characters of main content hold no paragraph or summary block (11378 characters of main text).

    The llms.txt contract recommends a short summary at the top of every page; agents quote it directly.

    Observation

    Global GDP running on Stripe: Financial infrastructure to grow your revenue. Accept payments, offer financial services and implement custom revenue models – from your first transaction to your billion
    id
    summary
    weight
    1
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    <main>
  <h1>Token efficiency for agent-readable pages</h1>
  <p class="summary">
    Content-to-markup ratio is the share of a page's bytes an agent can read: below 15% most of the
    HTML is scaffolding, and every wrapper div is billed to someone's context window.
  </p>
  <h2>How the ratio is measured</h2>
  <p>Script, style and template blocks are removed, the remaining tags are stripped, and the visible
  characters are divided by the raw HTML size.</p>
</main>

    Reproduction command and full detail →

  • Token efficiency (content-to-markup ratio) — Content-to-markup ratio 1.8% (12911 visible of 702748 markup characters, ~2554 tokens), below the 8% floor where markup outweighs the content.

    A bloated DOM wastes an agent's context window.

    Observation

    visible characters: 12911; markup characters: 702748; words: 1892; estimated tokens: 2554
    id
    token-efficiency
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    // scripts/tighten-html.mjs - run after the build over every emitted page.
import { readdirSync, readFileSync, writeFileSync } from 'node:fs';
import { minify } from 'html-minifier-terser';

const pages = readdirSync('dist', { recursive: true, encoding: 'utf8' }).filter((p) => p.endsWith('.html'));

for (const page of pages) {
  const file = `dist/${page}`;
  const before = readFileSync(file, 'utf8');
  const after = await minify(before, {
    collapseWhitespace: true,
    removeComments: true,
    removeRedundantAttributes: true,
    minifyCSS: true,
    minifyJS: true,
  });
  writeFileSync(file, after);
}

    Reproduction command and full detail →

  • Web Bot Auth key directory — /.well-known/http-message-signatures-directory answered HTTP 404, not a JWK Set.

    RFC 9421 with Ed25519: the mechanism that lets a site verify which agent is calling rather than guessing from a user-agent string. Adoption in the curated corpus we measured is around one site in a hundred.

    Observation

    <!DOCTYPE html> <html class="MktRoot" lang="en-US" data-js-controller="Page" data-page-id="Not found" data-page-title="Page not found" data-loading > <head> <script>window.__capturedErrors = []; window.onerror = functio…
    id
    webbotauth
    weight
    3
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    RFC 9421

    Reproduction command and full detail →

  • Agent permission model (agent-permissions.json) — Neither path served a permission document (/.well-known/agent-permissions.json HTTP 404, /agent-permissions.json HTTP 404).

    Declares which actions an agent may take, which are refused, and which need a person. It is the difference between a policy and a wish: in the curated corpus we measured, roughly one site in a hundred publishes one.

    id
    agent-permissions
    weight
    3
    points
    0.00
    standard
    Experimental — An early convention that may still change shape.

    Reproduction command and full detail →

  • Content-Signal usage signals — No Content-Signal line in robots.txt (643 bytes) and none in the homepage response headers.

    Declares how your content may be used, inside robots.txt. Cloudflare included this in its readiness checks.

    Observation

    HTTP 200 · text/plain; charset=utf-8 · 643 bytes · 297 ms
    id
    content-signal
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    contentsignals.org

    Fix

    # https://example.com/robots.txt - Content Signals Policy (contentsignals.org)
# search   = index the content and return links and short excerpts
# ai-input = use the content in a model at answer time (grounding)
# ai-train = use the content to train or fine-tune a model

User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

User-agent: GPTBot
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /

    Reproduction command and full detail →

  • AI usage policy page — No AI policy page found: 0 of 7 candidate paths served a policy page and the home page links to none.

    States the rules agents must follow and reduces licensing ambiguity.

    id
    ai-policy
    weight
    2
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <!doctype html>
<html lang="en">
<head><meta charset="utf-8"><title>AI usage policy</title></head>
<body>
  <h1>AI usage policy</h1>
  <h2>Permitted</h2>
  <p>Indexing, retrieval and citation by identified search and answer engines.</p>
  <h2>Not permitted</h2>
  <p>Do not train, fine-tune or distil a model on this content; no bulk scraping or resale.</p>
  <h2>Contact</h2>
  <p><a href="mailto:agents@example.com">agents@example.com</a></p>
</body>
</html>

    Reproduction command and full detail →

  • Crawler and agent policy page — No bot or agent policy page found: 0 of 7 candidate paths served one and the home page links to none.

    Explains which agents are permitted and how they are verified.

    id
    bot-page
    weight
    1
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <!doctype html>
<html lang="en">
<head><meta charset="utf-8"><title>Bot policy</title></head>
<body>
<h1>Bot and agent policy</h1>
<h2>Welcome</h2>
<p>Identified search and answer engines that cite the source.</p>
<h2>Refused</h2>
<p>Training crawlers, spoofed User-Agents, clients that ignore robots.txt.</p>
<h2>How we verify identity</h2>
<p>Signed requests are checked against our key directory at /.well-known/http-message-signatures-directory; unsigned clients by published IP ranges.</p>
<h2>Contact</h2>
<p><a href="mailto:agents@example.com">agents@example.com</a></p>
</body>
</html>

    Reproduction command and full detail →

  • /ai.txt access declaration — /ai.txt answered HTTP 404, not an access declaration.

    Some agent ecosystems read an /ai.txt contract alongside robots.txt.

    Observation

    <!DOCTYPE html> <html class="MktRoot" lang="en-US" data-js-controller="Page" data-page-id="Not found" data-page-title="Page not found" data-loading > <head> <script>window.__capturedErrors = []; window.onerror = functio…
    id
    ai-txt
    weight
    1
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Reproduction command and full detail →

  • MCP server card — No MCP server card was served as JSON at the 3 declared paths (/.well-known/mcp/server-card.json 404 text/html; /.well-known/mcp.json 404 text/html; /mcp.json 404 text/html).

    Since MCP 2026-07-28, agents discover tool servers through a published declaration.

    id
    mcp-card
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    MCP 2026-07-28

    Fix

    {
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "com.example/weather",
  "version": "1.0.0",
  "description": "Live weather and forecast data for partner agents.",
  "title": "Example Weather",
  "websiteUrl": "https://your-domain.example/developers",
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://your-domain.example/mcp",
      "supportedProtocolVersions": ["2026-07-28"]
    }
  ]
}

    Reproduction command and full detail →

  • OpenAPI definition — No OpenAPI document was found: 5 candidate paths (0 advertised, 5 standard) returned no JSON OpenAPI 3.x document.

    A machine-readable contract so an agent can discover your API and generate correct calls.

    Observation

    tried: /openapi.json 404 | /openapi.yaml 404 | /.well-known/openapi.json 404 | /api/openapi.json 404 | /swagger.json 404
    id
    openapi
    weight
    2
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    OpenAPI 3.x

    Fix

    {
  "openapi": "3.1.0",
  "info": { "title": "Example Public API", "version": "1.4.0" },
  "servers": [{ "url": "https://api.your-domain.example/v1" }],
  "paths": {
    "/orders/{orderId}": {
      "get": {
        "operationId": "getOrder",
        "summary": "Get the status of one order",
        "parameters": [{ "name": "orderId", "in": "path", "required": true, "schema": { "type": "string" } }],
        "responses": { "200": { "description": "The order" } }
      }
    }
  }
}

    Reproduction command and full detail →

  • OAuth discovery documents — None of the 3 OAuth discovery paths returned a JSON document (/.well-known/oauth-authorization-server 404 text/html; /.well-known/openid-configuration 404 text/html; /.well-known/oauth-protected-resource 404 text/html).

    Required for agents to connect to your authenticated API on their own (RFC 8414 / RFC 9728).

    id
    oauth-discovery
    weight
    2
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 8414, RFC 9728

    Fix

    {
  "resource": "https://api.your-domain.example/",
  "resource_name": "Example API",
  "resource_logo_uri": "https://your-domain.example/logo.png",
  "authorization_servers": ["https://auth.your-domain.example/"],
  "scopes_supported": ["api.read", "api.write"],
  "bearer_methods_supported": ["header"]
}

    Reproduction command and full detail →

  • API catalog — No API catalog linkset was served at the 3 declared paths (/.well-known/api-catalog 404 text/html; /api-catalog.json 404 text/html; /.well-known/ai-plugin.json 404 text/html).

    Lets an agent see which capabilities are callable in a single document (RFC 9727).

    id
    api-catalog
    weight
    2
    points
    0.00
    standard
    Experimental — An early convention that may still change shape.
    standards
    RFC 9727

    Fix

    {
  "linkset": [
    {
      "anchor": "https://your-domain.example/apis/public_api",
      "service-desc": [
        { "href": "https://your-domain.example/openapi.json", "type": "application/json" }
      ],
      "service-doc": [
        { "href": "https://your-domain.example/docs/", "type": "text/html" }
      ],
      "status": [
        { "href": "https://your-domain.example/status.json", "type": "application/json" }
      ]
    }
  ]
}

    Reproduction command and full detail →

  • Agent Skills declaration — No agent skills index with a non-empty skills array was served as JSON at the 3 declared paths (/.well-known/agent-skills/index.json 404 text/html; /.well-known/agent-skills.json 404 text/html; /.well-known/skills.json 404 text/html).

    Offers ready-made capability packages to agent runtimes.

    id
    agent-skills
    weight
    1
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    {
  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
  "skills": [
    {
      "name": "invoice-reconciliation",
      "type": "skill-md",
      "description": "Reconcile invoices against payments and flag unmatched line items.",
      "url": "/.well-known/agent-skills/invoice-reconciliation/SKILL.md",
      "digest": "sha256:9f2c1a4b7d8e0f3a5c6b1d2e4f7089a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6"
    }
  ]
}

    Reproduction command and full detail →

  • A2A agent card — No A2A agent card was served as JSON at the 2 declared paths (/.well-known/agent-card.json 404 text/html; /.well-known/agent.json 404 text/html).

    A2A v1.0 (Linux Foundation) is the emerging standard for agent-to-agent discovery. Almost no site publishes a card yet, which makes this one of the cheapest places to be early.

    id
    a2a-card
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    A2A v1.0

    Fix

    {
  "name": "Example Support Agent",
  "description": "Answers product and billing questions for partner agents.",
  "version": "1.0.0",
  "supportedInterfaces": [
    { "url": "https://your-domain.example/a2a/v1", "protocolBinding": "JSONRPC", "protocolVersion": "1.0" }
  ],
  "capabilities": { "streaming": true },
  "defaultInputModes": ["text/plain"],
  "defaultOutputModes": ["text/plain"],
  "skills": [
    {
      "id": "billing-question",
      "name": "Billing question",
      "description": "Answers invoice questions for one account.",
      "tags": ["billing"]
    }
  ]
}

    Reproduction command and full detail →

  • /auth.md agent authentication guide — No markdown authentication guide was served at the 2 declared paths (/auth.md 404 text/html; /.well-known/auth.md 404 text/html).

    A guide telling an agent which authentication flow to use.

    id
    auth-md
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    # auth.md

Agents authenticate here: discover, register, claim if needed, call.

## Methods
- `identity_assertion`: you hold an ID-JAG bound to this `resource`.
- `service_auth`: you have the user's verified email; a claim follows.
- `anonymous`: no user identity yet.

## Endpoints
GET https://api.your-domain.example/.well-known/oauth-protected-resource
POST `agent_auth.identity_endpoint`, then `agent_auth.claim_endpoint` when claim is
required; exchange at `token_endpoint` for an access_token.

    Reproduction command and full detail →

  • WebMCP browser tool declaration — No WebMCP declaration was found: the 3 manifest paths served no tools array and the homepage contains 0 registerTool calls.

    WebMCP lets sites expose tools to in-browser agents. It is the only normative deliverable of the W3C Agentic Web WG.

    id
    webmcp
    weight
    2
    points
    0.00
    standard
    Experimental — An early convention that may still change shape.
    standards
    W3C WebMCP

    Fix

    {
  "tools": [
    {
      "name": "search_products",
      "title": "Search products",
      "description": "Search the public catalogue by free-text query and return matching products with prices.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": { "type": "string", "description": "Free-text search query" },
          "limit": { "type": "integer", "minimum": 1, "maximum": 50, "default": 10 }
        },
        "required": ["query"],
        "additionalProperties": false
      }
    }
  ]
}

    Reproduction command and full detail →

  • ARD resource discovery manifest — No ARD manifest with an entries array was served at the 4 declared paths (/.well-known/ard.json 404 text/html; /.well-known/agent-resources.json 404 text/html; /.well-known/ai-catalog.json 404 text/html; /ard.json 404 text/html; first JSON document: none).

    Cisco/Outshift's Agentic Resource Discovery specification; Lighthouse audits it too.

    id
    ard-manifest
    weight
    1
    points
    0.00
    standard
    Experimental — An early convention that may still change shape.
    standards
    ard-spec

    Fix

    {
  "entries": [
    {
      "identifier": "urn:air:your-domain.example:server:support",
      "displayName": "Example Support MCP Server",
      "type": "application/mcp-server-card+json",
      "url": "https://your-domain.example/.well-known/mcp/server-card.json",
      "description": "Tools for order status and returns."
    }
  ]
}

    Reproduction command and full detail →

  • Product/catalog schema — No Product, Offer or AggregateOffer type appears in the homepage JSON-LD (7 types) or in the JSON-LD of the 1 readable product or collection page.

    Product data is the most valuable and the least machine-readable: price, availability and returns are usually rendered for a person to read and never declared for a machine to parse.

    Observation

    homepage @type: WebSite, Organization, Person, ImageObject, ContactPoint, Place, PostalAddress; product paths: /products HTTP 200, /shop HTTP 404, /store HTTP 404
    id
    product-schema
    weight
    3
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/Product

    Fix

    {
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Aurora Desk Lamp",
  "sku": "ADL-100-BLK",
  "offers": {
    "@type": "Offer",
    "price": "1299.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}

    Reproduction command and full detail →

  • Agent purchase policy — No page among the 5 agent policy paths carries both an agent word and a purchase word (/ai-policy HTTP 404, /agent-policy HTTP 404, /terms HTTP 200, /agentic-commerce HTTP 404, /ai HTTP 404).

    Liability is the open question in agent commerce, and it is a policy decision rather than a technical one: a site that accepts an agent purchase has to decide who carries the cost when the agent is wrong, and publish that decision where an agent can read it.

    Observation

    readable pages: /terms
    id
    agent-purchase
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Reproduction command and full detail →

  • UCP manifest (/.well-known/ucp) — Neither /.well-known/ucp nor /.well-known/ucp.json returned HTTP 200 (/.well-known/ucp HTTP 404, /.well-known/ucp.json HTTP 404), so no manifest was served.

    Google and Shopify's Universal Commerce Protocol; lets a merchant declare checkout capabilities at transaction time.

    id
    ucp-manifest
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.

    Fix

    {
  "protocol_version": "1.0",
  "merchant": { "id": "shop.example.com", "name": "Example Shop", "url": "https://shop.example.com" },
  "capabilities": { "catalog_search": true, "product_detail": true, "cart": true, "checkout": true },
  "checkout": {
    "endpoint": "https://shop.example.com/api/ucp/checkout",
    "payment_handlers": ["ap2", "acp", "x402"]
  }
}

    Reproduction command and full detail →

  • Return and shipping terms machine-readable — No return or shipping page responded (/returns HTTP 404, /shipping HTTP 404, /refund-policy HTTP 404) and the homepage JSON-LD declares neither MerchantReturnPolicy nor OfferShippingDetails.

    An agent must verify return terms before making a purchase decision.

    Observation

    homepage @type: WebSite, Organization
    id
    returns
    weight
    1
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/MerchantReturnPolicy

    Fix

    {
  "@context": "https://schema.org",
  "@type": "Offer",
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": "US",
    "merchantReturnDays": 14,
    "returnMethod": "https://schema.org/ReturnByMail",
    "returnFees": "https://schema.org/FreeReturn"
  },
  "shippingDetails": {
    "@type": "OfferShippingDetails",
    "shippingRate": { "@type": "MonetaryAmount", "value": "49.00", "currency": "USD" }
  }
}

    Reproduction command and full detail →

Not measured 1

The scanner could not observe these checks. Under rubric v0.7, each one stays in the denominator at 0 points, the same as a missing check.

  • Cryptographically signed agent card — No A2A agent card is published, so there are no signatures to inspect and the check is not scored.

    A2A v1.0 makes identity verifiable through JWS (RFC 7515).

    id
    a2a-signed
    weight
    1
    points
    not counted
    standard
    Draft — A published specification that is not yet ratified.
    standards
    RFC 7515

    Reproduction command and full detail →

Out of scope 9

The scan did not ask this site for these checks. Each applies to a site profile the scan did not confirm here, or needs a commercial signal it did not detect. They left the denominator. They are not failures, and they are not requests. If this report asks you to fix something that does not apply to your site, the error is ours, not yours.

  • Inventory and price freshness — Not scored: this check applies to ecommerce or marketplace sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    An agent that cannot tell whether an item is in stock — or when a price was last valid — will quote a stale offer to a buyer, or refuse to quote at all.

    id
    inventory-freshness
    weight
    2
    points
    not counted
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/Offer

    Reproduction command and full detail →

  • Seller identity declared — Not scored: this check applies to ecommerce or marketplace sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    On a marketplace an offer is meaningless without knowing who is selling and who is the merchant of record, because that is who the agent has a contract with.

    id
    seller-identity
    weight
    2
    points
    not counted
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/Organization

    Reproduction command and full detail →

  • Shipping cost and delivery declared — Not scored: this check applies to ecommerce or marketplace sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    A purchase agent that cannot compute the delivered total cannot complete a checkout, and returns to the merchant without it.

    id
    shipping-costs
    weight
    2
    points
    not counted
    standard
    Adopted — A ratified standard with real deployment.
    standards
    schema.org/OfferShippingDetails

    Reproduction command and full detail →

  • Sandbox or test environment documented — Not scored: this check applies to saas or api sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    An agent cannot safely integrate against a production endpoint; a documented sandbox is the difference between a working trial and a support ticket.

    id
    sandbox-environment
    weight
    2
    points
    not counted
    standard
    Experimental — An early convention that may still change shape.

    Reproduction command and full detail →

  • Rate limits and quotas documented — Not scored: this check applies to api sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    An agent that does not know the quota discovers it by being throttled, halfway through a task it cannot resume.

    id
    rate-limits-declared
    weight
    1
    points
    not counted
    standard
    Experimental — An early convention that may still change shape.
    standards
    RFC 9110

    Reproduction command and full detail →

  • Reuse and licensing terms declared — Not scored: this check applies to publisher or institution sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    Declaring ai-train=no without stating a licensing path leaves both the publisher and the agent without an answer they can act on.

    id
    licensing-terms
    weight
    2
    points
    not counted
    standard
    Draft — A published specification that is not yet ratified.
    standards
    TDM Reservation Protocol

    Reproduction command and full detail →

  • Content provenance declared — Not scored: this check applies to publisher or institution sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    Author, publication date and update date are what let an agent judge whether a source is current and attributable before it quotes it.

    id
    provenance-declared
    weight
    1
    points
    not counted
    standard
    Draft — A published specification that is not yet ratified.
    standards
    schema.org/author, C2PA

    Reproduction command and full detail →

  • Machine-readable booking action — Not scored: this check applies to services sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    For a service business the agent's task is to book, not to browse — a declared action is what turns a contact page into a completed job.

    id
    booking-action
    weight
    2
    points
    not counted
    standard
    Draft — A published specification that is not yet ratified.
    standards
    schema.org/ReserveAction

    Reproduction command and full detail →

  • Documents in machine-readable formats — Not scored: this check applies to institution sites, and the site type could not be confirmed (best candidates: api, saas). Declare the type to have it measured.

    A PDF that carries no document structure is unreadable to an agent and to a screen reader alike — the same defect, found twice.

    id
    document-formats
    weight
    2
    points
    not counted
    standard
    Draft — A published specification that is not yet ratified.
    standards
    PDF/UA

    Reproduction command and full detail →

Request transcript 138 requests

Every fetch this scan record logged, in order. A fetch that followed redirects shows how many redirect requests it made.

  1. 200 / +1 redirect text/html 687.5 KB 413ms
  2. 200 /robots.txt text/plain 643 B 297ms
  3. 404 /sitemap.xml text/html 361.6 KB 347ms
  4. 200 /llms.txt text/plain 68.3 KB 341ms
  5. 404 /llms-full.txt text/html 361.6 KB 343ms
  6. 404 /AGENTS.md text/html 361.6 KB 219ms
  7. 404 /sitemap.md text/html 361.6 KB 207ms
  8. 404 /ai.txt text/html 361.6 KB 199ms
  9. 404 /ai-policy text/html 361.6 KB 211ms
  10. 404 /ai-usage text/html 361.6 KB 210ms
  11. 404 /ai +1 redirect text/html 363.5 KB 661ms
  12. 404 /terms/ai text/html 361.6 KB 222ms
  13. 404 /yapay-zeka-politikasi text/html 361.6 KB 243ms
  14. 404 /auth.md text/html 361.6 KB 240ms
  15. 404 /.well-known/auth.md text/html 361.6 KB 208ms
  16. 404 /.well-known/http-message-signatures-directory text/html 361.6 KB 212ms
  17. 404 /.well-known/agent-permissions.json text/html 361.6 KB 261ms
  18. 404 /agent-permissions.json text/html 361.6 KB 224ms
  19. 404 /.well-known/mcp/server-card.json text/html 361.6 KB 244ms
  20. 404 /.well-known/mcp.json text/html 361.6 KB 217ms
  21. 404 /mcp.json text/html 361.6 KB 247ms
  22. 404 /.well-known/agent-card.json text/html 361.6 KB 247ms
  23. 404 /.well-known/agent.json text/html 361.6 KB 203ms
  24. 404 /.well-known/oauth-authorization-server text/html 361.6 KB 202ms
  25. 404 /.well-known/oauth-protected-resource text/html 361.6 KB 191ms
  26. 404 /.well-known/openid-configuration text/html 361.6 KB 208ms
  27. 404 /.well-known/api-catalog text/html 361.6 KB 211ms
  28. 404 /api-catalog.json text/html 361.6 KB 217ms
  29. 404 /.well-known/ai-plugin.json text/html 361.6 KB 213ms
  30. 404 /.well-known/agent-skills/index.json text/html 361.6 KB 218ms
  31. 404 /.well-known/agent-skills.json text/html 361.6 KB 207ms
  32. 404 /.well-known/skills.json text/html 361.6 KB 212ms
  33. 200 /.well-known/security.txt text/plain 285 B 206ms
  34. 404 /security.txt text/html 361.6 KB 337ms
  35. 404 /.well-known/webmcp.json text/html 361.6 KB 257ms
  36. 404 /.well-known/webmcp text/html 361.6 KB 323ms
  37. 404 /webmcp.json text/html 361.6 KB 255ms
  38. 404 /.well-known/ard.json text/html 361.6 KB 268ms
  39. 404 /.well-known/agent-resources.json text/html 361.6 KB 227ms
  40. 404 /.well-known/ai-catalog.json text/html 361.6 KB 263ms
  41. 404 /ard.json text/html 361.6 KB 834ms
  42. 404 /.well-known/ucp text/html 361.6 KB 251ms
  43. 404 /.well-known/ucp.json text/html 361.6 KB 237ms
  44. 404 /openapi.json text/html 361.6 KB 239ms
  45. 404 /openapi.yaml text/html 361.6 KB 246ms
  46. 404 /.well-known/openapi.json text/html 361.6 KB 243ms
  47. 404 /api/openapi.json text/html 361.6 KB 224ms
  48. 404 /swagger.json text/html 361.6 KB 254ms
  49. 404 /.well-known/ai text/html 361.6 KB 266ms
  50. 200 /api +3 redirects text/html 1355.0 KB 1175ms
  51. 404 /bot text/html 361.6 KB 236ms
  52. 404 /bots text/html 361.6 KB 250ms
  53. 404 /agents text/html 361.6 KB 217ms
  54. 404 /agent text/html 361.6 KB 245ms
  55. 404 /agent-policy text/html 361.6 KB 238ms
  56. 404 /agentic-commerce text/html 361.6 KB 208ms
  57. 200 /terms +2 redirects text/html 143.5 KB 1003ms
  58. 200 /pricing +1 redirect text/html 890.8 KB 323ms
  59. 404 /fiyatlandirma text/html 361.6 KB 255ms
  60. 404 /fiyat text/html 361.6 KB 264ms
  61. 404 /plans text/html 361.6 KB 233ms
  62. 200 /contact +1 redirect text/html 342.2 KB 288ms
  63. 404 /iletisim text/html 361.6 KB 262ms
  64. 404 /contact-us text/html 361.6 KB 217ms
  65. 200 /faq +1 redirect text/html 22.0 KB 1272ms
  66. 404 /sss text/html 361.6 KB 250ms
  67. 404 /sikca-sorulan-sorular text/html 361.6 KB 254ms
  68. 200 /help +1 redirect text/markdown 2.3 KB 1119ms
  69. 404 /yardim text/html 361.6 KB 263ms
  70. 200 /docs +1 redirect text/html 1344.9 KB 1005ms
  71. 404 /documentation text/html 361.6 KB 275ms
  72. 404 /developers text/html 361.6 KB 271ms
  73. 404 /gelistiriciler text/html 361.6 KB 243ms
  74. 200 /status +2 redirects text/html 892 B 575ms
  75. 200 /changelog +1 redirect text/html 1044.9 KB 531ms
  76. 404 /releases text/html 361.6 KB 204ms
  77. 404 /whats-new text/html 361.6 KB 213ms
  78. 404 /returns text/html 361.6 KB 220ms
  79. 404 /shipping text/html 361.6 KB 191ms
  80. 404 /iade text/html 361.6 KB 189ms
  81. 404 /kargo text/html 361.6 KB 192ms
  82. 404 /refund-policy text/html 361.6 KB 190ms
  83. 200 /about +1 redirect text/html 176.5 KB 411ms
  84. 200 /products +1 redirect text/html 679.7 KB 279ms
  85. 404 /shop text/html 361.6 KB 239ms
  86. 404 /store text/html 361.6 KB 227ms
  87. 404 /urunler text/html 361.6 KB 216ms
  88. 404 /magaza text/html 361.6 KB 236ms
  89. 404 /cart text/html 361.6 KB 248ms
  90. 404 /sepet text/html 361.6 KB 224ms
  91. 404 /docs/sandbox +1 redirect text/html 23.3 KB 88ms
  92. 404 /sandbox text/html 361.6 KB 255ms
  93. 404 /developers/sandbox text/html 361.6 KB 234ms
  94. 404 /rate-limits.json text/html 361.6 KB 276ms
  95. 404 /.well-known/rate-limits.json text/html 361.6 KB 247ms
  96. 200 /docs/rate-limits +1 redirect text/html 798.2 KB 800ms
  97. 404 /licensing text/html 361.6 KB 225ms
  98. 404 /.well-known/tdmrep.json text/html 361.6 KB 216ms
  99. 404 /book text/html 361.6 KB 241ms
  100. 404 /appointment text/html 361.6 KB 232ms
  101. 404 /documents text/html 361.6 KB 1180ms
  102. 404 /publications text/html 361.6 KB 277ms
  103. 404 /reports text/html 361.6 KB 247ms
  104. 200 /payments +1 redirect text/html 1190.5 KB 1785ms
  105. 200 /payments/features +1 redirect text/html 708.8 KB 416ms
  106. 200 /payments/payment-methods +1 redirect text/html 2798.4 KB 2849ms
  107. 200 /authorization-boost +1 redirect text/html 824.5 KB 1599ms
  108. 200 /payments/authentication +1 redirect text/html 647.9 KB 1321ms
  109. 200 /payments/ai +1 redirect text/html 649.1 KB 1203ms
  110. 200 /en-pl/guides/best-practices-for-launching-and-scaling-platform-payments text/html 508.5 KB 80ms
  111. 200 /en-pl/guides/introduction-to-monetizing-payments text/html 524.5 KB 241ms
  112. 200 / +1 redirect text/html 687.5 KB 302ms