agenticweb.wiki

padlet.com agentic web readiness

A+ Manifest validity: 100% (6/6 valid, 1 security.txt error, 10 warnings) · Surface score 70 (coverage 40 + breadth 15 + conformance 15). 10 standards observed across 4 of 9 steps; 6 manifests present (+ robots.txt, security.txt), 1 security.txt error, 10 warnings. Checked 2026-10-25 03:29:31 UTC. This grades the agent-facing files published at padlet.com, not the organisation's products.

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

Coverage by step

01 DiscoverAI Catalog well-known file, RFC 972702 Identifynothing observed03 PermitContent Signals Policy, auth.md, OAuth Protected Resource and Authorization Server Metadata (as used for agent authorization)04 Readllms.txt, Markdown for Agents05 ActAgent Skills06 Coordinatenothing observed07 Paynothing observed08 Presentnothing observed

Manifests

ManifestResultFindings
Agentic Resource Discovery
/.well-known/ard.json
absent HTTP 404
AI Catalog well-known file
/.well-known/ai-catalog.json
valid
  • entries[0] has no description; registries index on it
  • entries[1] has no description; registries index on it
  • entries[2] has no description; registries index on it
  • entries[3] has no description; registries index on it
  • entries[4] has no description; registries index on it
  • entries[5] has no description; registries index on it
  • served only at deprecated /.well-known/ai-catalog.json; ARD v0.91+ expects /.well-known/ard.json (serve both during migration)
MCP Server Cards (SEP-2127)
/.well-known/mcp/server-card.json
valid
  • remotes[0].supportedProtocolVersions missing; clients use it to pick a version before connecting
Agent2Agent Protocol
/.well-known/agent-card.json
absent HTTP 404
llms.txt
/llms.txt
valid
AGENTS.md
/AGENTS.md
soft-404 HTML
  • answered with an HTML page (catch-all or soft 404), counted as absent
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
no AI tokens
  • no AI crawler token named (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, ...); the policy for them is whatever User-agent: * says (allowed)
security.txt (RFC 9116)
/.well-known/security.txt
errors
  • Expires: missing (RFC 9116 requires it)
  • Canonical: missing
View valid /.well-known/security.txt template for padlet.com
Contact: mailto:security@padlet.com
Expires: 2027-09-20T23:41:38Z
Canonical: https://padlet.com/.well-known/security.txt
Preferred-Languages: en
Policy: https://padlet.com/security-policy
auth.md
/auth.md
valid
Open Knowledge Format
/okf/index.md
absent HTTP 404

What an agent can call

Standards observed

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": "padlet.com"}))
  2. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for padlet.com
    # Padlet for agents
    
    Padlet and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://padlet.com/llms.txt
    - API description: https://padlet.com/openapi.json
    - Discovery catalog: https://padlet.com/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://padlet.com/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@padlet.com
    

Agent pre-flight & practical readiness

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

Fetch: POST https://mcp.padlet.com/ 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, HTML-to-llms.txt token ratio 1.944×.

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 35/35, conformance 15/15, total 100/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