Checkout.com: the 360 agent-readiness check
Checkout.com scores 73 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 2: a public API, OAuth. A home page worth copying, in front of an API with no specification.
On 9 November 2026 the public site at checkout.com scored 73 of 100 on Ora's agent-readiness scan, a B, in Ora's Payments & Fintech category. Ora probes a site the way an agent would: it requests pages with the agents' own user agents, reads robots.txt, looks for the files agents read, and tries the API, MCP and payment surfaces. This check reads the act layer first, because that is what the directory records, then the door, what an agent can read, and whether the company is found and recommended. Ora's one-line summary: Checkout.com offers strong developer SDKs and documentation discovery, but needs an OpenAPI specification for agent integration.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 39 of 63 | 62% |
| Access | Can agents read it | 47 of 61 | 77% |
| Discovery | Can agents find and recommend it | 14 of 16 | 88% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 73 of 100 | 73% |
What an agent can do
The surfaces an agent acts on: an API it can find and call, an MCP server, an agent card, OAuth metadata, a command line. This is the layer the directory records, so it comes first. 2 checks in this group do not apply to this site and are left out.
In the directory, Checkout.com sign-in required, tools not seen, not counted; the connector run of 4 November 2026 is on the entry page. Ora's MCP server check for the same domain reads partial; the two look for different things, the directory for a server that answers a handshake and lists tools, Ora for a server it can find from the site.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | MCP server detected at https://support.checkout.com/mcp; it requires authentication. Presence is verified (5/6), but Ora could not inspect its tools or verify access scopes without credentials. |
| MCP well-known discovery mcp-well-known-discovery | Partial | 1 of 2 | MCP server at https://support.checkout.com/mcp - list its server card, hosted on your own domain, in /.well-known/ai-catalog.json so MCP clients can discover it |
| Public API with reachable endpoints public-api | Pass | 7 of 7 | REST API documentation found at https://www.checkout.com/docs/payments.md. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | API/docs link found on homepage and resolves: https://www.checkout.com/docs |
| Developer portal developer-portal | Pass | 6 of 6 | Developer portal found at /docs |
| OpenAPI spec published openapi-spec | Fail | 0 of 7 | No OpenAPI/Swagger specification found |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| A2A / agent-card a2a-agent-card | Fail | 0 of 2 | No A2A agent card found at /.well-known/agent-card.json |
| Agent discovery file agent-discovery-file | Fail | 0 of 2 | No agent discovery file found |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://support.checkout.com/mcp/oauth |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Pass | 2 of 2 | no detail published |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 5 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Fail | 0 of 3 | No CLI tool found |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 3 ecosystems: npm, go, rubygems |
| JSON error responses json-error-responses | Fail | 0 of 4 | API does not return JSON error responses (or no API detected) |
At the door
What the site answers when a request arrives with an agent's user agent, and what robots.txt says to agents.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Not blocked by bot detection bot-detection | Pass | 2 of 2 | Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot). |
| Agent crawler reachability agent-crawler-reachability | Pass | 2 of 2 | Reachable to every agent we tested - ChatGPT-User: reachable, OAI-SearchBot: reachable, Claude-User: reachable, PerplexityBot: reachable |
| robots.txt AI crawler policy robots-ai-policy-quality | Pass | 2 of 2 | 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. |
| robots.txt agent-user policy robots-agent-user-policy | Pass | 2 of 2 | No applicable crawl or usage restriction found for 3 user-triggered agents (chatgpt-user, claude-user, perplexity-user) on 1 public page: https://checkout.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (5 with substantive content) |
| Homepage not hidden from search noindex-directives | 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. |
| Redirect hygiene redirect-hygiene | Pass | 1 of 1 | no detail published |
| Web Bot Auth directory web-bot-auth-directory | Fail | 0 of 2 | No /.well-known/http-message-signatures-directory found |
What an agent can read
Whether the text is in the first response, what the site publishes for agents, and how it describes itself to them.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Pass | 3 of 3 | 10450 chars, semantic headings (1 H1 + 12 H2s + 21 H3s), 7.2% content ratio |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~9K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.checkout.com/sitemap.xml with 1541 entries |
| Sitemap freshness (lastmod) sitemap-lastmod | Pass | 1 of 1 | no detail published |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://checkout.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 157,293 characters it exceeds the 30,000-character recommendation for a navigation index. |
| llms.txt links resolve llms-txt-links-resolve | Pass | 2 of 2 | no detail published |
| Markdown agent docs markdown-negotiation | Pass | 1 of 1 | Returns markdown when requested via Accept header |
| Markdown URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://checkout.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| Bot-UA markdown serving agent-ua-markdown | 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 mode view agent-mode-view | Fail | 0 of 2 | ?mode=agent returns same content as homepage (no dedicated agent view) |
| JSON-LD structured data json-ld | Pass | 4 of 4 | Rich JSON-LD identity: Organization with name, description, url, and sameAs/logo/address (1 block(s)) |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 1 of 2 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Schema type breadth schema-type-breadth | Fail | 0 of 2 | No extended schema types found - AI can only answer basic questions about this entity |
| Metadata completeness metadata-completeness | Pass | 2 of 2 | All metadata signals present: canonical URL, lang="en", og:image, og:type |
| Agent instruction / when-to-use agent-instruction | Pass | 3 of 3 | no detail published |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | checkout.com ranks #3 for "checkout payment processing" (search term updated) |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "Checkout.com" and Wikidata Q110815500 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Fail | 0 of 1 | No bi-directionally verified MCP registry entry found. To pass, either publish the server from a package whose homepage, repository or maintainer email names your domain, get a verified Smithery listing with non-zero usage, |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Fail | 0 of 2 | Not found in ChatGPT app directory |
| Registry branding registry-branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| Listed on skills.sh skills-sh-listed | 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) |
| ARD discovery ard-catalog | Fail | 0 of 1 | No /.well-known/ard.json (and no legacy /.well-known/ai-catalog.json) |
Payments
The agent payment protocols Ora probes for. A site that sells nothing has nothing here, and Ora scores the layer out of zero when none applies.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| UCP - Universal Commerce Protocol ucp-support | Partial | 0 of 3 | text mentions (universal commerce protocol, agentic checkout) but no /.well-known/ucp profile or commerce metadata |
| ACP - Agentic Commerce Protocol acp-support | Partial | 0 of 3 | text mentions (agentic commerce protocol) but no reachable /checkout_sessions endpoint or supporting artifact |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | No ACP Delegate Payment signals detected |
| AP2 - Agent Payments Protocol ap2-support | Partial | 0 of 3 | No AP2 (Agent Payments Protocol) signals detected |
| x402 payment protocol x402-support | Partial | 0 of 2 | No x402 payment protocol support detected |
| MPP payment protocol mpp-support | Partial | 0 of 2 | No MPP (Machine Payments Protocol) support detected |
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 Checkout.com, with what Ora observed. The wording of each fix is Ora's; the 28 checks it runs on an MCP server are listed with their layer and tier.
- OpenAPI spec published: fail, 0 of 7, about 3.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
- Scoped permissions: fail, 0 of 5, about 3.5 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
- WebMCP support: fail, 0 of 5, about 3.5 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
- JSON error responses: fail, 0 of 4, about 2.8 points to gain. Ora saw: API does not return JSON error responses (or no API detected)
- CLI tool available: fail, 0 of 3, about 2.1 points to gain. Ora saw: No CLI tool found
Our read
Checkout.com, the payment processor and not the checkout page of a shop, has a home page worth copying and an act layer worth finishing. The page gives 10,450 characters at a 7.2 percent text ratio with one H1, twelve H2s and twenty-one H3s under a complete Organization block, the site returns markdown when an agent asks for it and checkout.com serves an llms.txt. The MCP server at support.checkout.com/mcp answers and requires authentication, OAuth authorization server metadata sits beside it at /mcp/oauth, the REST documentation scores 7 of 7 and SDKs are in npm, Go and rubygems. Ora found no OpenAPI specification and no declared scopes, about 7 points, endpoints that do not answer errors as JSON, and no CLI. The brand search was run on a common word and placed the domain third. A processor whose customers integrate it by API should publish the file that describes the API.
Test your own surfaces
The scan above is free and needs no account: enter a domain at ora.ai and read the same four layers for your own site. For an MCP server, Ora scans the server URL itself and runs 28 of its 132 public checks on it, which is why it is the check this directory recommends; the reasons, the limits and the alternatives are on their own 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.
npx ax@0.10 audit https://example.com --min-score 70All 360 checks, one company a day. Corrections to the corrections page.