aihero.dev agentic web readiness

A Manifest validity: 67% (2/3 valid, 1 error, 4 warnings) · Surface score 46 (coverage 30 + breadth 6 + conformance 10). 4 standards observed across 3 of 9 steps; 3 manifests present, 1 error, 4 warnings. Checked 2026-10-25 23:40:09 UTC via www.aihero.dev. This grades the agent-facing files published at aihero.dev, not the organisation's products.

Badge for a README: ![agentic web grade](https://agenticweb.wiki/badge/aihero.dev.svg) · JSON · Markdown · Re-check now

Coverage by step

Manifests

# Aihero

> Aihero and what it offers to agents

Short notes an agent should know before using the site: what it is for, who runs it, how to cite it.

## Docs
- [Getting started](https://aihero.dev/docs/getting-started): the first page to read
- [API reference](https://aihero.dev/openapi.json): OpenAPI description

## Optional
- [Changelog](https://aihero.dev/changelog): what changed, newest first

What an agent can call

• API description https://www.aihero.dev/api/openapi.json (application/openapi+json)
• API description https://www.aihero.dev/v1/course-sync/openapi.json (application/openapi+json)
• API description https://www.aihero.dev/llms.txt (text/plain)
• API description https://aihero.dev/api/openapi.json (service-desc)
• llms.txt: untitled, 0 links
• robots.txt AI policy: unlisted crawlers partial

Standards observed

• Content Signals Policy https://aihero.dev/robots.txt
• api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://aihero.dev/.well-known/api-catalog
• AI Crawler User-Agent Tokens in robots.txt https://aihero.dev/robots.txt
• Markdown for Agents https://aihero.dev/

Cheapest next steps

1. Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch (emerging spec — publish only if you run the underlying endpoints; generate via MCP template({"id": "ard", "domain": "aihero.dev"}))
2. AGENTS.md: instructions for coding agents working on or with the site
   Generate starter /AGENTS.md for aihero.dev

   # Aihero for agents
   
   Aihero and what it offers to agents
   
   ## Read the data, not the HTML
   - Index: https://aihero.dev/llms.txt
   - API description: https://aihero.dev/openapi.json
   - Discovery catalog: https://aihero.dev/.well-known/ard.json
   
   ## Calling
   - MCP server (Streamable HTTP): https://aihero.dev/mcp
   - Rate limits and authentication: describe them here
   
   ## Conventions
   - How to cite or attribute content
   - What not to do (no scraping of /account/, no automated sign-ups, etc.)
   
   Contact: security@aihero.dev
   

3. security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people
   Generate starter /.well-known/security.txt for aihero.dev

   Contact: mailto:security@aihero.dev
   Expires: 2027-09-20T23:40:09Z
   Canonical: https://aihero.dev/.well-known/security.txt
   Preferred-Languages: en
   Policy: https://aihero.dev/security-policy
   

Agent pre-flight & practical readiness

Preferred mode: openapi (fallback markdown_negotiation). Read the published API description and call those operations. Scraping HTML skips the interface the site already gave you.

Fetch: GET https://www.aihero.dev/api/openapi.json GET the API description and call the documented operations.

Practical readability: exa_parsable yes, markdown negotiation yes, render markdown_native, HTML quality high, first content at byte 0.

AI crawler posture: open_to_all · Assistant access: OpenAI partial, Anthropic allowed, Google allowed, Perplexity partial, Exa allowed.

Readiness subscores: reach 20/20, readability 28/30, capabilities 10/35, conformance 10/15, total 68/100, grade A.

How the grade is made

+10 per lifecycle step with a standard observed, counting manifests that validate or that the probe rule for the standard recognises (a valid MCP server card counts for MCP; max 90); +3 per observed standard beyond the first two (max 15); conformance +15 (+10 with one manifest) minus 5 per agent-facing manifest with errors, never below 0 (security.txt is reported, not scored). Lifecycle grade: A+ >= 60, A >= 45, B >= 30, C >= 20, D >= 10. Strict 100-point composite (subscores.total_100 / subscores.grade_100): reach_and_policy (20) + readability (30) + capabilities (35) + conformance (15), where A+ >= 80, A >= 65, B >= 45, C >= 28, D >= 15. Errors are specification violations; warnings are best-practice gaps. Only public paths are fetched, without credentials, so standards that need a login (skipped in the probe) are not counted either way. The same report is the validate_manifest tool on the MCP server.

JSON · Markdown · probe rules