Agent Ready CheckoutEdition . The pay layer for agents.

360 check, 9 Nov 2026

Dollar General on the pay layer: the 360 agent-readiness check

In short

Dollar General scores 50 of 100 on Ora's agent-readiness scan, a C, read 14 Nov 2026. The six payment checks did not apply to dollargeneral.com on this read, which is how Ora treats a site it does not read as a shop. Four agent files published, and four of them fail to parse.

On 14 Nov 2026 the public site at dollargeneral.com scored 50 of 100 on Ora's agent-readiness scan, a C. Dollar General is the discount chain with the most stores 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: Dollar General offers solid search visibility and crawlability, but lacks a public API and OpenAPI specification for agent integration.

The score

Dollar General on Ora, read 14 Nov 2026: points per layer, with the share of each layer's maximum. 17 checks pass, 20 are partial, 38 fail and 57 do not apply to this site.
LayerPointsShareWhat the layer asks
Discovery10 of 1471%Can agents find and recommend it
Access25 of 5347%Can agents read it
Usability20 of 4842%Can agents use it
Payments0 of 0none applyCan agents pay
Total50 of 10050%Grade C

The pay layer

Ora did not run the six payment checks against dollargeneral.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 dollargeneral.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
MPPDoes not apply0 of 2MPP in the matrixNo MPP (Machine Payments Protocol) support detected
UCPDoes not apply0 of 3UCP in the matrixno UCP (Universal Commerce Protocol) signals detected
ACPDoes not apply0 of 3ACP in the matrixno ACP (Agentic Commerce Protocol) signals detected
ACP delegate paymentDoes not apply0 of 3ACP in the matrixNo ACP Delegate Payment signals detected
AP2Does not apply0 of 3AP2 in the matrixNo AP2 (Agent Payments Protocol) signals detected

The other layers, check by check

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

Discovery: 10 of 14

Discovery checks on dollargeneral.com, read 14 Nov 2026; 6 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
ARD discoveryPartial0 of 1/.well-known/ard.json exists but is not valid JSON
AI Catalog discoveryPartial0 of 1/.well-known/ai-catalog.json exists but is not valid JSON
Developer resource discoverabilityFail0 of 3In a search for your API docs, none of the 10 results is your official docs
Brand name discoverabilityPass3 of 3dollargeneral.com ranks #3 for "Dollar General" (searched your brand name alone: no main product term from your homepage qualified)
Wikipedia / Wikidata entity presencePass4 of 4Wikipedia "Dollar General" and Wikidata Q145168 both verified - domain confirmed on both sources
robots.txt AI crawler policyPass2 of 2AI 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: 25 of 53

