Skip to content
Is Agentic

conductor.build

Ready with a few material gaps

80/ 100

Technical readiness score

What should the prompt cover?

19 findings · 5 selected

Failures (7)

Warnings (12)

How the score adds up

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

    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

Ready with gaps

72%

10 of 20 mature checks passed

API

Needs work

52%

4 of 9 mature checks passed

Authentication

Ready with gaps

70%

1 of 3 mature checks passed

MCP

Blocked

17%

0 of 2 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

    Scoped permissions

    Support scoped API permissions (OAuth scopes or API key roles) so agents can request only the access they need.

    Advertised capabilities
  5. 05

    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

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.

Essential7 of 11 passed · 63.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
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPassed
  • Scoped permissionsPartial (60%)
  • JSON error responsesPassed
  • Agent-friendly 404sPartial (50%)
Recommended8 of 23 passed · 11 / 20 points
  • Developer resource discoverabilityPassed
  • Brand name discoverabilityFailed
  • robots.txt AI crawler policyPartial (50%)
  • Sitemap existsPassed
  • Content efficiencyPartial (50%)
  • Content crawl depth signalsFailed
  • JSON-LD structured dataPassed
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-usePartial (67%)
  • Metadata completenessPartial (50%)
  • Organization schema completenessPartial (50%)
  • Trust anchor pagesPartial (50%)
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPartial (50%)
  • MCP server / manifestPartial (33%)
  • CLI tool availableFailed
  • Multi-language SDK packagesPartial (67%)
  • MCP Apps supportFailed
  • API schema complexity analysisFailed
  • Function calling compatibilityFailed
Bonus signals22 positive · +5 points
  • NPM/PyPI SDK packagePassed
  • Listed on skills.shPassed
  • ChatGPT app listedPassed
  • Agent discovery filePassed
  • Agent Skills index conformance (v0.2.0)Passed
  • pricing.md existsPartial (50%)
  • HTTP Link headers (RFC 8288)Passed
  • Markdown URL fallbackPassed
  • Sitemap freshness (lastmod)Passed
  • llms.txt existsPassed
  • llms.txt formattingPassed
  • Skills.sh skill qualityPartial (50%)
  • Schema type breadthPartial (50%)
  • llms.txt links resolvePassed
  • Markdown frontmatter metadataPassed
  • API catalog (RFC 9727)Passed
  • Markdown agent docsPassed
  • Markdown content negotiation (acceptmarkdown.com)Passed
  • 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 conductor.build.

Source: Ora API

Snapshot 2026-08-19T21-27-39-857+00-00