Agent Ready CheckoutEdition . The pay layer for agents.

360 check, 11 Nov 2026

Dick's Sporting Goods on the pay layer: the 360 agent-readiness check

In short

Dick's Sporting Goods scores 16 of 100 on Ora's agent-readiness scan, an F, read 14 Nov 2026. The six payment checks did not apply to dickssportinggoods.com on this read, which is how Ora treats a site it does not read as a shop. Six agents blocked at the door, and a GraphQL endpoint waiting behind the shield.

On 14 Nov 2026 the public site at dickssportinggoods.com scored 16 of 100 on Ora's agent-readiness scan, an F. Dick's Sporting Goods is the largest sporting goods retailer in the United States, so this check reads the Payments layer first: the six checks that look for x402, MPP, UCP, ACP and AP2 on the domain, the same protocols this site's matrix tracks row by row. The other layers follow, with every check Ora ran and what it saw. Ora's one-line summary: Public API with reachable endpoints, but lacks an OpenAPI specification.

The score

Dick's Sporting Goods on Ora, read 14 Nov 2026: points per layer, with the share of each layer's maximum. 3 checks pass, 3 are partial, 53 fail and 60 do not apply to this site.
LayerPointsShareWhat the layer asks
Discovery3 of 838%Can agents find and recommend it
Access0 of 440%Can agents read it
Usability8 of 4418%Can agents use it
Payments0 of 0none applyCan agents pay
Total16 of 10016%Grade F

The pay layer

Ora did not run the six payment checks against dickssportinggoods.com on this read: it marks them not applicable on a site it does not read as a shop, so the layer has no maximum and costs nothing. A retailer that sells online can still publish any of the five protocols; the matrix says which processors and platforms carry each one. Each protocol links to its matrix row, where the processors and platforms that carry it are dated and sourced.

The six Payments checks Ora runs, on dickssportinggoods.com, read 14 Nov 2026. A protocol not found costs nothing, and a check marked does not apply was not run against the site.
Payment checkResultPointsMatrix rowWhat Ora saw
x402Does not apply0 of 2x402 in the matrixNo commerce signals detected - agent-payment protocols are optional for non-commerce sites
MPPDoes not apply0 of 2MPP in the matrixNo commerce signals detected - agent-payment protocols are optional for non-commerce sites
UCPDoes not apply0 of 3UCP in the matrixNo commerce signals detected - agent-payment protocols are optional for non-commerce sites
ACPDoes not apply0 of 3ACP in the matrixNo commerce signals detected - agent-payment protocols are optional for non-commerce sites
ACP delegate paymentDoes not apply0 of 3ACP in the matrixNo commerce signals detected - agent-payment protocols are optional for non-commerce sites
AP2Does not apply0 of 3AP2 in the matrixNo commerce signals detected - agent-payment protocols are optional for non-commerce sites

The other layers, check by check

Every check Ora ran on dickssportinggoods.com, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.

Discovery: 3 of 8

