360 check, 9 Nov 2026
Target on the pay layer: the 360 agent-readiness check
In short
Target scores 41 of 100 on Ora's agent-readiness scan, a D, read 14 Nov 2026. The six payment checks did not apply to target.com on this read, which is how Ora treats a site it does not read as a shop. Live on UCP in the matrix, and no UCP profile on its own domain.
On 14 Nov 2026 the public site at target.com scored 41 of 100 on Ora's agent-readiness scan, a D, in Ora's E-commerce category. Target is the US general merchandise retailer that sits in this site's matrix as a column, 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
| Layer | Points | Share | What the layer asks |
|---|---|---|---|
| Discovery | 7 of 10 | 70% | Can agents find and recommend it |
| Access | 26.83 of 45 | 60% | Can agents read it |
| Usability | 6.43 of 51 | 13% | Can agents use it |
| Payments | 0 of 0 | none apply | Can agents pay |
| Total | 41 of 100 | 41% | Grade D |
The pay layer
Ora did not run the six payment checks against target.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.
| Payment check | Result | Points | Matrix row | What Ora saw |
|---|---|---|---|---|
| x402 | Does not apply | 0 of 2 | x402 in the matrix | No x402 payment protocol support detected. No working way for an agent to pay was found, so payments are not scored |
| MPP | Does not apply | 0 of 2 | MPP in the matrix | No MPP (Machine Payments Protocol) support detected. No working way for an agent to pay was found, so payments are not scored |
| UCP | Does not apply | 0 of 3 | UCP in the matrix | no UCP (Universal Commerce Protocol) signals detected. No working way for an agent to pay was found, so payments are not scored |
| ACP | Does not apply | 0 of 3 | ACP in the matrix | no 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 target.com, grouped by layer, with the result, the points and what Ora recorded where its wording passes this site's gate.
Discovery: 7 of 10
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| ARD discovery | Fail | 0 of 1 | No /.well-known/ard.json, no same-site rel="ard" link, and no legacy /.well-known/ai-catalog.json |
| Developer resource discoverability | Pass | 4 of 4 | Pass, no detail recorded. |
| Brand name discoverability | Partial | 1 of 3 | target.com ranks #8 for "Target" (searched your brand name alone: no main product term from your homepage qualified) |
| robots.txt AI crawler policy | Pass | 1 of 1 | AI 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 configs | Fail | 0 of 1 | Could 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 manifest | Fail | 0 of 1 | No Agent Plugins manifest (plugin.json) found in discovered repos |
| ChatGPT app listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Homepage not hidden from search | Pass | 1 of 1 | No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search. |
Access: 26.83 of 45
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Sitemap exists | Pass | 1 of 1 | Valid sitemap found at https://www.target.com/sitemap_keywords-index.xml.gz with multiple sitemaps entries |
| Content without JavaScript | Partial | 3.33 of 5 | Homepage: 3001 chars with H1, but 1.9% content ratio is below the 5% target. No inner pages checked: the 5 sampled pages were skipped (forms, login pages, bot challenges, error pages |
| Not blocked by bot detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent discovery file | Fail | 0 of 2 | No agent discovery file found |
| A2A / agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Listed on skills.sh | Fail | 0 of 1 | No 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 exists | Fail | 0 of 2 | No pricing.md found - agents need machine-readable pricing to compare products and make purchase recommendations |
| NLWeb Schema Feeds | Fail | 0 of 1 | No schemamap: directive in robots.txt |
| MCP well-known discovery | Fail | 0 of 2 | No MCP server URL discovered |
| HTTP Link headers (RFC 8288) | Fail | 0 of 1 | No HTTP Link response headers (RFC 8288) found |
| Markdown URL fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://target.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 area | Fail | 0 of 1 | No section-level llms.txt found. Tried /docs/llms.txt, /api/llms.txt, /developers/llms.txt, /guides/llms.txt, /reference/llms.txt, /circlecard/llms.txt, /gift-registry/llms.txt, /weekly-ad/llms.txt, /account/llms.txt, /cart/llms.txt. |
| robots.txt agent-user policy | Pass | 1 of 1 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://target.com/. Declared policy only |
| llms.txt exists | Pass | 1 of 1 | Found the llms.txt at https://developer.target.com/llms.txt. |
| llms.txt formatting | Pass | 2 of 2 | The llms.txt is well-formatted: 64 lines with markdown links, 6,158 characters in total. |
| JSON-LD structured data | Partial | 0.5 of 2 | JSON-LD found (1 block(s)) but no identity type - use SoftwareApplication, Product, Organization, Person, or Article so agents can tell what this site is |
| Pricing info accessible | Fail | 0 of 3 | No pricing page or pricing data found |
| Public API/docs linked from homepage | Pass | 4 of 4 | Documentation site found at https://developer.target.com |
| Agent instruction / when-to-use | Fail | 0 of 1 | No agent instruction file with when-to-use guidance found |
| Skills.sh skill quality | Fail | 0 of 2 | No official skills on skills.sh to evaluate |
| JSON-LD entity linking (sameAs) | Fail | 0 of 1 | No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand |
| Metadata completeness | Partial | 0.5 of 1 | 3/4 metadata signals present - missing: og:image |
| Organization schema completeness | Fail | 0 of 1 | No Organization type found in JSON-LD |
| Trust anchor pages | Partial | 0.5 of 1 | About, Privacy pages verified - missing: Contact |
| llms.txt links resolve | Pass | 2 of 2 | Pass, no detail recorded. |
| Markdown alternate link | Fail | 0 of 1 | No 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 hygiene | Pass | 1 of 1 | Pass, no detail recorded. |
| Page token budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~1K tokens) |
| Content starts near the top | Pass | 1 of 1 | Pass, no detail recorded. |
| Code fence validity | Pass | 1 of 1 | Pass, no detail recorded. |
| Content behind auth | Pass | 1 of 1 | All 5 sampled pages are publicly readable (0 with substantive content) |
| OpenAPI spec published | Fail | 0 of 8 | No OpenAPI/Swagger specification found |
| Developer portal | Pass | 5 of 5 | Developer portal found at https://developer.target.com |
| API catalog (RFC 9727) | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| Markdown agent docs | Fail | 0 of 1 | Missing 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) | Fail | 0 of 1 | Homepage https://target.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 serving | Fail | 0 of 1 | No 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 reachability | Pass | 1 of 1 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
Usability: 6.43 of 51
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Public API with reachable endpoints | Partial | 3.43 of 8 | Documentation site found at https://developer.target.com but API content unclear. Best-of-protocols score: 3/7. |
| OAuth 2.0 support | Partial | 2 of 5 | OAuth mentioned on homepage but no standard endpoints found |
| Scoped permissions | Fail | 0 of 5 | No declared OAuth scopes, security schemes, or scoped-permission documentation found |
| Agent onboarding friction | Partial | 1 of 2 | Onboarding signals described but not verified live: self-serve key generation, sandbox/test environment |
| Web Bot Auth directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
| auth.md exists | Fail | 0 of 2 | No /auth.md found at site root |
| auth.md structure | Fail | 0 of 2 | No /auth.md found at site root |
| Agent auth discovery metadata | Fail | 0 of 3 | Neither /.well-known/oauth-protected-resource nor /.well-known/oauth-authorization-server found. Probed: target.com, api.target.com. |
| Agent auth WWW-Authenticate hint | Fail | 0 of 1 | No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://target.com/api, https://target.com/api/v1, https://target.com/v1, https://target.com/v2, https://target.com/agent/identity, https://target.com/agent/auth |
| agent_auth endpoints reachable | Fail | 0 of 2 | No agent_auth endpoint URIs found in AS metadata or /auth.md prose; nothing to probe |
| MCP server / manifest | Fail | 0 of 10 | No MCP server or manifest found |
| WebMCP support | Fail | 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| JSON error responses | Fail | 0 of 3 | API does not return JSON error responses (or no API detected) |
| NLWeb /ask endpoint | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| NLWeb streaming support | Fail | 0 of 1 | NLWeb /ask does not support SSE streaming via GET or POST |
| MCP server-card.json | Fail | 0 of 2 | No 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 coverage | Fail | 0 of 2 | This 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. |
| Agent-friendly 404s | Fail | 0 of 2 | Docs host developer.target.com: Nonexistent paths return HTTP 200 with the app shell (soft-404). Agents probing for resources conclude every path exists. Return a real HTTP 404 status for unknown paths. |
| Accessible document structure | Pass | 3 of 3 | Pass, no detail recorded. |
| Native interactive controls | Pass | 3 of 3 | Pass, no detail recorded. |
| Accessible names on controls | Pass | 2 of 2 | Pass, no detail recorded. |
| Accessibility-tree injection safety (bonus) | Pass | 2 of 2 | Pass, no detail recorded. |
| MCP Apps support | Fail | 0 of 4 | No MCP Apps support detected - this product has an in-agent UI surface but exposes no ui:// resources or tool UI metadata for agents to render. |
| A2UI / generative UI support | Fail | 0 of 2 | No A2UI or generative UI support detected |
| API schema complexity analysis | Fail | 0 of 2 | No API schema detected |
| Function calling compatibility | Fail | 0 of 2 | No 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 Target.
- MCP server / manifest
- Fail, 0 of 10, about 8.7 points to gain. Ora saw:
No MCP server or manifest found
. - WebMCP support
- Fail, 0 of 8, about 7 points to gain. Ora saw:
No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
. - OpenAPI spec published
- Fail, 0 of 8, about 5.9 points to gain. Ora saw:
No OpenAPI/Swagger specification found
. - Brand name discoverability
- Partial, 1 of 3, about 4.4 points to gain. Ora saw:
target.com ranks #8 for "Target" (searched your brand name alone: no main product term from your homepage qualified)
. - Scoped permissions
- Fail, 0 of 5, about 4.4 points to gain. Ora saw:
No declared OAuth scopes, security schemes, or scoped-permission documentation found
.
Our read
Target is the one retailer in this site's matrix with a live UCP cell, a fact sheet saying shoppers buy from Target in Google AI Mode and Gemini via a protocol Target co-developed, and Ora finds no UCP signal on target.com itself: the six payment checks were probed and none answered, so the pay layer reads 0 of 0. The two are not in conflict. UCP checkout runs through Google's surfaces, and nothing on the retailer's own domain declares it, which is the gap the matrix and the scan read from different sides. The rest is the best of the US retailers here. The door is open to all four agent user agents, robots.txt allows the search and training crawlers, the sitemap is valid, and developer.target.com is a real portal with an llms.txt. The gaps are an MCP server, an OpenAPI specification and declared scopes, about 13 points, and a home page at 1.8 percent text. A UCP profile on target.com would turn the live cell into a scored layer.
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 70All 360 checks, one company a day. Corrections to the corrections page.
Sources
- ora.ai/api/score/target.com, Ora's scan (vendor), read 14 Nov 2026
- Ora's scoring rules, version 3 (vendor), read 14 Nov 2026
- Ora check catalog (GET /api/checks), read 14 Nov 2026
- target.com, the company's site, read 14 Nov 2026
Last reviewed