Skip to content
Is Agentic

planetscale.com

Strong technical baseline

87/ 100

Technical readiness score

What should the prompt cover?

10 findings · 5 selected

Failures (3)

Warnings (7)

How the score adds up

32 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.

    2 / 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.

    3 / 3 passed

Advertised capabilities have material gaps

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

Public website

Strong

88%

15 of 19 mature checks passed

API

Needs work

60%

4 of 9 mature checks passed

Authentication

Strong

100%

3 of 3 mature checks passed

MCP

Needs work

67%

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

    JSON error responses

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

    Advertised capabilities
  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

    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
  5. 05

    Function calling compatibility

    Ensure API endpoints have unique operation IDs, typed schemas, and descriptions compatible with LLM function-calling formats.

    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.

Essential8 of 11 passed · 67 / 80 points
  • Content without JavaScriptPassed
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • Content behind authPassed
  • OpenAPI spec publishedPartial (71%)
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPassed
  • Scoped permissionsPassed
  • JSON error responsesFailed
  • Agent-friendly 404sPartial (50%)
Recommended14 of 21 passed · 15.8 / 20 points
  • Developer resource discoverabilityPassed
  • Brand name discoverabilityPassed
  • robots.txt AI crawler policyPartial (50%)
  • Sitemap existsPassed
  • Content efficiencyPassed
  • JSON-LD structured dataPartial (25%)
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-usePassed
  • Metadata completenessPassed
  • Organization schema completenessPartial (50%)
  • Trust anchor pagesPassed
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • MCP server / manifestPartial (67%)
  • CLI tool availablePartial (67%)
  • Multi-language SDK packagesPassed
  • API schema complexity analysisFailed
  • Function calling compatibilityFailed
Bonus signals20 positive · +4.5 points
  • NPM/PyPI SDK packagePassed
  • Listed on skills.shPassed
  • pricing.md existsPassed
  • MCP well-known discoveryPassed
  • HTTP Link headers (RFC 8288)Passed
  • Sitemap freshness (lastmod)Passed
  • llms.txt existsPassed
  • llms.txt formattingPartial (50%)
  • Skills.sh skill qualityPassed
  • llms.txt links resolvePassed
  • Markdown frontmatter metadataPassed
  • API catalog (RFC 9727)Partial (50%)
  • Markdown agent docsPassed
  • Markdown content negotiation (acceptmarkdown.com)Passed
  • WebMCP supportPartial (50%)
  • MCP server-card.jsonPartial (50%)
  • Accessible document structurePassed
  • 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 planetscale.com.

Source: Ora API

Snapshot 2026-08-15T06-01-48-389+00-00