Adyen: the 360 agent-readiness check
Adyen scores 71 of 100 on Ora's agent-readiness scan, a B, read 10 November 2026. Of the five surfaces an agent acts on, Ora found 2: OAuth, a command line. An MCP package on npm, OpenID Connect at sso.adyen.com, and no specification file yet.
On 10 November 2026 the public site at adyen.com scored 71 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: Adyen offers strong developer documentation and SDK packages, but lacks a published OpenAPI specification and declared OAuth scopes for agents.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 38 of 56 | 68% |
| Access | Can agents read it | 41 of 59 | 69% |
| Discovery | Can agents find and recommend it | 12 of 15 | 80% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 71 of 100 | 71% |
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.
Adyen is not in the directory's edition of 4 November 2026: no source read for that run named an MCP endpoint for adyen.com, so the MCP evidence here is Ora's alone. Its MCP server check reads partial.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Partial | 5 of 6 | First-party MCP server published by product org (npm, @adyen/mcp, 14767 score). Add live handshake at /.well-known/mcp for full credit. |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Partial | 3 of 7 | API described in documentation at https://docs.adyen.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://docs.adyen.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer documentation portal found at https://docs.adyen.com |
| 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 | OpenID Connect discovery endpoint found at https://sso.adyen.com |
| OAuth Protected Resource metadata (RFC 9728) oauth-protected-resource | Fail | 0 of 2 | No /.well-known/oauth-protected-resource found (RFC 9728) |
| 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 (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations) |
| NLWeb /ask endpoint nlweb-ask | Fail | 0 of 1 | No NLWeb-conformant /ask endpoint found via GET or POST |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: @adyen/adyen-salesforce-pwa |
| Multi-language SDK packages rest-sdk-packages | Pass | 3 of 3 | SDK packages found across 3 ecosystems: npm, pypi, rubygems |
| JSON error responses json-error-responses | Pass | 4 of 4 | no detail published |
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://adyen.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 | Partial | 2 of 3 | Homepage: 3230 chars with H1, but 2.2% content ratio is below the 5% target. 2 of 2 sampled inner pages have text without JavaScript (3 skipped). |
| Page token budget page-token-budget | Pass | 1 of 1 | All 6 measured pages fit an agent context budget (largest ~7K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://www.adyen.com/sitemap_index.xml with multiple sitemaps 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://docs.adyen.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt at https://adyen.com/llms.txt is well-formatted with markdown links, but at 591,195 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 | 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 URL fallback markdown-url-fallback | Fail | 0 of 2 | Homepage does not support the .md suffix. Probed https://adyen.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 | Partial | 2 of 4 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness org-schema-completeness | Partial | 1 of 2 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Pass | 2 of 2 | no detail published |
| 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 | Partial | 1 of 2 | 3/4 metadata signals present - missing: og:type |
| Agent instruction / when-to-use agent-instruction | Partial | 2 of 3 | When-to-use guidance found at https://docs.adyen.com |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. 2 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | adyen.com ranks #9 for "Adyen payment processing" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Pass | 4 of 4 | Wikipedia "Adyen" and Wikidata Q4686934 both verified - domain confirmed on both sources |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| 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 |
| Listed on skills.sh skills-sh-listed | Fail | 0 of 1 | No official skills self-published on skills.sh (42 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, no same-site rel="ard" link, 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 (checkout-sessions) but no /.well-known/ucp profile or commerce metadata |
| ACP - Agentic Commerce Protocol acp-support | Partial | 0 of 3 | no ACP (Agentic Commerce Protocol) signals detected |
| ACP delegate payment acp-delegate-payment | Partial | 0 of 3 | Delegate Payment text signals (delegated payment); no reachable /agentic_commerce/delegate_payment endpoint on https://adyen.com or https://api.adyen.com |
| 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 | x402 referenced in docs (x402, facilitator) |
| 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 Adyen, 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 4 points to gain. Ora saw: No OpenAPI/Swagger specification found
- Scoped permissions: fail, 0 of 5, about 4 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
- WebMCP support: fail, 0 of 5, about 4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found (scanned 2 of 2 same-origin script bundle(s) for modelContext registrations)
- Public API with reachable endpoints: partial, 3 of 7, about 3.2 points to gain. Ora saw: API described in documentation at https://docs.adyen.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7.
- Brand name discoverability: partial, 1 of 3, about 3 points to gain. Ora saw: adyen.com ranks #9 for "Adyen payment processing"
Our read
Adyen's act layer is nearly whole and oddly unfinished. Ora found a first-party MCP server published on npm as @adyen/mcp, but no live handshake at /.well-known/mcp, so the check scores partial credit; an OpenID Connect discovery endpoint answers at sso.adyen.com; the API is described at docs.adyen.com without a machine-verifiable surface, 3 of 7; a CLI package and SDKs on npm, PyPI and RubyGems are there. What is missing is the paperwork: neither an OpenAPI specification nor declared OAuth scopes, each worth about 4 points, and no WebMCP in the 2 script bundles read. The door is open to all four test agents, with robots.txt allowing every AI crawler checked. The reading layer has an llms.txt at docs.adyen.com, well formed and 591,195 characters long against a 30,000-character recommendation, a home page at 2.2 percent text, and an Organization block without a description. A B at 71: the server is published, the specification that would let an agent trust it is not.
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.