Miro: the 360 agent-readiness check
Miro scores 74 of 100 on Ora's agent-readiness scan, a B, read 9 November 2026. Of the five surfaces an agent acts on, Ora found 3: a public API, OAuth, a command line. A live server behind a shield, and a 445-character home page in front of it.
On 9 November 2026 the public site at miro.com scored 74 of 100 on Ora's agent-readiness scan, a B, in Ora's Productivity 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: Miro offers strong developer resource discoverability and SDK packages, but lacks WebMCP support for agent integration.
The score
| Layer | Asks | Points | Share |
|---|---|---|---|
| Usability | Can agents use it | 59 of 81 | 73% |
| Access | Can agents read it | 33 of 46 | 72% |
| Discovery | Can agents find and recommend it | 13 of 16 | 81% |
| Payments | Can agents pay | 0 of 0 | none apply |
| Total | Grade B | 74 of 100 | 74% |
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.
In the directory, Miro 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://mcp.miro.com; 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.miro.com - 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 /api. GraphQL endpoint at https://api.miro.com/v1/graphql is reachable; introspection requires authentication (API key / OAuth), which is expected for agent access. |
| Public API/docs linked from homepage public-api-docs | Pass | 3 of 3 | Documentation site found at https://developers.miro.com |
| Developer portal developer-portal | Pass | 6 of 6 | Developer documentation portal found at https://developers.miro.com |
| API catalog (RFC 9727) api-catalog-rfc9727 | Fail | 0 of 2 | No /.well-known/api-catalog found (RFC 9727) |
| OAuth 2.0 support oauth-support | Pass | 5 of 5 | OAuth authorization server metadata at https://mcp.miro.com/ |
| 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 | Pass | 3 of 3 | CLI package found on npm: create-miro-app |
| Multi-language SDK packages rest-sdk-packages | Partial | 1 of 3 | SDK package found only in npm |
| Rate limit response headers rate-limit-headers | Partial | 1 of 2 | The live API at https://miro.com/api returns legacy x-ratelimit-limit, x-ratelimit-remaining, x-ratelimit-reset headers. Adopting the IETF RateLimit-* standard would earn full credit. |
| Idempotency-Key support idempotency-key-support | Fail | 0 of 3 | GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages |
| 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. One check in this group does not apply to this site and is left out.
| 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://miro.com/. Declared policy only; |
| Content behind auth docs-auth-gate | Pass | 2 of 2 | All 5 sampled pages are publicly readable (0 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 |
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. 2 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 | 1 of 3 | Homepage: Only 445 chars of text content - agents see limited content. No inner pages checked: the 5 sampled pages were skipped (forms, login pages, bot challenges, error pages, |
| Page token budget page-token-budget | Pass | 1 of 1 | All 1 measured page fit an agent context budget (largest ~1K tokens) |
| Sitemap exists sitemap | Pass | 2 of 2 | Valid sitemap found at https://miro.com/sitemap.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://developers.miro.com/llms.txt. |
| llms.txt formatting llms-txt-formatting | Partial | 1 of 2 | The llms.txt is well-formatted with markdown links, but at 95,346 characters it exceeds the 30,000-character recommendation for a navigation index. |
| 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://miro.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 | Pass | 2 of 2 | no detail published |
| JSON-LD structured data json-ld | Fail | 0 of 4 | No JSON-LD structured data found on homepage |
| Organization schema completeness org-schema-completeness | Fail | 0 of 2 | No JSON-LD found - Organization schema missing |
| JSON-LD entity linking (sameAs) json-ld-entity-linking | Fail | 0 of 2 | No JSON-LD found - no entity linking possible |
| 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 |
Found and recommended
Whether an assistant can find the company by name, confirm what it is, and see it in the registries agents read. One check in this group does not apply to this site and is left out.
| Check | Result | Points | What Ora saw |
|---|---|---|---|
| Brand name discoverability brand-search-accuracy | Partial | 1 of 3 | miro.com ranks #8 for "AI Innovation Workspace visual collaboration" |
| Wikipedia / Wikidata entity presence wikipedia-presence | Partial | 2 of 4 | Wikidata Q94126521 (Miro) verified - draft a Wikipedia page with cited references to complete knowledge graph coverage |
| Developer resource discoverability agentic-search-specific | Pass | 3 of 3 | no detail published |
| Listed in MCP registries mcp-registry-listed | Pass | 1 of 1 | no detail published |
| 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 miro.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 Miro, 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.
- JSON-LD structured data: fail, 0 of 4, about 2.9 points to gain. Ora saw: No JSON-LD structured data found on homepage
- Brand name discoverability: partial, 1 of 3, about 2.8 points to gain. Ora saw: miro.com ranks #8 for "AI Innovation Workspace visual collaboration"
- WebMCP support: fail, 0 of 5, about 2.7 points to gain. Ora saw: No WebMCP support detected - no document.modelContext / navigator.modelContext usage found
- GraphQL typed error model: fail, 0 of 3, about 1.6 points to gain. Ora saw: GraphQL introspection auth-gated and no typed graphql error model documentation found on GraphQL-tagged pages
- Idempotency-Key support: fail, 0 of 3, about 1.6 points to gain. Ora saw: GraphQL introspection auth-gated and no idempotency documentation found on GraphQL-tagged pages
Our read
Miro's read is divided by a shield. The MCP server at mcp.miro.com answers and requires authentication, with OAuth authorization server metadata on the same host; the REST documentation at developers.miro.com carries an llms.txt, the GraphQL endpoint at api.miro.com is reachable, create-miro-app is on npm and the site returns markdown when an agent asks for it. Three probes were answered 403 by a bot shield, the OpenAPI specification, the A2A agent card and the agent skills index, so those rows are unverified and the Access layer's maximum shrinks to 46. What Ora could confirm against the site is on the reading side: a home page of 445 characters without JavaScript, no inner page that could be sampled, no JSON-LD, and a brand search that places the domain eighth for a term Ora read off the page. A board every agent will be asked to draw on; the page an agent lands on is almost empty.
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.