Skip to content
Is Agentic

eve.dev

Important blockers remain

66/ 100

Technical readiness score

What should the prompt cover?

19 findings · 5 selected

Failures (9)

Warnings (10)

How the score adds up

33 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…

Critical access needs attention

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.

    1 / 2 passed

  • Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    1 / 2 passed

  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    2 / 2 passed

Advertised capabilities have material gaps

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

Public website

Needs work

57%

8 of 20 mature checks passed

API

Needs work

52%

4 of 9 mature checks passed

Authentication

Strong

87%

2 of 3 mature checks passed

MCP

Blocked

33%

0 of 1 mature checks passed

Fix these gaps first

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

  1. 01

    Agent-friendly 404s

    Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with `curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist` - it must print 404.

    Critical access
  2. 02

    Content without JavaScript

    Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

    Critical access
  3. 03

    OpenAPI spec published

    Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.

    Advertised capabilities
  4. 04

    JSON error responses

    Return structured JSON error responses with error codes, messages, and resolution hints. Agents can't parse HTML error pages.

    Advertised capabilities
  5. 05

    Markdown content negotiation (acceptmarkdown.com)

    On the responses that serve text/markdown via Accept negotiation, add Accept to the Vary header (Vary: Accept, Accept-Encoding). Without it, CDNs can serve the cached HTML variant to an agent asking for markdown (or vice versa), depending on which variant landed in cache first.

    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.

Essential6 of 12 passed · 51.8 / 80 points
  • Content without JavaScriptPartial (67%)
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • Content behind authPassed
  • OpenAPI spec publishedFailed
  • Markdown content negotiation (acceptmarkdown.com)Failed
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPartial (60%)
  • Scoped permissionsPassed
  • JSON error responsesFailed
  • Agent-friendly 404sPartial (50%)
Recommended8 of 21 passed · 10.6 / 20 points
  • Developer resource discoverabilityPartial (17%)
  • Brand name discoverabilityFailed
  • robots.txt AI crawler policyPartial (50%)
  • Sitemap existsPassed
  • Content efficiencyPartial (50%)
  • JSON-LD structured dataFailed
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-useFailed
  • Metadata completenessPartial (50%)
  • Organization schema completenessFailed
  • Trust anchor pagesPartial (50%)
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • MCP server / manifestPartial (33%)
  • CLI tool availablePassed
  • Multi-language SDK packagesPartial (67%)
  • API schema complexity analysisFailed
  • Function calling compatibilityFailed
Bonus signals13 positive · +3.3 points
  • NPM/PyPI SDK packagePassed
  • Agent platform configsPassed
  • Agent discovery filePassed
  • Modular llms.txt per product areaPassed
  • llms.txt existsPassed
  • llms.txt formattingPassed
  • llms.txt links resolvePassed
  • Markdown alternate linkPassed
  • Markdown agent docsPassed
  • Sandbox / test environmentPassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Accessibility-tree injection safety (bonus)Passed

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 eve.dev.

Source: Ora API

Snapshot 2026-08-20T18-47-55-897Z