openfort.io agentic web readiness

A+ Manifest validity: 80% (4/5 valid, 3 errors, 16 warnings) · Surface score 62 (coverage 40 + breadth 12 + conformance 10). 6 standards observed across 4 of 9 steps; 5 manifests present, 3 errors, 16 warnings. Checked 2026-10-23 16:44:06 UTC via www.openfort.io. This grades the agent-facing files published at openfort.io, not the organisation's products.

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

Coverage by step

01 DiscoverRFC 9727 02 Identifynothing observed 03 PermitContent Signals Policy 04 Readllms.txt, Markdown for Agents 05 ActAgent Skills 06 Coordinatenothing observed 07 Paynothing observed 08 Presentnothing observed 09 Accountnothing observed

Manifests

Manifest	Result	Findings
Agentic Resource Discovery `/.well-known/ard.json`	absent HTTP 404
AI Catalog well-known file `/.well-known/ai-catalog.json`	absent HTTP 404
MCP Server Cards (SEP-2127) `/.well-known/mcp/server-card.json`	errors	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) name must be reverse-DNS with exactly one slash, e.g. com.example/weather version missing Content-Type is application/json; charset=utf-8; SEP-2127 says serve application/mcp-server-card+json pre-final card shape (url/transport/tools); the final SEP-2127 card uses name, version, description and remotes[] description is over 100 characters remotes missing: a card with no remotes gives clients nothing to connect to legacy /.well-known/mcp.json is still live and may shadow /.well-known/mcp/server-card.json in older scanners
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid	no blockquote summary under the title
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	valid	skills[0].digest missing skills[1].digest missing skills[2].digest missing skills[3].digest missing skills[4].digest missing skills[5].digest missing skills[6].digest missing skills[7].digest missing
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	valid
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json)
security.txt (RFC 9116) `/.well-known/security.txt`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://www.openfort.io/api/mcp (streamable-http) — from /.well-known/mcp.json
MCP endpoint https://www.openfort.io/api/mcp (streamable-http) — from /.well-known/mcp/server-card.json
API description https://www.openfort.io/docs/openapi.json (application/json)
API description https://www.openfort.io/docs (text/html)
llms.txt: Openfort, 58 links
robots.txt AI policy: unlisted crawlers allowed

Standards observed

llms.txt https://openfort.io/llms.txt
Content Signals Policy https://openfort.io/robots.txt
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://openfort.io/.well-known/api-catalog
Agent Skills https://openfort.io/.well-known/agent-skills/index.json
Markdown for Agents https://openfort.io/
AI Crawler User-Agent Tokens in robots.txt

Cheapest next steps

Agentic Resource Discovery: a catalog at /.well-known/ard.json lets agents discover your APIs, MCP servers and data in one fetch
AGENTS.md: instructions for coding agents working on or with the site
security.txt (RFC 9116): RFC 9116 contact and expiry, read by agents and people

Agent pre-flight & practical readiness

Preferred mode: mcp (fallback openapi). Call the MCP endpoint at https://www.openfort.io/api/mcp first. Do not scrape the HTML when a tool can answer.

Fetch: POST https://www.openfort.io/api/mcp POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.

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 allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.

Readiness subscores: reach 20/20, readability 30/30, capabilities 31/35, conformance 10/15, total 91/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