swarmsync.ai agentic web readiness

B Manifest validity: 60% (3/5 valid, 5 errors, 14 warnings) · Surface score 38 (coverage 30 + breadth 3 + conformance 5). 3 standards observed across 3 of 9 steps; 5 manifests present, 5 errors, 14 warnings. Checked 2026-10-23 17:30:55 UTC. This grades the agent-facing files published at swarmsync.ai, not the organisation's products.

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

Coverage by step

01 Discovernothing observed 02 Identifynothing observed 03 PermitAI Crawler User-Agent Tokens in robots.txt 04 Readllms.txt 05 Actnothing observed 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`	absent HTTP 404
MCP Server Cards (SEP-2127) `/.well-known/mcp.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; 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 tools/resources/prompts listed in the card; SEP-2127 excludes primitives (list them live, or under a namespaced _meta key) no Access-Control-Allow-Origin: * (required for browser clients)
Agent2Agent Protocol `/.well-known/agent-card.json`	errors	version missing skills missing or not an array supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape defaultInputModes missing defaultOutputModes missing protocolVersion missing; clients cannot tell which A2A revision the card follows provider missing (organization, url)
llms.txt `/llms.txt`	valid	no Markdown links: list the pages an agent should read
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	absent HTTP 404
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	absent HTTP 404
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid	no Agentmap: line (optional convention pointing agents at /.well-known/ard.json) no Content-Signal: line (optional; states ai-train / search / ai-input preferences)
security.txt (RFC 9116) `/.well-known/security.txt`	valid
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

A2A agent SwarmSync at https://swarmsync.ai
A2A agent SwarmSync Commerce Demo Agent at https://swarmsync-agents.onrender.com/a2a, skills: Escrow-Protected Payment Demo, SwarmScore Trust Badge Demo, Task Verification Demo
llms.txt: Instructions, 0 links, llms-full.txt present
robots.txt AI policy: allows GPTBot, OAI-SearchBot, ClaudeBot, anthropic-ai, Google-Extended, PerplexityBot; unlisted crawlers partial

Standards observed

Agent2Agent Protocol https://swarmsync.ai/.well-known/agent-card.json
llms.txt https://swarmsync.ai/llms.txt
AI Crawler User-Agent Tokens in robots.txt https://swarmsync.ai/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
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs: an RFC 9727 linkset pointing at your OpenAPI description

Agent pre-flight & practical readiness

Preferred mode: a2a (fallback llms_txt). Send the task to the A2A agent endpoint named in the card. Use the card's skills instead of crawling pages.

Fetch: POST https://swarmsync.ai Send an A2A message to this agent endpoint. The card lists the skills.

Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 17847, JSON-LD WebSite, Organization, SearchAction, EntryPoint, SoftwareApplication, Offer, ContactPoint, WebApplication, ServiceChannel, BreadcrumbList, ListItem.

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

Readiness subscores: reach 19/20, readability 22/30, capabilities 10/35, conformance 5/15, total 56/100, grade B.

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