attio.com agentic web readiness
B Manifest validity: 75% (3/4 valid, 3 errors, 8 warnings) · Surface score 43 (coverage 30 + breadth 3 + conformance 10). 3 standards observed across 3 of 9 steps; 4 manifests present, 3 errors, 8 warnings. Checked 2026-10-25 03:09:05 UTC. This grades the agent-facing files published at attio.com, not the organisation's products.
Coverage by step
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 |
View valid |
Agent2Agent Protocol/.well-known/agent-card.json | valid |
|
llms.txt/llms.txt | valid | |
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 |
|
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://mcp.attio.com(sse) — from/.well-known/mcp.json - A2A agent Attio at
https://attio.com - llms.txt: Attio, 24 links, llms-full.txt present
- robots.txt AI policy: blocks CCBot, Bytespider, cohere-ai, YouBot; allows GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, anthropic-ai, Google-Extended, PerplexityBot, Applebot-Extended, Amazonbot, DuckAssistBot; unlisted crawlers allowed
- Endpoint check (
a2ahttps://attio.com): pseudo_endpoint_html (agent card url points to the HTML homepage rather than a callable A2A endpoint)
Standards observed
- Agent2Agent Protocol https://attio.com/.well-known/agent-card.json
- llms.txt https://attio.com/llms.txt
- AI Crawler User-Agent Tokens in robots.txt https://attio.com/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
Generate starter
/AGENTS.mdfor attio.com# Attio for agents Attio and what it offers to agents ## Read the data, not the HTML - Index: https://attio.com/llms.txt - API description: https://attio.com/openapi.json - Discovery catalog: https://attio.com/.well-known/ard.json ## Calling - MCP server (Streamable HTTP): https://attio.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@attio.com
- 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: mcp (fallback llms_txt). Call the MCP endpoint at https://mcp.attio.com first. Do not scrape the HTML when a tool can answer. Split-brain llms.txt: attio.com/llms.txt has 24 links while docs.attio.com/llms.txt has 369 technical links. Probe docs.attio.com for full developer documentation.
Fetch: POST https://mcp.attio.com POST a JSON-RPC tools/list, or server/discover on the 2026-07-28 revision, before reading HTML.
Subdomain discovery hint (split_brain_llms_txt): Split-brain llms.txt: attio.com/llms.txt has 24 links while docs.attio.com/llms.txt has 369 technical links. Probe docs.attio.com for full developer documentation. (check docs.attio.com)
Practical readability: exa_parsable yes, markdown negotiation no, render ssr_rich, HTML quality high, first content at byte 79828, HTML-to-llms.txt token ratio 56.717×, JSON-LD Organization, ImageObject, WebSite, SoftwareApplication, Offer.
AI crawler posture: search_partially_blocked · Assistant access: OpenAI allowed, Anthropic allowed, Google allowed, Perplexity allowed, Exa allowed.
Readiness subscores: reach 16/20, readability 22/30, capabilities 16/35, conformance 10/15, total 64/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