Wise: the 360 agent-readiness check
Wise scores 77 of 100 on Ora's agent-readiness scan, a B, read 11 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. A live MCP server, a 7 of 7 API, and no declared OAuth scopes.
On 11 November 2026 the public site at wise.com scored 77 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: Wise offers a broad API, MCP server, and SDK packages, but lacks declared OAuth scopes and scoped-permission documentation for agents.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 35.33 of 50 | 71% |
| Access | Can agents read it | 37.04 of 45 | 82% |
| Discovery | Can agents find and recommend it | 11.67 of 14 | 83% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 77 of 100 | 77% |
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. 4 checks in this group do not apply to this site and are left out.
Wise is not in the directory's edition of 4 November 2026: no source read for that run named an MCP endpoint for wise.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 | 8.33 of 10 | MCP server detected at https://mcp.wise.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://mcp.wise.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 | 8 of 8 | REST API documentation found at https://docs.wise.com/guides/developer/language-support.md. Best-of-protocols score: 7/7. |
| Public API/docs linked from homepage public-api-docs | Pass | 4 of 4 | Documentation site found at https://docs.wise.com |
| Developer portal developer-portal | Pass | 5 of 5 | Developer documentation portal found at https://docs.wise.com |
| OpenAPI spec published openapi-spec | Partial | 5.71 of 8 | OpenAPI spec (YAML) found at https://docs.wise.com/_bundle/api-reference/@legacy/webhook/tmp/generated/openapi.yaml |
| 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 |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth endpoint found at https://wise.com/oauth/authorize |
| 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 |
| 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: @wise/wds-codemods |
| 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.
| 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 | 1 of 1 | 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 | 1 of 1 | AI search crawlers: allowed in 9 of 9 checks (3 crawlers on 3 pages). AI training crawlers: allowed in 6 of 6 checks (2 crawlers on 3 pages), 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://wise.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 1 of 1 | All 2 sampled pages are publicly readable (2 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 | 3.33 of 5 | Homepage: 6856 chars with H1, but heading hierarchy skips H1 to H5; 4.4% content ratio is below the 5% target. 2 of 2 sampled inner pages have text without JavaScript. |
| Page token budget page-token-budget | Pass | 1 of 1 | All 3 measured pages fit an agent context budget (largest ~2K tokens) |
| Sitemap exists sitemap | Pass | 1 of 1 | Valid sitemap found at https://wise.com/sitemap with multiple sitemaps entries |
| llms.txt exists llms-txt-exists | Pass | 1 of 1 | Found the llms.txt at https://docs.wise.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 40,865 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://wise.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. |
| JSON-LD structured data json-ld | Partial | 1 of 2 | JSON-LD Organization found - missing description on this entity |
| Organization schema completeness org-schema-completeness | Partial | 0.5 of 1 | Organization schema found but missing: contactPoint, address |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Partial | 0.5 of 1 | Entity linking to linkedin.com - add more authority profiles (Wikipedia, Wikidata, LinkedIn, GitHub) |
| Metadata completeness metadata-completeness | Pass | 1 of 1 | All metadata signals present: canonical URL, lang="en-GB", og:image, og:type |
| 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.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Pass | 3 of 3 | wise.com ranks #5 for "Wise" (searched your brand name alone: no main product term from your homepage qualified) |
| Developer resource discoverability agentic-search-specific | Partial | 2.67 of 4 | In a search for your API docs, your docs came up at #2 (https://docs.wise.com/guides/developer). In a search for your MCP server, SDK or CLI, none of the 10 results is your own, although the scan found one on your site |
| Listed in MCP registries mcp-registry-listed | 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 |
| Registry branding registry-branding | Fail | 0 of 2 | No registry branding (name, icon, description) found |
| 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 wise.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 Wise, 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.
- Scoped permissions: fail, 0 of 5, about 4.4 points to gain. Ora saw: No declared OAuth scopes, security schemes, or scoped-permission documentation found
- Developer resource discoverability: partial, 2.67 of 4, about 2.1 points to gain. Ora saw: In a search for your API docs, your docs came up at #2 (https://docs.wise.com/guides/developer). In a search for your MCP server, SDK or CLI, none of the 10 results is your own, although the scan found one on your site
- MCP OAuth metadata: fail, 0 of 2, about 1.8 points to gain. Ora saw: OAuth protected-resource metadata was found for https://mcp.wise.com/mcp, but its resource field identifies https://mcp.wise.com/. The resource must exactly match the requested endpoint (RFC 9728).
- MCP PKCE S256 support: fail, 0 of 2, about 1.8 points to gain. Ora saw: No code_challenge_methods_supported in OAuth metadata for product MCP
- OpenAPI spec published: partial, 5.71 of 8, about 1.7 points to gain. Ora saw: OpenAPI spec (YAML) found at https://docs.wise.com/_bundle/api-reference/@legacy/webhook/tmp/generated/openapi.yaml
Our read
Wise has built most of the act layer and tripped on the paperwork around it. Ora found an MCP server at mcp.wise.com/mcp that requires authentication and verifies at 5 of 6, an OAuth endpoint, a REST API scoring 7 of 7, a developer portal at docs.wise.com and an OpenAPI file that sits under a webhook path and scores 5.71 of 8. Declared OAuth scopes are missing, the largest gap at about 4.4 points; the server's protected-resource metadata names https://mcp.wise.com/ while the endpoint is /mcp, which RFC 9728 does not allow, and no PKCE S256 method is declared. The door is open: all four test agents got in, and robots.txt allowed the AI search crawlers in 9 of 9 checks. The llms.txt runs 40,865 characters against a 30,000 recommendation. The WebMCP and agent discovery rows are unverified rather than failed, since a bot shield answered with a 403. A B at 77, and the next points sit in a scopes list and one trailing slash.
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.