AgenticWebScore
Scan

rubric v0.7 · scanned

shopify.com

33.4 BB L0 Not Ready 9/51 checks passed

42 checks to fix. Open the fix list

Fix list

The files below list the 42 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
33.4
out of 100

BB thin L0 · Not Ready

Agents cannot read, verify or use this site.

Held at this level by reachable — the requirements for L1 Basic Web Presence are not all met. Levels are cumulative: a high score does not skip one.

9/51 checks passed

Scan record

Target
https://shopify.com
Scanned
Requests
218
Duration
1.5s
Confidence
99% · high
Rubric
rubric v0.7

Fingerprint

5d805e1c45c6… verify this record

full hash

5d805e1c45c6dc2de4e883fa1b0150419771ce5af1e2a23606edd9c8e0b820b5

Page as an agent receives it

Words
1024
Est. tokens
1382
Markup
652.8 KB
Language
en

“Shopify: The All-in-One Commerce Platform for Businesses - Shopify”

Score unchanged since the last scan

Measured 3 hours ago. Previously 33.4/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: marketplace (3) and api (2), margin 1 < 2.
  • · Profile-scoped checks were not scored rather than guessed at.

Signal scores

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

By dimension

Weighted within each tier pool. Commerce checks are in scope: purchase-intent copy ("buy now"); commerce path (/shop).

Scores by dimension
Dimension Score Pass Partial Missing Not scored
Protocol Discovery 25% 12.5 1 3 10 3
Content Accessibility 22% 45.5 5 1 6 3
Discoverability 20% 40.9 2 4 5 0
Bot Access Control 18% 19.3 0 3 5 0
Commerce Protocols 15% 37.1 1 2 3 4

All 61 checks

