Revolut: the 360 agent-readiness check
Revolut scores 23 of 100 on Ora's agent-readiness scan, an F, read 12 November 2026. Of the five surfaces an agent acts on, Ora found 2: OAuth, a command line. An OAuth server at auth.revolut.com, a WAF at the front, and no MCP server.
On 12 November 2026 the public site at revolut.com scored 23 of 100 on Ora's agent-readiness scan, an F, 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: Turns agents away at the door: bot detection blocks them and there is no public API, MCP server or OpenAPI spec.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 11 of 48 | 23% |
| Access | Can agents read it | 1.5 of 39 | 4% |
| Discovery | Can agents find and recommend it | 6 of 12 | 50% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade F | 23 of 100 | 23% |
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. 3 checks in this group do not apply to this site and are left out.
Revolut is not in the directory's edition of 4 November 2026: no source read for that run named an MCP endpoint for revolut.com, so the MCP evidence here is Ora's alone. Its MCP server check reads fail.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| MCP server / manifest mcp-server | Fail | 0 of 10 | No MCP server or manifest found |
| MCP well-known discovery mcp-well-known-discovery | Fail | 0 of 2 | No MCP server URL discovered |
| Public API with reachable endpoints public-api | Fail | 0 of 8 | No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated) |
| Public API/docs linked from homepage public-api-docs | Partial | 0 of 4 | Homepage blocked by WAF - cannot check for docs links |
| Developer portal developer-portal | Fail | 0 of 5 | No developer portal found |
| OpenAPI spec published openapi-spec | Fail | 0 of 8 | 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://auth.revolut.com (issuer=https://auth.revolut.com) |
| auth.md exists auth-md-exists | Fail | 0 of 2 | No /auth.md found at site root |
| WebMCP support webmcp | Fail | 0 of 8 | No WebMCP support detected - no document.modelContext / navigator.modelContext usage found |
| NLWeb /ask endpoint nlweb-ask | Pass | 1 of 1 | NLWeb /ask endpoint exists but requires authentication (HTTP 403, via GET) |
| CLI tool available cli-tool | Pass | 3 of 3 | CLI package found on npm: @revolut/cra-overrides |
| JSON error responses json-error-responses | Pass | 3 of 3 | 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. 5 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| robots.txt AI crawler policy robots-ai-policy-quality | 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. |
| robots.txt agent-user policy robots-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://revolut.com/. Declared policy only; |
| 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. 3 checks in this group do not apply to this site and are left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Content without JavaScript content-no-js | Partial | 0 of 5 | Homepage blocked by WAF/security challenge - content not accessible to agents |
| Sitemap exists sitemap | Fail | 0 of 1 | No sitemap found |
| llms.txt exists llms-txt-exists | Fail | 0 of 1 | No llms.txt found at https://revolut.com/llms.txt. Publish it at the site root, where agents that follow the llms.txt spec look for it. |
| llms.txt formatting llms-txt-formatting | Fail | 0 of 2 | No llms.txt found to evaluate quality |
| 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://revolut.com/index.md and it did not return markdown (expected text/markdown content-type or a heading-led non-HTML body). |
| JSON-LD structured data json-ld | Partial | 0 of 2 | Homepage blocked by WAF - cannot check structured data |
| Organization schema completeness org-schema-completeness | Partial | 0 of 1 | Homepage blocked by WAF - cannot check Organization schema |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 0 of 1 | Homepage blocked by WAF - cannot check entity linking |
| Metadata completeness metadata-completeness | Partial | 0 of 1 | Homepage blocked by WAF - cannot check metadata |
| Agent instruction / when-to-use agent-instruction | Fail | 0 of 1 | No agent instruction file with when-to-use guidance found |
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 | 2 of 3 | revolut.com ranks #6 for "revolut payments fintech" and appears 4 times in the top 10 |
| Developer resource discoverability agentic-search-specific | Fail | 0 of 4 | In a search for your API docs, none of the 10 results is your official docs |
| NPM/PyPI SDK package npm-sdk-package | Pass | 1 of 1 | no detail published |
| ChatGPT app listed chatgpt-app-listed | Pass | 2 of 2 | no detail published |
| Listed on skills.sh skills-sh-listed | Pass | 1 of 1 | no detail published |
| 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. None of the 6 payment checks applied to revolut.com.
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 Revolut, 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.
- MCP server / manifest: fail, 0 of 10, about 9.3 points to gain. Ora saw: No MCP server or manifest found
- Developer resource discoverability: fail, 0 of 4, about 7.4 points to gain. Ora saw: In a search for your API docs, none of the 10 results is your official docs
- Public API with reachable endpoints: fail, 0 of 8, about 7.4 points to gain. Ora saw: No publicly reachable API surface detected (REST and GraphQL both absent or auth-gated)
- WebMCP support: fail, 0 of 8, about 7.4 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
- OpenAPI spec published: fail, 0 of 8, about 6.8 points to gain. Ora saw: No OpenAPI/Swagger specification found
Our read
Revolut gives an agent almost nothing to act on. Ora found neither an MCP server nor a public API, since REST and GraphQL were both absent or behind authentication, and there is neither an OpenAPI specification nor a developer portal, and no WebMCP or declared OAuth scopes. What does answer is an OAuth authorization server at auth.revolut.com, and the one CLI Ora found is an npm package, @revolut/cra-overrides. Usability reads 11 of 48. The door is harder to judge: robots.txt allows the AI search crawlers in 3 of 3 checks and restricts none of the user-triggered agents, but a WAF challenged the home page itself, so the agent tests, structured data, metadata and docs links are unverified rather than failed. Access reads 1.5 of 39, with neither a sitemap nor an llms.txt to fall back on. The fix worth most is an MCP server, about 9.3 points. An F at 23: the authorization server is already up, and nothing public behind it takes a call.
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.