Access checks on dollargeneral.com, read 14 Nov 2026; 4 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
Sitemap existsPass2 of 2Valid sitemap found at https://www.dollargeneral.com/sitemap.xml with multiple sitemaps entries
Content without JavaScriptPartial1 of 3Homepage: 11784 chars of readable text, but no H1 tag. Sampled pages with almost no text without JavaScript (1 of 3): https://www.dollargeneral.com/store-directory/ny/glenfield (190 chars).
Not blocked by bot detectionPass2 of 2Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
Agent discovery filePartial1 of 2Found legacy /.well-known/agent-skills; /.well-known/agent-skills/index.json exists but is not valid JSON - fix the file or remove it so agents fall back to /.well-known/agent-skills, /agents.md, or /skills.sh
Agent Skills index conformance (v0.2.0)Fail0 of 2/.well-known/agent-skills/index.json is not valid JSON
A2A / agent-cardPartial1 of 2agent-card.json exists but contains invalid JSON
Listed on skills.shFail0 of 1No official skills self-published on skills.sh (2 community skills with potential relation to this domain found, but only self-published official skills count)
pricing.md existsPartial1 of 2pricing.md found at /.well-known/pricing.md (2457 lines), but it does not open with a # heading - start it with a # title so agents read it as markdown
NLWeb Schema FeedsFail0 of 1No schemamap: directive in robots.txt
MCP well-known discoveryFail0 of 2No MCP server URL discovered
Agent mode viewFail0 of 2?mode=agent returns same content as homepage (no dedicated agent view)
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://dollargeneral.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, /verify-email/llms.txt, /sign-in/llms.txt, /sign-up/llms.txt, /shopping-list/llms.txt
Sitemap freshness (lastmod)Pass1 of 1Pass, no detail recorded.
robots.txt agent-user policyPass2 of 2No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://dollargeneral.com/. Declared policy only
llms.txt existsPartial0 of 1A file is present at https://dollargeneral.com/.well-known/llms.txt, but it returns an HTML page rather than a plain-text llms.txt.
llms.txt formattingFail0 of 2No llms.txt found to evaluate quality
JSON-LD structured dataPartial1 of 4JSON-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 accessiblePartial2 of 3Product page https://www.dollargeneral.com/p/holiday-style-led-battery-operated-lights-10-ct-assorted/430001983857 shows a price only in its text ($1). Add Product markup with an Offer price so agents can read it reliably
Public API/docs linked from homepageFail0 of 3No public API or documentation page linked from homepage
Agent instruction / when-to-usePartial2 of 3Agent instruction file at /.well-known/agent-skills/ but no explicit when-to-use guidance
Skills.sh skill qualityFail0 of 2No official skills on skills.sh to evaluate
JSON-LD entity linking (sameAs)Fail0 of 2No sameAs entity linking in JSON-LD - agents cannot disambiguate your brand
Metadata completenessPass2 of 2All metadata signals present: canonical URL, lang="en", og:image, og:type
Organization schema completenessFail0 of 2No Organization type found in JSON-LD
Schema type breadthPartial1 of 2Some extended schema types found: BreadcrumbList - add 2 more types that match what the homepage shows, for full coverage
Trust anchor pagesPartial1 of 2About, Privacy pages verified - missing: Contact
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 4 measured pages fit an agent context budget (largest ~3K tokens)
Content behind authPartial1 of 2Some sampled pages are auth-gated: 2 return 401/403 (https://www.dollargeneral.com/store-directory/ga/marietta/3937 and https://www.dollargeneral.com/store-directory/sc/south-congaree/6282)
OpenAPI spec publishedFail0 of 7No OpenAPI/Swagger specification found
API catalog (RFC 9727)Partial1 of 2api-catalog responded but body is not valid JSON
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://dollargeneral.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 reachabilityPass2 of 2Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable

Usability: 20 of 48

Usability checks on dollargeneral.com, read 14 Nov 2026; 41 more checks in this layer did not apply to the site.
CheckResultPointsWhat Ora saw
Public API with reachable endpointsFail0 of 7No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
OAuth 2.0 supportPass5 of 5OpenID Connect discovery endpoint found at https://dollargeneral.com
Scoped permissionsFail0 of 5No declared OAuth scopes, security schemes, or scoped-permission documentation found
Agent onboarding frictionPartial1 of 2Onboarding signals described but not verified live: self-serve key generation
Web Bot Auth directoryPartial1 of 2Web Bot Auth directory found but body is not valid JSON
OAuth Protected Resource metadata (RFC 9728)Fail0 of 2No /.well-known/oauth-protected-resource found (RFC 9728)
auth.md existsFail0 of 2Path https://dollargeneral.com/auth.md returned HTML (SPA / 404 fallback), not an auth.md document
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: dollargeneral.com, api.dollargeneral.com.
Agent auth WWW-Authenticate hintFail0 of 1No 401 with WWW-Authenticate: Bearer resource_metadata=... found. Probed [https://dollargeneral.com/api, https://dollargeneral.com/api/v1, https://dollargeneral.com/v1, https://dollargeneral.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 / manifestPartial2 of 6/.well-known/mcp/manifest.json redirects to an HTML page (https://www.dollargeneral.com/errorpages/404), not an MCP endpoint
JSON error responsesFail0 of 4API 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
Agent-friendly 404sPartial1 of 2The nonexistent path https://dollargeneral.com/__ora-404-probe-iqx4yx1x correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
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.
MCP Apps supportFail0 of 4No 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 supportFail0 of 2No A2UI or generative UI support detected
API schema complexity analysisPartial1 of 2REST: OpenAPI spec found but failed to parse for complexity analysis
Function calling compatibilityPartial1 of 2API spec found but couldn't validate function calling compatibility

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 Dollar General.

Public API with reachable endpoints
Fail, 0 of 7, about 6.5 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated).
Developer resource discoverability
Fail, 0 of 3, about 4.8 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs.
Scoped permissions
Fail, 0 of 5, about 4.6 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found.
OpenAPI spec published
Fail, 0 of 7, about 4.4 points to gain. Ora saw: No OpenAPI/Swagger specification found.
JSON error responses
Fail, 0 of 4, about 3.7 points to gain. Ora saw: API does not return JSON error responses (or no API detected).

Our read

Dollar General has more agent files than most retailers here, and they are broken. The agent skills index at /.well-known/agent-skills/index.json is not valid JSON, the A2A agent card is not valid JSON, the MCP manifest path redirects to a 404 page, and the llms.txt at /.well-known/llms.txt returns an HTML page: four files, four parse failures. The reading side is better: the door is open to all four agent user agents, robots.txt allows the search and training crawlers, the sitemap is valid and the home page gives 11,784 characters of text, without an H1 and with one JSON-LD block that lacks an identity type. The six payment checks did not apply on this read, and Ora's UCP probe found no signal on the domain of the retailer with more stores than any other in the United States. The act layer is OpenID Connect discovery and nothing else, with no publicly reachable API. Fix the four files and the C moves on its own.

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

Last reviewed