intercom.com

Whether agents can crawl you, find you in the registries and searches they check, and trust what they find.

• ◐Sitemap present & freshrequired2/4

  Sitemap at https://www.intercom.com/sitemap.xml is valid XML with 61 entries but contains no <lastmod> dates

  fix → Publish /sitemap.xml, reference it from robots.txt, and include <lastmod> dates so agents can tell what's current. Freshest lastmod seen: none.

  Resolved the sitemap from robots.txt or /sitemap.xml, validated XML, and checked lastmod freshness

  spec ↗report issue
• ✓Brand search discoverabilityrequired4/4

  Both searches ("Intercom" and "Intercom communication support") cited intercom.com: https://www.intercom.com/help/en/articles/4549035-create-a-custom-report, https://www.intercom.com/help/en/articles/7022438-reporting-metrics-attributes, https://www.intercom.com/help/en/articles/8825260-reporting-datasets, https://www.intercom.com/help/en/articles/8921906-reporting-faqs, https://www.intercom.com/help/en/collections/2094752-reports

  Ran clean brand-name web searches and checked whether your domain is cited in the results

  report issue
• ◐MCP registry listingsrecommended2/4

  /.well-known/mcp/server-card.json serves JSON; searched "intercom.com" and "Intercom": listed only in Glama, not in the official MCP registry

  fix → Publish your MCP server to the official MCP registry (registry.modelcontextprotocol.io) plus Smithery and Glama. Found in: Glama.

  Queried the official MCP registry, Smithery, Glama, and PulseMCP for servers matching your domain

  spec ↗report issue

Whether your robots policy, bot protection, and agent guidance actively admit AI agents instead of blocking them.

• ✓robots.txt present & parseablerequired2/2

  /robots.txt parses: 1 User-agent group(s), 1 Sitemap line(s)

  Fetched /robots.txt and validated it parses as a robots policy

  spec ↗report issue
• ✓AI crawler policyrequired5/5

  All 12 AI crawler user-agents (GPTBot, ClaudeBot, PerplexityBot, …) are allowed at / by robots.txt

  Evaluated robots.txt groups for the major AI agent user-agents (GPTBot, ClaudeBot, PerplexityBot, …)

  report issue
• ✓Content Signals directivesemerging2/2

  1 valid Content-Signal line(s) in robots.txt (e.g. `Content-Signal: ai-train=yes, search=yes, ai-input=yes`)

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• !Agent user-agent paritybetarequirederror

  Browser UA received HTTP 200 with bot-challenge markers — cannot evaluate parity (the site may be blocking our scanner)

  Compared responses served to browser and AI-agent user-agents (informational while in beta)

  report issue
• ✗agents.mdrecommended0/3

  No agents.md: https://intercom.com/agents.md → HTTP 404, https://intercom.com/AGENTS.md → HTTP 404

  fix → Add /agents.md: what agents may do on your site, key URLs, auth, rate limits, and who to contact.

  Fetched /agents.md and checked for substantive agent guidance

  spec ↗report issue

Whether your pages carry machine-readable identity: structured data, llms.txt, clear copy an agent can quote.

