www.adyen.com/pt_BR
Finalizing the report
Preparing the stored Is Agentic score
www.adyen.com/pt_BR
Preparing the stored Is Agentic score
www.adyen.com/pt_BR
These checks describe whether an ordinary agent can enter, read, and operate the public site.
Agents can reach the site
Crawler access and bot defenses.
Core content is available
Useful content remains accessible without a fragile browser-only path.
Navigation fails safely
Redirects and missing pages give agents a recoverable path.
Controls are understandable
Forms and interactive controls expose usable names and structure.
The public website is always evaluated. Optional surfaces appear when the scan finds positive evidence that they apply.
Ready with gaps
Weighted across 17 applicable checks
Needs work
Weighted across 8 applicable checks
Needs work
Weighted across 3 applicable checks
Ready with gaps
Weighted across 1 applicable check
Critical access gaps come first, followed by other applicable readiness gaps.
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
Checks are grouped by relevance for App sites.
Homepage: 3230 chars with H1, but 2.2% content ratio is below the 5% target. 1 of 1 sampled inner page has text without JavaScript (4 skipped).
How to pass
Serve at least 500 characters of meaningful homepage content in raw HTML. Add a clear H1, keep deeper heading levels sequential, and remove excessive non-content markup. Inner pages need their main text in the raw HTML too, not only after JavaScript runs.
Site accessible to 4 agent user-agents (ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot).
No meta-refresh or JavaScript-redirect stubs across 27 checked pages
All 5 sampled pages are publicly readable (5 with substantive content)
No OpenAPI/Swagger specification found
How to pass
Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.
Homepage https://adyen.com does not meet the Markdown negotiation requirements: Accept: text/markdown returned text/html; charset=utf-8; Vary header missing Accept (got "accept-encoding")
How to pass
Enable Markdown negotiation on the scanned homepage. Supporting it only on /docs or a separate .md URL does not satisfy this check. Requests with Accept: text/markdown must receive a nonempty Markdown body with Content-Type: text/markdown and Vary: Accept. Keep serving HTML for Accept: text/html. Adding Vary alone does not create a Markdown response. Verify both with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/ and curl -sS -L -i -H 'Accept: text/html' https://yourdomain.com/. Check the final response headers and body: Markdown with Vary: Accept for the first request, HTML for the second.
OpenID Connect discovery endpoint found at https://sso.adyen.com
No declared OAuth scopes, security schemes, or scoped-permission documentation found
How to pass
Declare scoped API permissions where machines can read them: named OAuth scopes in your OpenAPI security schemes, or scopes_supported in RFC 9728 protected-resource metadata. Prose descriptions of roles help humans, but agents need the machine-readable declaration to request least-privilege access.
API returns JSON error responses (404 at https://www.adyen.com/orank-probe-test)
The nonexistent path https://adyen.com/__ora-404-probe-53npm4l7 correctly returns HTTP 404. Partial credit: no Markdown error body was detected.
How to pass
Keep the correct HTTP 404 status. The remaining requirement is a Markdown error body when agents request Accept: text/markdown. Include at least 20 characters explaining the error and a link to your docs, sitemap, or llms.txt. Verify with curl -sS -L -i -H 'Accept: text/markdown' https://yourdomain.com/some-path-that-does-not-exist. Check both the final 404 status and the Markdown body with Content-Type: text/markdown. Checking the status alone does not verify the missing requirement.
In a search for your API docs, your docs came up at #2 (https://docs.adyen.com/api-explorer). In a search for your MCP server, SDK or CLI, we found your MCP server at #3 (https://docs.adyen.com/development-resources/mcp-server)
adyen.com ranks #3 for "Adyen" (searched your brand name alone: no main product term from your homepage qualified)
No noindex on the homepage: no robots, googlebot or bingbot meta tag and no X-Robots-Tag header hides it from search.
Valid sitemap found at https://www.adyen.com/sitemap_index.xml with multiple sitemaps entries
JSON-LD Organization found - missing description on this entity
How to pass
Add description to the Organization JSON-LD entity for full score.
Pricing page found at /pricing
Documentation site found at https://docs.adyen.com
When-to-use guidance found in llms.txt
3/4 metadata signals present - missing: og:type
How to pass
Add all four signals to your homepage: <link rel="canonical"> pointing to the page on your own site, <html lang="...">, <meta property="og:image">, and <meta property="og:type">. Agents use these for entity resolution and attribution.
Organization schema found but missing: contactPoint, address
How to pass
Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress). This lets AI verify your business legitimacy and answer contact queries.
All trust anchor pages verified: About, Contact, Privacy
All 6 measured pages fit an agent context budget (largest ~7K tokens)
Code fences balanced across 1 markdown document
Developer portal found at https://docs.adyen.com
API described in documentation at https://docs.adyen.com but no machine-verifiable API surface confirmed. Best-of-protocols score: 3/7.
How to pass
Expose a public REST or GraphQL API. AI agents need programmatic access - not just a web UI - to integrate with your product.
Low friction onboarding verified live: free tier available, self-serve key generation, sandbox/test environment, zero-friction self-serve registration at /signup
First-party MCP server published by product org (npm, @adyen/mcp, 15093 score). Add live handshake at /.well-known/mcp for full credit.
How to pass
Build an MCP (Model Context Protocol) server exposing your API as tools. Use Streamable HTTP transport for full score. This lets Claude, ChatGPT, and other AI agents call your product natively.
CLI package found on npm: @adyen/adyen-salesforce-pwa
REST: OpenAPI spec found but failed to parse for complexity analysis
How to pass
Make your API spec self-describing: a unique operationId and a description on every operation, typed parameters, and response schemas. For GraphQL, a fully typed schema with a documented cost or rate limit reads best.
API spec found but couldn't validate function calling compatibility
How to pass
Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.
Wikipedia "Adyen" and Wikidata Q4686934 both verified - domain confirmed on both sources
NPM package found: @adyen/api-library - "The Adyen API Library for NodeJS enables you to work with Adyen APIs."
Rich agent mode view at ?mode=agent with 7 agent signals and navigation links
100% of 500 sampled sitemap entries carry lastmod; newest is 2 day(s) old
Found the llms.txt at https://docs.adyen.com/llms.txt.
The llms.txt at https://adyen.com/llms.txt is well-formatted with markdown links, but at 593,095 characters it exceeds the 30,000-character recommendation for a navigation index.
How to pass
Format your llms.txt as a navigation index: start with a markdown heading, include markdown links to deeper resources, and keep it under 30,000 characters. Agents truncate an llms.txt past 100,000 characters, so nothing after that point is read. If you have more to say, move long-form content into /llms-full.txt or per-section files (e.g. /docs/llms.txt, /api/llms.txt) and link to them from the main index.
Strong entity linking via sameAs: wikipedia.org, linkedin.com
All 5 probed llms.txt links resolve to real content
SDK packages found across 3 ecosystems: npm, pypi, rubygems
Server HTML is a well-structured document (main=true, landmarks=4/4, h1=1, maxHeadingSkip=1).
88 native controls, 0 non-native div-soup affordances (100% native).
88/88 interactive elements have a computable accessible name (100%).
No hidden instruction text detected in accessibility-tree attributes or off-screen content.
What does www.adyen.com do and who is it for? Explain it back to me.
Sign me up for Vercel product updates and marketing emails.
Unsubscribe anytime. Privacy Notice
Source: Ora API
What does www.adyen.com do and who is it for? Explain it back to me.
5 steps1 reasoning step1 search
The agent successfully assembled a comprehensive explanation of Adyen's business model, pricing, and market position by fetching the homepage, pricing page, and payments product page, then supplementing gaps with third-party comparison articles. The Adyen site itself provides clear high-level positioning but withholds specific pricing details and makes no direct competitor comparisons, forcing the agent to source external context.