agenticweb.wiki

developers.intercom.com agentic web readiness

B Manifest validity: 50% (2/4 valid, 2 errors, 12 warnings) · Surface score 38 (coverage 30 + breadth 3 + conformance 5). 3 standards observed across 3 of 9 steps; 4 manifests present, 2 errors, 12 warnings. Checked 2026-10-25 09:06:41 UTC. This grades the agent-facing files published at developers.intercom.com, not the organisation's products.

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

Coverage by step

01 Discovernothing observed02 Identifynothing observed03 Permitnothing observed04 Readllms.txt05 ActAgent Skills06 CoordinateA2A07 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
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
  • 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 ETag
View valid /mcp/server-card template for developers.intercom.com
{
  "$schema": "https://static.modelcontextprotocol.io/schemas/v1/server-card.schema.json",
  "name": "com.intercom.developers/developers",
  "title": "Developers",
  "version": "1.0.0",
  "description": "Developers and what it offers to agents",
  "websiteUrl": "https://developers.intercom.com/",
  "icons": [
    {
      "src": "https://developers.intercom.com/icon.png",
      "mimeType": "image/png",
      "sizes": [
        "180x180"
      ]
    }
  ],
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://developers.intercom.com/mcp",
      "supportedProtocolVersions": [
        "2025-11-25",
        "2025-06-18",
        "2025-03-26"
      ]
    }
  ]
}
Agent2Agent Protocol
/.well-known/agent-card.json
valid
  • skills is empty
  • supportedInterfaces missing; A2A 1.0 cards declare interfaces there (url, protocolBinding, protocolVersion) and the top-level url is the 0.3 shape
  • protocolVersion is "0.3.0" (pre-1.0 legacy shape; A2A 1.0 uses protocolVersion "1.0" and supportedInterfaces[])
  • provider missing (organization, url)
llms.txt
/llms.txt
valid
  • file is large; keep llms.txt an index and put the full text in llms-full.txt
AGENTS.md
/AGENTS.md
absent HTTP 404
Agent Skills
/.well-known/agent-skills/index.json
errors
  • skills is empty
View valid /.well-known/agent-skills/index.json template for developers.intercom.com
{
  "$schema": "https://schemas.agentskills.io/discovery/0.2.0/schema.json",
  "skills": [
    {
      "name": "developers",
      "type": "skill-md",
      "description": "Developers and what it offers to agents",
      "url": "https://developers.intercom.com/.well-known/agent-skills/developers/SKILL.md",
      "digest": "sha256:0000000000000000000000000000000000000000000000000000000000000000"
    }
  ]
}
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
absent HTTP 404
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

Standards observed

Cheapest next steps

  1. AI Crawler User-Agent Tokens in robots.txt: state what AI crawlers may do in robots.txt you already serve
    Generate starter /robots.txt for developers.intercom.com
    # search and answer-engine crawlers
    User-agent: Googlebot
    User-agent: bingbot
    User-agent: OAI-SearchBot
    User-agent: Claude-SearchBot
    User-agent: PerplexityBot
    User-agent: ExaSearchBot
    User-agent: TavilyBot
    Allow: /
    
    # model-training crawlers: choose Allow or Disallow and keep it explicit
    User-agent: GPTBot
    User-agent: ClaudeBot
    User-agent: Google-Extended
    User-agent: Applebot-Extended
    User-agent: CCBot
    User-agent: meta-externalagent
    User-agent: Bytespider
    Disallow: /
    
    # user-triggered fetchers (a person asked for this page)
    User-agent: ChatGPT-User
    User-agent: Claude-User
    User-agent: Perplexity-User
    Allow: /
    
    # default fallback for unlisted crawlers (RFC 9309 §2.2.1: specific groups above take precedence over *)
    User-agent: *
    Allow: /
    Disallow: /account/
    Content-Signal: ai-train=no, search=yes, ai-input=yes
    
    Sitemap: https://developers.intercom.com/sitemap.xml
    Agentmap: https://developers.intercom.com/.well-known/ard.json
    
  2. 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": "developers.intercom.com"}))
  3. AGENTS.md: instructions for coding agents working on or with the site
    Generate starter /AGENTS.md for developers.intercom.com
    # Developers for agents
    
    Developers and what it offers to agents
    
    ## Read the data, not the HTML
    - Index: https://developers.intercom.com/llms.txt
    - API description: https://developers.intercom.com/openapi.json
    - Discovery catalog: https://developers.intercom.com/.well-known/ard.json
    
    ## Calling
    - MCP server (Streamable HTTP): https://developers.intercom.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@developers.intercom.com
    

Agent pre-flight & practical readiness

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

Fetch: POST /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 no, render ssr_rich, HTML quality high, first content at byte 373345 (~365 KB of head/script markup before main text), HTML-to-llms.txt token ratio 5.877×.

AI crawler posture: unspecified · Assistant access: OpenAI unspecified, Anthropic unspecified, Google unspecified, Perplexity unspecified, Exa unspecified.

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