Skip to content
Is Agentic

worldmonitor.app

Strong technical baseline

100/ 100

Technical readiness score

What should the prompt cover?

5 findings · 5 selected

Warnings (5)

How the score adds up

45 checks

Starting an observed agent task

This run is collected separately from the technical score and will appear here as the agent moves through the public site.

Starting the agent…

Agents can access the public site

These checks describe whether an ordinary agent can enter, read, and operate the public site.

  • Agents can reach the site

    Crawler access, bot defenses, and explicit agent policy.

    3 / 3 passed

  • Core content is available

    Useful content remains accessible without a fragile browser-only path.

    2 / 2 passed

  • Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    2 / 2 passed

  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    3 / 3 passed

Advertised capabilities are technically strong

Optional surfaces appear only when the scan finds positive evidence that the site offers them.

Public website

Strong

95%

18 of 20 mature checks passed

API

Strong

93%

13 of 16 mature checks passed

Authentication

Strong

100%

3 of 3 mature checks passed

MCP

Strong

100%

6 of 6 mature checks passed

Fix these gaps first

Critical access gaps come first, followed by gaps in capabilities the site advertises.

  1. 01

    Brand name discoverability

    Make sure a clean search for your brand name returns your own domain in the top results. If it does not, your brand may be too generic, conflict with a more established term, or not yet indexed. Strengthen brand-name search by claiming consistent NAP across listings, earning press mentions that link to the canonical domain, and avoiding redirect chains that mask the apex domain in search results.

    Advertised capabilities
  2. 02

    API schema complexity analysis

    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.

    Advertised capabilities
  3. 03

    REST versioning / deprecation policy

    Declare a versioning policy agents can rely on: version your API (in the URL path or a version header) and publish how you signal deprecation (a Sunset/Deprecation header or a documented timeline). Agents avoid integrating against a surface that can change without warning.

    Advertised capabilities
  4. 04

    Developer resource discoverability

    Make your developer resources (API docs, OpenAPI spec, auth docs, webhooks, MCP server) discoverable by name. Publish them at predictable URLs, list them in llms.txt, and include your product name in page titles and headings so search engines surface them for name-based queries.

    Advertised capabilities
  5. 05

    Multi-language SDK packages

    Publish official SDK packages across multiple language ecosystems (npm, PyPI, Go modules, RubyGems). Auto-generate them from your OpenAPI spec using tools like openapi-generator. For each package set the project URL or homepage to your product domain (package.json `repository`/`homepage`, PyPI `Home-Page` or `project_urls`, RubyGems `homepage_uri`) - this is how agents verify the package is your official SDK.

    Advertised capabilities

Audit the checks behind the score

Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.

Essential14 of 14 passed · 80 / 80 points
  • Content without JavaScriptPassed
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • Content behind authPassed
  • OpenAPI spec publishedPassed
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPassed
  • Scoped permissionsPassed
  • JSON error responsesPassed
  • MCP resources exposedPassed
  • Agent-friendly 404sPassed
  • MCP App view reachablePassed
  • MCP App view CSPPassed
Recommended26 of 31 passed · 18.6 / 20 points
  • Developer resource discoverabilityPartial (67%)
  • Brand name discoverabilityPartial (33%)
  • robots.txt AI crawler policyPassed
  • Sitemap existsPassed
  • Content efficiencyPassed
  • Content crawl depth signalsPassed
  • JSON-LD structured dataPassed
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-usePassed
  • Metadata completenessPassed
  • Organization schema completenessPassed
  • Trust anchor pagesPassed
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • MCP server / manifestPassed
  • Rate limit response headersPassed
  • Idempotency-Key supportPassed
  • REST typed error modelPassed
  • REST versioning / deprecation policyPartial (67%)
  • REST pagination patternPassed
  • REST async-job patternPassed
  • CLI tool availablePassed
  • Multi-language SDK packagesPartial (67%)
  • REST response schema coveragePassed
  • MCP Apps supportPassed
  • API schema complexity analysisPartial (50%)
  • Function calling compatibilityPassed
  • MCP resource qualityPassed
Bonus signals58 positive · +5 points
  • ARD / ai-catalogPassed
  • ARD entry validityPassed
  • ARD trust manifestPassed
  • Listed in MCP registriesPassed
  • NPM/PyPI SDK packagePassed
  • Agent platform configsPassed
  • Listed on skills.shPassed
  • Registry brandingPassed
  • Agent discovery filePassed
  • Agent Skills index conformance (v0.2.0)Passed
  • A2A / agent-cardPassed
  • pricing.md existsPassed
  • MCP well-known discoveryPassed
  • Agent mode viewPartial (50%)
  • HTTP Link headers (RFC 8288)Passed
  • Markdown URL fallbackPassed
  • Modular llms.txt per product areaPassed
  • Sitemap freshness (lastmod)Passed
  • llms.txt existsPassed
  • llms.txt formattingPassed
  • Skills.sh skill qualityPassed
  • JSON-LD entity linking (sameAs)Partial (50%)
  • Speakable content markupPassed
  • Schema type breadthPassed
  • llms.txt links resolvePassed
  • API catalog (RFC 9727)Passed
  • Markdown agent docsPassed
  • Markdown content negotiation (acceptmarkdown.com)Passed
  • MCP tool descriptionsPassed
  • MCP parameter schemasPassed
  • MCP server identityPassed
  • MCP tool listingPassed
  • MCP tool namingPassed
  • MCP auth mechanismPassed
  • Web Bot Auth directoryPassed
  • OAuth Protected Resource metadata (RFC 9728)Passed
  • auth.md existsPassed
  • auth.md structurePassed
  • auth.md walkthrough simulationPassed
  • Agent auth discovery metadataPassed
  • Agent auth WWW-Authenticate hintPassed
  • agent_auth endpoints reachablePassed
  • MCP error handlingPassed
  • MCP modern transportPassed
  • WebMCP supportPassed
  • NLWeb /ask endpointPassed
  • NLWeb streaming supportPassed
  • MCP tool annotationsPassed
  • MCP server-card.jsonPassed
  • Product + docs MCP coveragePassed
  • Sandbox / test environmentPassed
  • REST batch / bulk endpointPassed
  • Accessible document structurePassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Accessibility-tree injection safety (bonus)Passed
  • A2UI / generative UI supportPassed
  • MCP Apps UI qualityPassed

Inspect the underlying audit

The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.

Score alerts

A weekly report with ranking changes, new agent feedback, and score alerts for worldmonitor.app.

Source: Ora API

Snapshot 2026-08-20T12-14-04-403Z