• ✓Homepage states what you arerequired3/3

  Homepage clarity rated 5/5 — an agent can confidently say what this company does (model's one-sentence read: "Intercom is a helpdesk platform that combines human agents and an integrated AI agent named Fin to provide customer service, offering features like an omnichannel inbox, AI-powered ticketing, and real-time assistance.")

  An LLM read your homepage as an agent would and rated how confidently it could say what you do

  report issue
• ✓OpenGraph / social metadatarecommended2/2

  Homepage has og:title, og:description, and og:image (twitter:card="summary_large_image" present)

  Parsed homepage og:title / og:description / og:image and twitter:card meta tags

  spec ↗report issue
• ✓llms.txtrecommended4/4

  /llms.txt is valid llmstxt.org shape: H1 "Intercom — llms.txt", 63 markdown link(s)

  Fetched /llms.txt and validated it against the llmstxt.org shape (H1, summary, curated links)

  spec ↗report issue
• ✗llms-full.txtbonusrecommended0/2

  GET /llms-full.txt returned HTTP 404

  fix → Add /llms-full.txt with expanded inline docs content so agents can load everything in one fetch.

  Fetched /llms-full.txt and checked for substantial inline markdown content

  spec ↗report issue
• ✓JSON-LD structured datarequired4/4

  12 JSON-LD block(s) on homepage and pricing page (types: WebSite, Organization, WebPage, Product, SoftwareApplication, ItemList, BreadcrumbList, FAQPage); WebSite block is well-formed

  Extracted and validated application/ld+json blocks on the homepage and pricing page

  spec ↗report issue
• ✗Markdown content negotiationrecommended0/3

  GET / with `Accept: text/markdown` returned HTTP 200 text/html; no .md twins found (1 probed)

  fix → Serve text/markdown when clients send `Accept: text/markdown` (or expose .md twins of key pages) — agents get far more signal per token.

  Requested key pages with Accept: text/markdown and probed .md twin URLs

  report issue

Whether the artifacts an agent needs to build on you — docs, API specs, SDKs, MCP servers — exist and are findable.

• —Developer resource discoverabilityrecommendedna

  No public API detected

  Searched for your brand with developer-keyword suffixes and checked which official resources are cited

  report issue
• —OpenAPI spec discoverablerequiredna

  No public developer API detected — API checks don't apply

  Probed standard OpenAPI locations and docs links for a fetchable, parseable spec

  spec ↗report issue
• ✓Docs discoverablerequired4/4

  Docs found at https://developers.intercom.com/ (via homepage link, 2134 chars of readable text)

  Followed homepage nav/footer links and probed /docs, /developers, docs.{domain}

  report issue
• ✗MCP server discoveryrequired0/5

  No MCP evidence found: probed /.well-known/mcp/server-card.json, /.well-known/mcp.json, /mcp.json and scanned llms.txt, agents.md, and docs for endpoints or install commands

  fix → Publish /.well-known/mcp/server-card.json describing your MCP endpoint so agents can autodiscover it. Evidence found: none.

  Probed /.well-known/mcp/server-card.json, mcp.json, and docs mentions for an MCP endpoint

  spec ↗report issue
• —npm SDKrecommendedna

  No public developer API detected — API checks don't apply

  Searched the npm registry for an official, domain-verified SDK package

  report issue
• —PyPI SDKrecommendedna

  No public developer API detected — API checks don't apply

  Searched PyPI for an official, domain-verified SDK package

  report issue

Whether your specs, docs, and tools are complete and descriptive enough for an agent to use them without guessing.

• —OpenAPI validity & qualityrecommendedna

  No public developer API detected — API checks don't apply

  Linted the spec: descriptions, operationIds, securitySchemes, servers

  report issue
• ◐Docs qualityrecommended2.3/3

  Docs at https://developers.intercom.com/ scored clarity 4/5, completeness 3/5, runnable examples 4/5, agent-friendliness 4/5 (mean 3.8/5)

  fix → Docs scored 3/5 on completeness. The documentation is a landing page and does not provide a complete, step-by-step guide for building a specific integration from start to finish without navigating to multiple linked pages.

  An LLM rated your docs for clarity, completeness, runnable examples, and agent-friendliness

  report issue
• ✓Quickstart / getting startedrecommended2/2

  Quickstart found: https://developers.intercom.com/docs/build-an-integration/getting-started/ (linked from https://developers.intercom.com/) returns 200 with a code block

  Looked for a quickstart/getting-started guide containing code blocks

  report issue
• —MCP tool qualityrecommendedna

  No MCP endpoint known — tool lint requires a tools/list

  Linted listed tools for descriptions, typed input schemas, and naming

  report issue

Response hygiene, TLS and redirect discipline, and security contact channels agents depend on at runtime.

• ✓TLS & redirect hygienerequired2/2

  http://intercom.com/ upgrades to https in 1 hop(s), 2 redirect(s) total, final HTTP 200; HSTS present

  Checked http→https redirect behavior, chain length, and TLS health

  report issue
• ◐Response speed & weightrequired0.5/1

  Homepage TTFB 179ms, payload 1576KB, Content-Encoding: br — one target missed: payload 1576KB (target ≤1536KB)

  fix → Fix: payload 1576KB (target ≤1536KB). Enable compression and trim payload — agents run on strict timeouts.

  Measured homepage TTFB, payload size, and compression

  report issue
• ✓security.txtrecommended1/1

  Valid security.txt at https://intercom.com/.well-known/security.txt: Contact https://bugcrowd.com/intercom, Expires 2029-03-15

  Fetched /.well-known/security.txt and validated Contact + Expires

  spec ↗report issue

Whether agents can discover your auth model machine-readably (OAuth metadata) and follow documented steps to credentials.

• —OAuth authorization server metadatarecommendedna

  No API or MCP server detected — OAuth metadata doesn't apply

  Fetched /.well-known/oauth-authorization-server (and openid-configuration fallback)

  spec ↗report issue
• —OAuth protected resource metadatarecommendedna

  No API or MCP server detected — OAuth metadata doesn't apply

  Fetched /.well-known/oauth-protected-resource

  spec ↗report issue
• —Auth documentationrecommendedna

  No public developer API detected — API checks don't apply

  Looked for /auth.md or an authentication docs page with code examples

  report issue

Whether pricing is discoverable and machine-readable, and whether you support agent payment protocols.

• ✓Pricing discoverablerequired5/5

  Pricing page found at https://www.intercom.com/pricing (via homepage link) with legible price signals ("$0.99per Fin outcome$29per sea").

  Followed nav/footer links and probed /pricing for a page with legible price signals

  report issue
• ✓Machine-readable pricingrecommended5/5

  LLM extracted 10 numerically-priced plan(s) from https://www.intercom.com/pricing at confidence 0.90: Essential $ 0.99/per Fin outcome; Essential $ 29/per seat/mo; Advanced $ 0.99/per Fin outcome; Advanced $ 85/per seat/mo; Expert $ 0.99/per Fin outcome; Expert $ 132/per seat/mo; Fin AI Agent (with existing helpdesk) $ 0.99/per Fin outcome; Pro Add-on $ 99//mo; Copilot Add-on $ 29/per agent/mo; Proactive Support Plus Add-on $ 99//mo.

  Looked for Offer JSON-LD, then had an LLM attempt structured extraction of your plans

  spec ↗report issue
• ✗x402 payment supportbonusrecommended0/2

  /.well-known/x402 returned HTTP 404. No x402 support detected (bonus check — absence costs nothing).

  fix → Support x402: serve payment requirements at /.well-known/x402, or answer unauthenticated API calls with HTTP 402 plus an x402 payment-requirements payload (x402Version, accepts[]).

  Probed /.well-known/x402 and API endpoints for HTTP 402 payment-required envelopes

  spec ↗report issue
• ✗AP2 readinessemerging0/1

  No AP2 hints found — scanned llms.txt, docs page (https://developers.intercom.com/); /.well-known/ap2 returned HTTP 404.

  fix → Adopt AP2 to accept delegated agent payments — see https://ap2-protocol.org.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• ✗Agentic Commerce Protocolemerging0/1

  No Agentic Commerce Protocol hints found — scanned llms.txt, docs page (https://developers.intercom.com/); /.well-known/acp returned HTTP 404.

  fix → Adopt the Agentic Commerce Protocol so agent checkouts can complete against your store — see https://developers.openai.com/commerce.

  Scanned docs and specs for agentic checkout endpoints

  spec ↗report issue
• ✗Other agent payment protocolsbonusemerging0/1

  No UCP/MPP hints found — scanned llms.txt, docs page (https://developers.intercom.com/).

  fix → Track emerging agent payment protocols (UCP, MPP) and adopt the ones your buyers' agents use.

  Scanned fetched artifacts for UCP/MPP protocol hints

  report issue

Whether an end user's agent can operate on their behalf: working MCP tools, published skills, agent configs.

• —Agent skill publishedbonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked /skill.md, /.well-known/skills/, and skills.sh for published agent skills

  report issue
• —MCP handshake & tools listrequiredna

  No MCP endpoint known — nothing to handshake with

  Performed a streamable-HTTP initialize + tools/list against the MCP endpoint

  spec ↗report issue
• —Agent configs in public repobonusemergingna

  Requires the analysis phase — not yet evaluated

  Checked your public GitHub org's main repos for AGENTS.md / .claude / .cursor configs

  report issue

Whether the site itself is legible to non-rendering and browser agents: semantic HTML, no JS walls, accessibility.

• ✗NLWeb endpointemerging0/1

  No NLWeb endpoint detected: /.well-known/nlweb.json returned HTTP 404 (text/html); GET /ask?query=hello returned HTTP 404 (text/html)

  fix → Consider exposing an NLWeb /ask endpoint (and /.well-known/nlweb.json) for conversational access to your content.

  Probed /.well-known/nlweb.json and the /ask endpoint

  spec ↗report issue
• ✓Semantic HTML structurerequired3/3

  5/6 semantic signals present on the homepage (missing: text-to-markup ratio ≥ 0.10)

  Scored landmark elements, heading hierarchy, and text-to-markup ratio on the homepage

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 8909 chars of visible text without JavaScript

  Measured visible text in the raw, unrendered homepage HTML

  report issue
• ✓Accessibility basicsrequired2/2

  Homepage accessibility: 5/5 checks passed

  Static checks: lang attribute, title, alt coverage, labeled inputs, landmarks

  report issue
• ✗WebMCPemerging0/1

  No WebMCP evidence on homepage: no application/webmcp script and no navigator.modelContext reference

  fix → Consider WebMCP to expose page actions as tools to browser agents.

  Looked for WebMCP script declarations on the homepage

  spec ↗report issue