Agent Ready CheckoutEdition . The pay layer for agents.

360 check, 9 Nov 2026

Costco on the pay layer: the 360 agent-readiness check

In short

Costco scores 26 of 100 on Ora's agent-readiness scan, an F, read 14 Nov 2026. The six payment checks did not apply to costco.com on this read, which is how Ora treats a site it does not read as a shop. An open door onto 414 characters and a GraphQL endpoint behind a key.

On 14 Nov 2026 the public site at costco.com scored 26 of 100 on Ora's agent-readiness scan, an F, in Ora's E-commerce category. Costco is the membership warehouse club, selling online to members in a dozen countries, 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.

The score

Costco on Ora, read 14 Nov 2026: points per layer, with the share of each layer's maximum. 16 checks pass, 5 are partial, 54 fail and 63 do not apply to this site.
LayerPointsShareWhat the layer asks
Discovery3 of 1030%Can agents find and recommend it
Access10.67 of 3828%Can agents read it
Usability14 of 6522%Can agents use it
Payments0 of 0none applyCan agents pay
Total26 of 10026%Grade F

The pay layer

Ora did not run the six payment checks against costco.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 costco.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 x402 payment protocol support detected. No working way for an agent to pay was found, so payments are not scored
MPPDoes not apply0 of 2MPP in the matrixNo MPP (Machine Payments Protocol) support detected. No working way for an agent to pay was found, so payments are not scored
UCPDoes not apply0 of 3UCP in the matrixno UCP (Universal Commerce Protocol) signals detected. No working way for an agent to pay was found, so payments are not scored
ACPDoes not apply0 of 3ACP in the matrixno ACP (Agentic Commerce Protocol) signals detected. No working way for an agent to pay was found, so payments are not scored

The other layers, check by check

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

Discovery: 3 of 10

Discovery checks on costco.com, read 14 Nov 2026; 6 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
ARD discoveryFail0 of 1No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json
Developer resource discoverabilityFail0 of 4In a search for your API docs, none of the 10 results is your official docs
Brand name discoverabilityPartial1 of 3costco.com ranks #7 for "costco" (searched your brand name alone: no main product term from your homepage qualified)
robots.txt AI crawler policyPass1 of 1AI search crawlers: allowed in 3 of 3 checks (3 crawlers on 1 page). AI training crawlers: allowed in 2 of 2 checks (2 crawlers on 1 page), not scored.
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
Homepage not hidden from searchPass1 of 1No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.

Access: 10.67 of 38