Passed 9

  • sitemap.xml valid and current — 555 absolute URLs, 555 with <lastmod>.

    The primary URL discovery source for agent crawlers.

    Observation

    HTTP 200 · application/xml · 69899 bytes · 77 ms · final https://www.shopify.com/sitemap.xml · root <urlset>
    id
    sitemap-xml
    weight
    2
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • /llms.txt published and well-structured — H1 "Shopify", blockquote summary, 12 H2 sections with 74 markdown links, 12520 bytes. The scan requested none of its links. Not requested: 74 links on another origin.

    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 · 12520 bytes · 77 ms · final https://www.shopify.com/llms.txt · headings: Shopify | Start a Business | Build with AI | Sell Online | Payments and Money | Manage your Store | Grow your Business …
    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 →

  • Semantic heading structure — 1 H1 with 6 H2s and 14 H3s, and no level in the outline is skipped.

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

    Observation

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

    Reproduction command and full detail →

  • JSON-LD structured data — 1 JSON-LD block parsed with a schema.org @context declaring Corporation (2 @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: Corporation, ContactPoint
    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" with 85 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"; alternates: x-default -> https://www.shopify.com, en-us -> https://www.shopify.com, es-ar -> https://www.shopify.com/ar, en-au -> https://www.shopify.com/au, de-at -> https://www.shopify.com/at, bn-bd -> https://www.shopify.com/bd, ru -> https://www.shopify.com/by, nl-be -> https://www.shopify.com/be, de-be -> https://www.shopify.com/be-de, fr-be -> https://www…
    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 — 7103 characters of static text and 1 H1 is 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: 7103; H1 in static HTML: 1; characters inside noscript: 13; markup characters: 667899
    id
    no-js-fallback
    weight
    2
    points
    1.00
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

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

    Agent browsers mostly run at mobile scale.

    Observation

    viewport meta: width=device-width,initial-scale=1; 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 →

  • Documentation reachable — Documentation is reachable at /blog/topics/guides (homepage anchor) and returns HTTP 200 text/html with 1060 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 →

  • Agent payment standard support (AP2/ACP/x402/UCP) — 2 distinct agent-payment signals: UCP named on /developers; agent-purchase grant stated on /developers.

    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: UCP
    id
    payment-protocols
    weight
    3
    points
    1.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    AP2, ACP, x402, UCP

    Reproduction command and full detail →

Partial 13

  • Homepage open to agent access — Homepage redirected off shopify.com to www.shopify.com (HTTP 200, 668424 bytes).

    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 · 668424 bytes · 74 ms · final https://www.shopify.com/
    id
    reachable
    weight
    3
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.

    Reproduction command and full detail →

  • DNS-AID discovery record — Only the TXT fallback form is published (3 records, 4 key=value pairs).

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

    Observation

    v=BIMI1; l=; a=;
    id
    dns-aid
    weight
    2
    points
    0.50
    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 →

  • Canonical and hreflang discipline — Canonical points at www.shopify.com, not the scanned host shopify.com.

    An agent needs one consistent URL per important page.

    Observation

    https://www.shopify.com/
    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 →

  • /llms-full.txt expanded context — 2089 words of text and 107 link lines in 18863 bytes, which is a list of links rather than expanded page content.

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

    Observation

    HTTP 200 · text/plain; charset=utf-8 · 18863 bytes · 77 ms · final https://www.shopify.com/llms-full.txt · # Shopify > [Shopify](https://www.shopify.com/about) is the leading commerce platform for starting, running, and growin…
    id
    llms-full
    weight
    1
    points
    0.50
    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 →

  • Title and summary metadata — Both carriers are present but outside the band: title 66 characters (band 50-60).

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

    Observation

    title(66): Shopify: The All-in-One Commerce Platform for Businesses - Shopify | description(142): Try Shopify free. Build or grow your business fast with AI. Get more than ecommerce software with tools to manage every part of your business.
    id
    meta
    weight
    2
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.

    Fix

    <head>
  <meta charset="utf-8" />
  <title>Agent readiness audit for e-commerce teams | Acme Inc</title>
  <meta
    name="description"
    content="Acme audits how well your store serves AI agents: 52 checks across discovery, content, bot access and commerce, each paired with a paste-ready fix."
  />
</head>

    Reproduction command and full detail →

  • Web Bot Auth key directory — The document parsed as JSON but holds 0 keys and 0 usable Ed25519 verification keys (no top-level keys array).

    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

    { "crv": "Ed25519", "kty": "OKP", "x": "Mt6otbtH_mqWe1Qsm0cW9GVfknDvrGXXMpyXhiW0Dr4", "use": "sig", "alg": "EdDSA", "kid": "SjjyXvQ2cGhsRXs9DXEaV6ClyCun0Pj5yxjV67dLGOk", "nbf": 1773401952, "exp": 1804937952 }
    id
    webbotauth
    weight
    3
    points
    0.50
    standard
    Draft — A published specification that is not yet ratified.
    standards
    RFC 9421

    Fix

    {
  "keys": [
    {
      "kty": "OKP",
      "crv": "Ed25519",
      "x": "K6zqFKAe5fHfdzecJiq7nnGe0teq-_bhC1eP_fGo5bc",
      "kid": "2026-10-primary",
      "use": "sig",
      "alg": "Ed25519"
    }
  ]
}

    Reproduction command and full detail →

  • AI usage policy page — AI policy at /ai covers 1 of 3 expected topics (permitted uses stated; prohibited uses and a contact route missing) and is not linked from the home page.

    States the rules agents must follow and reduces licensing ambiguity.

    Observation

    ai-enabled commerce assistant, sidekick, designed to make it easier for you to start, run, and grow your business on shopify. - shopify skip to content why shopify back get started fast you could be selling by tomorrow. switch to shopify get more customers. m…
    id
    ai-policy
    weight
    2
    points
    0.35
    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 →

  • security.txt (RFC 9116) — security.txt at /.well-known/security.txt holds 1 of 2 required fields (Expires is missing). 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://www.shopify.com/security-response Contact: mailto:security@shopify.com Encryption: https://www.shopify.com/shopify-security.pub Policy: https://hackerone.com/shopify Acknowledgments: https://hackerone.com/shopify/thanks Hiring: https://www.sh…
    id
    security-txt
    weight
    1
    points
    0.50
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 9116

    Fix

    # security.txt - RFC 9116
Contact: mailto:security@example.com
Expires: 2027-09-30T18:37:07Z
Canonical: https://example.com/.well-known/security.txt
Preferred-Languages: en
Policy: https://example.com/security-policy

    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 "$125.00".

    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 →

  • 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 — The homepage advertises 1 status or feed reference, but the status document at https://shopifystatus.com was not fetched by this scan, so its response was not observed.

    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 →

  • Return and shipping terms machine-readable — /shipping responded but none of the 4 documents read declares MerchantReturnPolicy or OfferShippingDetails.

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

    Observation

    readable return pages: /shipping 437912 bytes
    id
    returns
    weight
    1
    points
    0.65
    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 →

  • Agent traffic measurement — The homepage names 1 analytics vendor (googletagmanager) but none of the 5 agent segmentation markers appears, so agent traffic is not separated.

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

    Observation

    homepage 668424 bytes; vendors: googletagmanager; markers: none
    id
    agent-analytics
    weight
    1
    points
    0.80
    standard
    Draft — A published specification that is not yet ratified.

    Reproduction command and full detail →

Missing 29

  • robots.txt with agent directives — robots.txt answered HTTP 429 with 9358 bytes.

    The front door for agent traffic (RFC 9309).

    Observation

    HTTP 429 · text/html; charset=utf-8 · 9358 bytes · 29 ms
    id
    robots-txt
    weight
    2
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.
    standards
    RFC 9309

    Fix

    # https://example.com/robots.txt  (RFC 9309)
User-agent: *
Allow: /
Disallow: /admin/

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

Sitemap: https://example.com/sitemap.xml

    Reproduction command and full detail →

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

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

    Observation

    HTTP 200 · text/html; charset=utf-8 · 668424 bytes · 74 ms · final https://www.shopify.com/
    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 →

  • AGENTS.md with the required sections — Not found (HTTP 404, 11026 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 · 11026 bytes · 48 ms · final https://www.shopify.com/AGENTS.md
    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, 11029 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 · 11029 bytes · 59 ms · final https://www.shopify.com/sitemap.md
    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: (none); 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: Corporation, ContactPoint
    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: Corporation, ContactPoint
    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 (3408 characters of main text).

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

    Observation

    Be the next AI all-star Be the next store they line up for AI all-star household name solo-preneur category creator global empire store they line up for big thing Dream big and build fast on Shopify.
    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 →

  • Per-page content separation (no SPA fallback) — Shell duplicate: /book, /reports match the homepage title "Shopify: The All-in-One Commerce Platform for Businesses - …" with 100% identical markup (2 of 15 probed pages).

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

    Observation

    /about: title "About Shopify", skeleton 39%; /pricing: title "Shopify Pricing: Find the Right Plan fo…", skeleton 41%; /contact: title "Contact Us — Shopify", skeleton 39%; /terms: title "Shopify Terms of Service - Shopify", skeleton 40%; /faq: title "Shopify FAQ - Shopify", skeleton 37%; /help: title "Shopify Help Center", skeleton 1%; /products: title "Browse all of Shopify’…
    id
    spa-fallback
    weight
    2
    points
    0.00
    standard
    Experimental — An early convention that may still change shape.

    Fix

    // Serve dist/<route>/index.html per URL; never rewrite every path to one shell.
import express from 'express';
import { existsSync } from 'node:fs';

const app = express();
app.use((req, res) => {
  if (req.method !== 'GET') return res.status(405).end();
  const file = new URL(`dist${req.path.replace(/\/$/, '/index')}.html`, import.meta.url).pathname;
  if (existsSync(file)) return res.sendFile(file);
  res.status(404).type('html')
    .send('<!doctype html><html lang="en"><title>404</title><h1>Not found</h1></html>');
});
app.listen(3000);

    Reproduction command and full detail →

  • Token efficiency (content-to-markup ratio) — Content-to-markup ratio 1.0% (7103 visible of 667899 markup characters, ~1382 tokens), below the 8% floor where markup outweighs the content.

    A bloated DOM wastes an agent's context window.

    Observation

    visible characters: 7103; markup characters: 667899; words: 1024; estimated tokens: 1382
    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 →

  • 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 →

  • Named AI bot rules in robots.txt — /robots.txt answered HTTP 429, so 0 of 18 named AI bots are addressed.

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

    id
    ai-rules
    weight
    2
    points
    0.00
    standard
    Draft — A published specification that is not yet ratified.
    standards
    RFC 9309

    Reproduction command and full detail →

  • Content-Signal usage signals — robots.txt answered HTTP 429 and the homepage response carries no Content-Signal header.

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

    Observation

    HTTP 429 · text/html; charset=utf-8 · 9358 bytes · 29 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 →

  • Crawler and agent policy page — No bot or agent policy page found: 0 of 8 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 →

  • Crawl rate declaration — /robots.txt answered HTTP 429, so no crawl rate is declared.

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

    id
    crawl-delay
    weight
    1
    points
    0.00
    standard
    Adopted — A ratified standard with real deployment.

    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

    <html class="bg-black h-full" lang="en" dir="ltr"><head><title>404: Page not found</title><meta charSet="utf-8"/><meta name="viewport" content="width=device-width,initial-scale=1"/><meta name="robots" content="noindex, …
    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/plain; /.well-known/mcp.json 404 text/plain; /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/plain; /.well-known/openid-configuration 404 text/plain; /.well-known/oauth-protected-resource 404 text/plain).

    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/plain; /api-catalog.json 404 text/html; /.well-known/ai-plugin.json 404 text/plain).

    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/plain; /.well-known/agent-skills.json 404 text/plain; /.well-known/skills.json 404 text/plain).

    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/plain; /.well-known/agent.json 404 text/plain).

    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/plain).

    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/plain; /.well-known/agent-resources.json 404 text/plain; /.well-known/ai-catalog.json 404 text/plain; /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 →

  • Service/product scope machine-readable — The homepage JSON-LD carries 1 model types with 0 Service or Product nodes, so the offer scope cannot be read.

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

    id
    service-schema
    weight
    2
    points
    0.00
    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 →

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

    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: Corporation, ContactPoint; product paths: /products HTTP 200, /shop HTTP 200, /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 200).

    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, /ai
    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 →

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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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: marketplace, api). 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 218 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 652.8 KB 74ms
  2. 429 /robots.txt text/html 9.1 KB 29ms
  3. 200 /sitemap.xml +1 redirect application/xml 68.3 KB 77ms
  4. 200 /llms.txt +1 redirect text/plain 12.2 KB 77ms
  5. 200 /llms-full.txt +1 redirect text/plain 18.4 KB 77ms
  6. 404 /AGENTS.md +1 redirect text/html 10.8 KB 48ms
  7. 404 /sitemap.md +1 redirect text/html 10.8 KB 59ms
  8. 404 /ai.txt +1 redirect text/html 10.8 KB 57ms
  9. 404 /ai-policy +1 redirect text/html 10.8 KB 57ms
  10. 404 /ai-usage +1 redirect text/html 10.8 KB 56ms
  11. 200 /ai +2 redirects text/html 496.8 KB 111ms
  12. 404 /terms/ai +1 redirect text/html 10.8 KB 54ms
  13. 404 /yapay-zeka-politikasi +1 redirect text/html 10.8 KB 59ms
  14. 404 /auth.md +1 redirect text/html 10.8 KB 58ms
  15. 404 /.well-known/auth.md +1 redirect text/plain 9 B 52ms
  16. 200 /.well-known/http-message-signatures-directory +1 redirect application/http-message-signatures-directory+json 224 B 16ms
  17. 404 /.well-known/agent-permissions.json +1 redirect text/plain 9 B 19ms
  18. 404 /agent-permissions.json +1 redirect text/html 10.8 KB 23ms
  19. 404 /.well-known/mcp/server-card.json +1 redirect text/plain 9 B 18ms
  20. 404 /.well-known/mcp.json +1 redirect text/plain 9 B 17ms
  21. 404 /mcp.json +1 redirect text/html 10.8 KB 24ms
  22. 404 /.well-known/agent-card.json +1 redirect text/plain 9 B 19ms
  23. 404 /.well-known/agent.json +1 redirect text/plain 9 B 20ms
  24. 404 /.well-known/oauth-authorization-server +1 redirect text/plain 9 B 18ms
  25. 404 /.well-known/oauth-protected-resource +1 redirect text/plain 9 B 24ms
  26. 404 /.well-known/openid-configuration +1 redirect text/plain 9 B 18ms
  27. 404 /.well-known/api-catalog +1 redirect text/plain 9 B 19ms
  28. 404 /api-catalog.json +1 redirect text/html 10.8 KB 22ms
  29. 404 /.well-known/ai-plugin.json +1 redirect text/plain 9 B 19ms
  30. 404 /.well-known/agent-skills/index.json +1 redirect text/plain 9 B 17ms
  31. 404 /.well-known/agent-skills.json +1 redirect text/plain 9 B 17ms
  32. 404 /.well-known/skills.json +1 redirect text/plain 9 B 16ms
  33. 200 /.well-known/security.txt +1 redirect text/plain 277 B 28ms
  34. 404 /security.txt +1 redirect text/html 10.8 KB 28ms
  35. 404 /.well-known/webmcp.json +1 redirect text/plain 9 B 25ms
  36. 404 /.well-known/webmcp +1 redirect text/plain 9 B 23ms
  37. 404 /webmcp.json +1 redirect text/html 10.8 KB 24ms
  38. 404 /.well-known/ard.json +1 redirect text/plain 9 B 12ms
  39. 404 /.well-known/agent-resources.json +1 redirect text/plain 9 B 19ms
  40. 404 /.well-known/ai-catalog.json +1 redirect text/plain 9 B 16ms
  41. 404 /ard.json +1 redirect text/html 10.8 KB 24ms
  42. 404 /.well-known/ucp +1 redirect text/plain 9 B 15ms
  43. 404 /.well-known/ucp.json +1 redirect text/plain 9 B 15ms
  44. 404 /openapi.json +1 redirect text/html 10.8 KB 24ms
  45. 404 /openapi.yaml +1 redirect text/html 10.8 KB 26ms
  46. 404 /.well-known/openapi.json +1 redirect text/plain 9 B 20ms
  47. 404 /api/openapi.json +1 redirect text/html 10.8 KB 27ms
  48. 404 /swagger.json +1 redirect text/html 10.8 KB 25ms
  49. 404 /.well-known/ai +1 redirect text/plain 9 B 16ms
  50. 404 /api +1 redirect text/html 10.8 KB 27ms
  51. 404 /bot +1 redirect text/html 10.8 KB 34ms
  52. 404 /bots +1 redirect text/html 10.8 KB 44ms
  53. 404 /agents +1 redirect text/html 10.8 KB 51ms
  54. 404 /agent +1 redirect text/html 10.8 KB 50ms
  55. 404 /agent-policy +1 redirect text/html 10.8 KB 38ms
  56. 404 /agentic-commerce +1 redirect text/html 10.8 KB 64ms
  57. 200 /terms +2 redirects text/html 646.9 KB 65ms
  58. 200 /pricing +1 redirect text/html 1067.5 KB 44ms
  59. 404 /fiyatlandirma +1 redirect text/html 10.8 KB 40ms
  60. 404 /fiyat +1 redirect text/html 10.8 KB 32ms
  61. 404 /plans +1 redirect text/html 10.8 KB 19ms
  62. 200 /contact +1 redirect text/html 400.1 KB 24ms
  63. 404 /iletisim +1 redirect text/html 10.8 KB 20ms
  64. 404 /contact-us +1 redirect text/html 10.8 KB 22ms
  65. 200 /faq +1 redirect text/html 377.0 KB 13ms
  66. 404 /sss +1 redirect text/html 10.8 KB 33ms
  67. 404 /sikca-sorulan-sorular +1 redirect text/html 10.8 KB 29ms
  68. 200 /help +3 redirects text/html 91.0 KB 992ms
  69. 404 /yardim +1 redirect text/html 10.8 KB 35ms
  70. 404 /docs +1 redirect text/html 10.8 KB 32ms
  71. 404 /documentation +1 redirect text/html 10.8 KB 35ms
  72. 200 /developers +3 redirects text/html 328.9 KB 47ms
  73. 404 /gelistiriciler +1 redirect text/html 10.8 KB 32ms
  74. 404 /status +1 redirect text/html 10.8 KB 36ms
  75. 200 /changelog +2 redirects text/html 322.3 KB 462ms
  76. 404 /releases +1 redirect text/html 10.8 KB 24ms
  77. 404 /whats-new +1 redirect text/html 10.8 KB 25ms
  78. 404 /returns +1 redirect text/html 10.8 KB 30ms
  79. 200 /shipping +1 redirect text/html 427.6 KB 54ms
  80. 404 /iade +1 redirect text/html 10.8 KB 48ms
  81. 404 /kargo +1 redirect text/html 10.8 KB 45ms
  82. 404 /refund-policy +1 redirect text/html 10.8 KB 35ms
  83. 200 /about +1 redirect text/html 411.1 KB 37ms
  84. 200 /products +1 redirect text/html 413.0 KB 32ms
  85. 200 /shop +1 redirect text/html 357.2 KB 30ms
  86. 404 /store +1 redirect text/html 10.8 KB 31ms
  87. 404 /urunler +1 redirect text/html 10.8 KB 28ms
  88. 404 /magaza +1 redirect text/html 10.8 KB 45ms
  89. 404 /cart +1 redirect text/html 10.8 KB 37ms
  90. 404 /sepet +1 redirect text/html 10.8 KB 45ms
  91. 404 /docs/sandbox +1 redirect text/html 10.8 KB 23ms
  92. 404 /sandbox +1 redirect text/html 10.8 KB 29ms
  93. 404 /developers/sandbox +1 redirect text/html 10.8 KB 30ms
  94. 404 /rate-limits.json +1 redirect text/html 10.8 KB 21ms
  95. 404 /.well-known/rate-limits.json +1 redirect text/plain 9 B 15ms
  96. 404 /docs/rate-limits +1 redirect text/html 10.8 KB 22ms
  97. 404 /licensing +1 redirect text/html 10.8 KB 28ms
  98. 404 /.well-known/tdmrep.json +1 redirect text/plain 9 B 21ms
  99. 200 /book +2 redirects text/html 652.8 KB 84ms
  100. 404 /appointment +1 redirect text/html 10.8 KB 41ms
  101. 404 /documents +1 redirect text/html 10.8 KB 40ms
  102. 404 /publications +1 redirect text/html 10.8 KB 35ms
  103. 200 /reports +2 redirects text/html 652.8 KB 59ms
  104. 200 /blog/topics/guides +1 redirect text/html 442.0 KB 34ms
  105. 200 / +1 redirect text/html 652.8 KB 30ms