pay.sh agentic web readiness

C Manifest validity: 60% (3/5 valid, 3 errors, 11 warnings) · Surface score 28 (coverage 20 + breadth 3 + conformance 5). 3 standards observed across 2 of 9 steps; 5 manifests present, 3 errors, 11 warnings. Checked 2026-10-23 16:44:19 UTC. This grades the agent-facing files published at pay.sh, not the organisation's products.

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

Coverage by step

01 Discovernothing observed 02 Identifynothing observed 03 Permitnothing observed 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	name 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[] $schema is not https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json 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
Agent2Agent Protocol `/.well-known/agent-card.json`	absent HTTP 404
llms.txt `/llms.txt`	valid
AGENTS.md `/AGENTS.md`	absent HTTP 404
Agent Skills `/.well-known/agent-skills/index.json`	valid	skills[0].digest missing $schema missing
api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs `/.well-known/api-catalog`	errors	Content-Type must be application/linkset+json (RFC 9727 §4), got application/json top-level linkset array missing (RFC 9264)
AI Crawler User-Agent Tokens in robots.txt `/robots.txt`	valid	no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (partial) 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`	absent HTTP 404
auth.md `/auth.md`	absent HTTP 404
Open Knowledge Format `/okf/index.md`	absent HTTP 404

What an agent can call

llms.txt: pay.sh, 20 links
robots.txt AI policy: unlisted crawlers partial

Standards observed

llms.txt https://pay.sh/llms.txt
Agent Skills https://pay.sh/.well-known/agent-skills/index.json
Markdown for Agents https://pay.sh/

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: agent_skills (fallback llms_txt). GET the Agent Skills index and load the SKILL.md files it lists. Those files are the procedure; the HTML is not.

Fetch: GET https://pay.sh/.well-known/agent-skills/index.json GET the Agent Skills index, then fetch the SKILL.md URLs it lists.

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 19/20, readability 28/30, capabilities 11/35, conformance 5/15, total 63/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