Access checks on costco.com, read 14 Nov 2026; 6 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
Sitemap existsPass1 of 1Valid sitemap found at https://www.costco.com/sitemap_lw_index.xml with multiple sitemaps entries
Content without JavaScriptPartial1.67 of 5Homepage: Only 299 chars of text content - agents see limited content. No inner pages checked: the 5 sampled pages were skipped (forms, login pages, bot challenges, error pages
Not blocked by bot detectionPass2 of 2Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
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 (100 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 schemamap: directive in robots.txt
MCP well-known discoveryFail0 of 2No MCP server URL discovered
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://costco.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 found. Tried /docs/llms.txt, /api/llms.txt, /developers/llms.txt, /guides/llms.txt, /reference/llms.txt, /myaccount/llms.txt, /checkoutcartview/llms.txt, /warehouse-locations/llms.txt
robots.txt agent-user policyPass1 of 1No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://costco.com/. Declared policy only
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 dataFail0 of 2No JSON-LD structured data found on homepage
Pricing info accessibleFail0 of 3No pricing page or pricing data found
Public API/docs linked from homepageFail0 of 4No public API or documentation page linked from homepage
Agent instruction / when-to-useFail0 of 1No 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)Fail0 of 1No JSON-LD found - no entity linking possible
Metadata completenessPartial0.5 of 12/4 metadata signals present - missing: og:image, og:type
Organization schema completenessFail0 of 1No JSON-LD found - Organization schema missing
Trust anchor pagesPartial0.5 of 1About, Contact pages verified - missing: Privacy
Markdown alternate linkFail0 of 1No sampled page advertises a markdown alternate. Add <link rel="alternate" type="text/markdown" href="..."> (or the equivalent Link response header) pointing at a markdown twin of the page.
Redirect hygienePass1 of 1Pass, no detail recorded.
Page token budgetPass1 of 1All 6 measured pages fit an agent context budget (largest ~1K tokens)
Content behind authPass1 of 1All 5 sampled pages are publicly readable (5 with substantive content)
OpenAPI spec publishedFail0 of 8No 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://costco.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding")
Bot-UA markdown servingFail0 of 1No probed bot User-Agent (ChatGPT-User, Claude-User, Perplexity-User) receives markdown when requesting HTML. Optional: detect AI-bot UAs server-side and serve them a markdown representation directly.
Agent crawler reachabilityPass1 of 1Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable

Usability: 14 of 65

Usability checks on costco.com, read 14 Nov 2026; 46 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
Public API with reachable endpointsPass8 of 8GraphQL endpoint at https://ecom-api.costco.com/ebusiness/product/v1/products/graphql\ is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access.
OAuth 2.0 supportPass5 of 5OpenID Connect discovery endpoint found at https://login.costco.com
Scoped permissionsFail0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
Agent onboarding frictionFail0 of 2High onboarding friction - no free tier, self-serve keys, or sandbox detected
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: costco.com, api.costco.com.
Agent auth WWW-Authenticate hintFail0 of 1No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://costco.com/api, https://costco.com/api/v1, https://costco.com/v1, https://costco.com/v2, https://costco.com/agent/identity, https://costco.com/agent/auth
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 10No MCP server or manifest found
WebMCP supportFail0 of 8No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 66 of 66 same-origin script bundle(s) for modelContext registrations)
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 3API does not return JSON error responses (or no API detected)
NLWeb /ask endpointFail0 of 1No NLWeb-conformant /ask endpoint found via GET or POST
NLWeb streaming supportFail0 of 1NLWeb /ask does not support SSE streaming via GET or POST
MCP server-card.jsonFail0 of 2No MCP server card found (checked /.well-known/mcp/server-card.json, the site's ai-catalog.json, servers[].card in mcp.json, and <server>/server-card)
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 2The nonexistent path https://costco.com/__ora-404-probe-oleot6jx correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
Accessible document structurePass3 of 3Pass, no detail recorded.
Native interactive controlsPass3 of 3Pass, no detail recorded.
Accessible names on controlsPass2 of 2Pass, no detail recorded.
Form control labelingPass2 of 2Pass, no detail recorded.
Accessibility-tree injection safety (bonus)Pass2 of 2Pass, no detail recorded.
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 Costco.

Developer resource discoverability
Fail, 0 of 4, about 8.9 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs.
OpenAPI spec published
Fail, 0 of 8, about 7 points to gain. Ora saw: No OpenAPI/Swagger specification found.
MCP server / manifest
Fail, 0 of 10, about 6.8 points to gain. Ora saw: No MCP server or manifest found.
WebMCP support
Fail, 0 of 8, about 5.5 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 66 of 66 same-origin script bundle(s) for modelContext registrations).
Brand name discoverability
Partial, 1 of 3, about 4.4 points to gain. Ora saw: costco.com ranks #7 for "costco" (searched your brand name alone: no main product term from your homepage qualified).

Our read

Costco opens the door and gives an agent 414 characters to read. All four agent user agents reach costco.com, robots.txt allows the search and training crawlers and the sitemap index is valid, but the home page renders almost nothing without JavaScript, carries no JSON-LD and the domain has no llms.txt. The six payment checks did not apply on this read, and Ora's UCP probe found no signal on the domain, so the pay layer reads 0 of 0. The act layer is what a warehouse club's public site would be expected to have, which is a GraphQL endpoint at ecom-api.costco.com with introspection gated, and nothing else: neither a developer portal nor an OpenAPI specification, neither an MCP server nor OAuth beyond a mention on the home page. Ora's search for Costco developer resources found nothing, which costs 5.6 points on its own. A members-only business has reasons to keep its API private; the home page text is the fix that costs nothing.

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/costco.com, Ora's scan (vendor), read 14 Nov 2026
  2. Ora's scoring rules, version 3 (vendor), read 14 Nov 2026
  3. Ora check catalog (GET /api/checks), read 14 Nov 2026
  4. costco.com, the company's site, read 14 Nov 2026

Last reviewed