Skip to content
Is Agentic

jobspipe.dev

Strong technical baseline

100/ 100

Technical readiness score

What should the prompt cover?

3 findings · 3 selected

Warnings (3)

How the score adds up

43 checks

The agent completed the observed task

One run shows how an agent performed, but it does not determine the technical score.

Task

What does jobspipe.dev do and who is it for? Explain it back to me.

9 steps4 reasoning steps

home
/index.md
llms.txt
docs
.well-known
1 observed runView journey ↗

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.

    2 / 2 passed

  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    4 / 4 passed

Advertised capabilities are technically strong

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

Public website

Strong

94%

17 of 20 mature checks passed

API

Strong

100%

16 of 16 mature checks passed

Authentication

Strong

100%

3 of 3 mature checks passed

MCP

Strong

100%

3 of 3 mature checks passed

Commerce

Strong

100%

1 of 1 mature checks passed

Fix these gaps first

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

  1. 01

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

    Content efficiency

    Reduce markup overhead so readable text is at least 5% of your HTML. Strip unused inline scripts/styles, server-render content instead of shipping large JSON hydration blobs, and keep wrapper nesting shallow.

    Advertised capabilities
  3. 03

    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

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.

Essential11 of 12 passed · 77.8 / 80 points
  • Content without JavaScriptPartial (67%)
  • 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
Recommended29 of 31 passed · 19.5 / 20 points
  • Developer resource discoverabilityPartial (67%)
  • Brand name discoverabilityPassed
  • robots.txt AI crawler policyPassed
  • Sitemap existsPassed
  • Content efficiencyPartial (50%)
  • Content crawl depth signalsPassed
  • JSON-LD structured dataPassed
  • Pricing info accessiblePassed
  • 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 policyPassed
  • REST pagination patternPassed
  • REST async-job patternPassed
  • CLI tool availablePassed
  • Multi-language SDK packagesPassed
  • REST response schema coveragePassed
  • API schema complexity analysisPassed
  • Function calling compatibilityPassed
  • MCP resource qualityPassed
Bonus signals62 positive · +5 points
  • ARD / ai-catalogPassed
  • ARD entry validityPassed
  • Listed in MCP registriesPassed
  • NPM/PyPI SDK packagePassed
  • Agent platform configsPassed
  • Listed on skills.shPassed
  • Registry brandingPassed
  • ChatGPT app listedPassed
  • Agent discovery filePassed
  • Agent Skills index conformance (v0.2.0)Passed
  • A2A / agent-cardPassed
  • pricing.md existsPassed
  • NLWeb Schema FeedsPassed
  • 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)Passed
  • Speakable content markupPassed
  • Schema type breadthPassed
  • llms.txt links resolvePassed
  • Markdown alternate linkPassed
  • API catalog (RFC 9727)Passed
  • Markdown agent docsPassed
  • Markdown content negotiation (acceptmarkdown.com)Passed
  • Bot-UA markdown servingPassed
  • 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 simulationPartial (50%)
  • Agent auth discovery metadataPartial (33%)
  • 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.jsonPartial (75%)
  • Sandbox / test environmentPassed
  • REST batch / bulk endpointPassed
  • Accessible document structurePassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Form control labelingPassed
  • Accessibility-tree injection safety (bonus)Passed
  • UCP - Universal Commerce ProtocolPassed
  • ACP - Agentic Commerce ProtocolPassed
  • ACP delegate paymentPassed

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

Source: Ora API

Snapshot 2026-08-19T23-18-38-436Z