dchub.cloud agentic web readiness

A+ Manifest validity: 70% (7/10 valid, 5 errors, 19 warnings) · Surface score 75 (coverage 60 + breadth 15 + conformance 0). 12 standards observed across 6 of 9 steps; 10 manifests present, 5 errors, 19 warnings. Checked 2026-10-23 16:01:42 UTC. This grades the agent-facing files published at dchub.cloud, not the organisation's products.

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

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 9727 02 IdentifyWebBotAuth 03 PermitContent Signals Policy, AI Crawler User-Agent Tokens in robots.txt, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization), CIMD 04 Readllms.txt, AGENTS.md, Markdown for Agents 05 ActAgent Skills 06 CoordinateA2A 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`	valid	entries[0].identifier is not a urn:air: identifier entries[1].identifier is not a urn:air: identifier entries[2].identifier is not a urn:air: identifier entries[3].identifier is not a urn:air: identifier entries[4].identifier is not a urn:air: identifier entries[5].identifier is not a urn:air: identifier no entry has representativeQueries; ARD registries use 2-5 example queries to index entries
MCP Server Cards (SEP-2127) `/mcp/server-card`	errors	$schema missing (required: https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json) name missing description 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[] remotes missing: a card with no remotes gives clients nothing to connect to tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key) no Cache-Control max-age; clients should be able to cache the card no ETag 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`	errors	url missing (or supportedInterfaces in the 1.0 shape) supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape capabilities object missing (streaming, pushNotifications, stateTransitionHistory) defaultInputModes missing defaultOutputModes missing protocolVersion missing; clients cannot tell which A2A revision the card follows
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	valid
Agent Skills `/.well-known/agent-skills/index.json`	valid
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
security.txt (RFC 9116) `/.well-known/security.txt`	valid
auth.md `/auth.md`	errors	none of the auth.md mechanism names found (identity_assertion, service_auth, anonymous)
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

MCP endpoint https://dchub.cloud/mcp (streamable-http) — from /.well-known/ai-catalog.json
MCP endpoint https://dchub.cloud/mcp (streamable-http), tools: claim_free_key, search, fetch, execute_plan, search_facilities, get_facility, get_market_intel, get_market_dcpi_rank, predict_market_trajectory, get_gas_index, get_gas_economics, get_grid_scoreboard, compare_isos, get_intelligence_index, list_transactions, get_news, semantic_search, search_intelligence, get_market_context, get_iso_context — from /.well-known/mcp.json
MCP endpoint https://dchub.cloud/mcp (streamable-http), tools: claim_free_key, search, fetch, execute_plan, search_facilities, get_facility, get_market_intel, get_market_dcpi_rank, predict_market_trajectory, get_gas_index, get_gas_economics, get_grid_scoreboard, compare_isos, get_intelligence_index, list_transactions, get_news, semantic_search, search_intelligence, get_market_context, get_iso_context — from /.well-known/mcp/server-card.json
A2A agent DC Hub Intelligence, skills: facility_intelligence, site_planning, grid_intelligence, market_ranking, ai_capex_intel, deal_flow
A2A agent DC Hub Intelligence, skills: facility_intelligence, site_planning, grid_intelligence, market_ranking, ai_capex_intel, deal_flow
API description https://dchub.cloud/openapi.json (application/vnd.oai.openapi+json)
API description https://dchub.cloud/openapi.json (application/vnd.oai.openapi+json)
API description https://dchub.cloud/api-docs (text/html)
API description https://dchub.cloud/.well-known/mcp/server-card.json (application/json)
API description https://dchub.cloud/llms.txt (text/plain)
llms.txt: DC Hub — Data Center Intelligence Platform, 67 links, llms-full.txt present
robots.txt AI policy: unlisted crawlers partial; Agentmap https://dchub.cloud/.well-known/ai-catalog.json
OAuth protected resource https://dchub.cloud, authorization servers: https://beloved-stream-52.authkit.app

Standards observed

Agent2Agent Protocol https://dchub.cloud/.well-known/agent-card.json
llms.txt https://dchub.cloud/llms.txt
AGENTS.md https://dchub.cloud/AGENTS.md
Content Signals Policy https://dchub.cloud/robots.txt
Web Bot Auth HTTP Message Signatures https://dchub.cloud/.well-known/http-message-signatures-directory
AI Catalog well-known file https://dchub.cloud/.well-known/ai-catalog.json
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs https://dchub.cloud/.well-known/api-catalog
AI Crawler User-Agent Tokens in robots.txt https://dchub.cloud/robots.txt
OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization) https://dchub.cloud/.well-known/oauth-protected-resource
Agent Skills https://dchub.cloud/.well-known/agent-skills/index.json
OAuth Client ID Metadata Document https://dchub.cloud/.well-known/oauth-authorization-server
Markdown for Agents https://dchub.cloud/

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

Agent pre-flight & practical readiness

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

Fetch: POST https://dchub.cloud/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 partial, Anthropic partial, Google partial, Perplexity partial, Exa partial.

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