Discovery checks on dickssportinggoods.com, read 14 Nov 2026; 7 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
ARD discoveryFail0 of 1No /.well-known/ard.json (and no legacy /.well-known/ai-catalog.json)
Developer resource discoverabilityPartial1 of 3Agent struggled to find developer resources by name - only 1 result(s) out of 10. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation
Brand name discoverabilityPartial1 of 3dickssportinggoods.com appears once in brand-name search results for "dickssportinggoods" (position #5 out of 7)
Wikipedia / Wikidata entity presenceFail0 of 4No Wikipedia article or Wikidata entity found for "dickssportinggoods" - creating a Wikipedia page and a Wikidata item with P856 = dickssportinggoods.com is the highest-impact step for AI search citation coverage
NPM/PyPI SDK packagePass1 of 1Pass, no detail recorded.
Agent platform configsFail0 of 1Could not locate a public repo containing agent configs or rules. If our probes missed it, AI coding agents likely will too - link the repo from your homepage or docs so it's discoverable.
Agent Plugins manifestFail0 of 1No Agent Plugins manifest (plugin.json) found in discovered repos
ChatGPT app listedFail0 of 2Not found in ChatGPT app directory

Access: 0 of 44

Access checks on dickssportinggoods.com, read 14 Nov 2026; 11 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
Sitemap existsFail0 of 2No sitemap found
Content without JavaScriptNot run0 of 3Could not fetch homepage
Not blocked by bot detectionFail0 of 2Agents blocked: GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended
Agent discovery fileFail0 of 2No agent discovery file found
A2A / agent-cardFail0 of 2No A2A agent card found at /.well-known/agent-card.json
Listed on skills.shFail0 of 1No official skills self-published on skills.sh (5 community skills with potential relation to this domain found, but only self-published official skills count)
pricing.md existsFail0 of 2No pricing.md found - agents need machine-readable pricing to compare products and make purchase recommendations
NLWeb Schema FeedsFail0 of 1No robots.txt found - cannot check for Schema Feeds
MCP well-known discoveryFail0 of 2No MCP server URL discovered
Agent mode viewFail0 of 2No agent mode view detected at ?mode=agent (optional)
HTTP Link headers (RFC 8288)Fail0 of 1No HTTP Link response headers (RFC 8288) found
Markdown URL fallbackFail0 of 2Homepage does not support the .md suffix. Probed https://dickssportinggoods.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body).
Modular llms.txt per product areaFail0 of 1No section-level llms.txt files found (optional)
llms.txt existsFail0 of 1No llms.txt found at /llms.txt or /.well-known/llms.txt.
llms.txt formattingFail0 of 2No llms.txt found to evaluate quality
JSON-LD structured dataNot run0 of 4Could not fetch homepage
Pricing info accessibleFail0 of 3No pricing page or pricing data found
Public API/docs linked from homepageFail0 of 3No public API or documentation page linked from homepage
Agent instruction / when-to-useFail0 of 3No agent instruction file with when-to-use guidance found
Skills.sh skill qualityFail0 of 2No official skills on skills.sh to evaluate
JSON-LD entity linking (sameAs)Not run0 of 2Not run, no detail recorded.
Metadata completenessNot run0 of 2Could not fetch homepage
Organization schema completenessNot run0 of 2Not run, no detail recorded.
Schema type breadthNot run0 of 2Not run, no detail recorded.
Trust anchor pagesFail0 of 2No trust anchor pages found with sufficient content (About, Contact, Privacy)
OpenAPI spec publishedFail0 of 7No OpenAPI/Swagger specification found
API catalog (RFC 9727)Fail0 of 2No /.well-known/api-catalog found (RFC 9727)
Markdown agent docsFail0 of 1Missing markdown content negotiation. Homepage returned text/html when probed with Accept: text/markdown (expected text/markdown), and none of the well-known root paths (/llms.md, /auth.md, /agents.md, /developers.md
Markdown content negotiation (acceptmarkdown.com)Fail0 of 1Homepage https://dickssportinggoods.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; Vary header missing Accept (got "none")
Bot-UA markdown servingFail0 of 1No probed bot User-Agent (GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended, Applebot-Extended, ora-agent, DeepSeekBot) receives markdown when requesting HTML.
Agent crawler reachabilityFail0 of 2No major AI crawler can reach the homepage - ChatGPT-User: blocked, ClaudeBot: blocked, Google-Extended: blocked, ora-agent: blocked, DeepSeekBot: blocked

Usability: 8 of 44

Usability checks on dickssportinggoods.com, read 14 Nov 2026; 36 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
Public API with reachable endpointsPass7 of 7GraphQL endpoint at https://dickssportinggoods.com/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. Best-of-protocols score: 7/7.
Agent onboarding frictionFail0 of 2Insufficient content to evaluate onboarding friction
Web Bot Auth directoryFail0 of 2No /.well-known/http-message-signatures-directory found
OAuth Protected Resource metadata (RFC 9728)Fail0 of 2No /.well-known/oauth-protected-resource found (RFC 9728)
auth.md existsFail0 of 2No /auth.md found at site root
auth.md structureFail0 of 2No /auth.md found at site root
Agent auth discovery metadataFail0 of 3Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: dickssportinggoods.com, api.dickssportinggoods.com.
Agent auth WWW-Authenticate hintFail0 of 1No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://dickssportinggoods.com/api, https://dickssportinggoods.com/api/v1, https://dickssportinggoods.com/v1, https://dickssportinggoods.com/v2
agent_auth endpoints reachableFail0 of 2No agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe
MCP server / manifestFail0 of 6No MCP server or manifest found
WebMCP supportFail0 of 5No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found
Rate limit response headersFail0 of 2GraphQL introspection auth-gated and no header convention documented on GraphQL-tagged pages
Idempotency-Key supportFail0 of 3GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages
JSON error responsesFail0 of 4API does not return JSON error responses (or no API detected)
NLWeb /ask endpointPass1 of 1NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET)
NLWeb streaming supportFail0 of 1NLWeb /ask requires authentication - cannot verify streaming
MCP server-card.jsonFail0 of 2No MCP server card found at /.well-known/mcp/server-card.json
Product + docs MCP coverageFail0 of 2This bonus needs two MCP servers: one for your product so agents can take actions, and a separate one for your documentation so agents can answer questions from your docs.
Sandbox / test environmentFail0 of 2No sandbox or test environment found
GraphQL typed error modelFail0 of 3GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
GraphQL versioning / deprecation policyFail0 of 2GraphQL introspection auth-gated and no graphql versioning / deprecation policy documentation found on GraphQL-tagged pages
GraphQL pagination patternFail0 of 2GraphQL introspection auth-gated and no graphql pagination pattern documentation found on GraphQL-tagged pages
GraphQL async-job patternFail0 of 2GraphQL introspection auth-gated and no graphql async-job pattern documentation found on GraphQL-tagged pages
Agent-friendly 404sPartial1 of 2Nonexistent paths return HTTP 403 instead of 404/410 - agents get a non-200 signal but not the standard not-found semantics
API schema complexity analysisFail0 of 2GraphQL: introspection auth-gated and no schema evidence in docs
Function calling compatibilityFail0 of 2No API spec found - function calling requires discoverable endpoints

The fixes worth most points

Ora attaches an estimate to each failing or partial check: how many points the site would gain by passing it. These are the 5 with the largest estimates for Dick's Sporting Goods.

MCP server / manifest
Fail, 0 of 6, about 6.1 points to gain. Ora saw: No MCP server or manifest found.
Developer resource discoverability
Partial, 1 of 3, about 5.6 points to gain. Ora saw: Agent struggled to find developer resources by name - only 1 result(s) out of 10. Not found in this search sample: API docs, OpenAPI spec, developer portal, auth docs, MCP server, SDK documentation.
Brand name discoverability
Partial, 1 of 3, about 5.6 points to gain. Ora saw: dickssportinggoods.com appears once in brand-name search results for "dickssportinggoods" (position #5 out of 7).
OpenAPI spec published
Fail, 0 of 7, about 5.3 points to gain. Ora saw: No OpenAPI/Swagger specification found.
WebMCP support
Fail, 0 of 5, about 5.1 points to gain. Ora saw: No WebMCP support detected - no tool-attribute forms and no document.modelContext / navigator.modelContext usage found.

Our read

Dick's Sporting Goods turns agents away at the door, and with the home page unreadable Ora found no commerce signals, so the six payment checks did not apply on this read. Bot detection blocked GPTBot, ClaudeBot, ChatGPT-User, PerplexityBot, Google-Extended and Applebot-Extended, and robots.txt answered with a 403. The Access layer reads 0 of 44. Because the home page could not be fetched, the JSON-LD, metadata and text rows are unverified rather than failed. Behind the shield there is more than the score shows: a GraphQL endpoint at dickssportinggoods.com/graphql whose introspection requires authentication, an SDK package on npm, and an NLWeb /ask endpoint that answers with a 403. Neither an MCP server nor an OpenAPI specification turned up, and the MCP server is the fix worth most, about 6 points. The brand search and the Wikipedia lookup ran on the bare string dickssportinggoods, which describes the probe more than the retailer. An F at 16, decided at the door before a single shelf was read.

Test your own checkout

The scan above is free and needs no account: enter a domain at ora.ai and read the same layers for your own site, with the six payment checks mapped to this matrix on the Ora Payments page. The command below runs the same audit from a terminal and exits with 1 under the score you set, so it can gate a deploy. Why Ora, and its limits.

npx ax@0.10 audit https://example.com --min-score 70

All 360 checks, one company a day. Corrections to the corrections page.

Sources

  1. ora.ai/api/score/dickssportinggoods.com, Ora's scan (vendor), read 14 Nov 2026
  2. Ora check catalog (GET /api/checks), read 14 Nov 2026
  3. dickssportinggoods.com, the company's site, read 14 Nov 2026

Last reviewed