intercom.com

Journey

· Snapshot & citation

76.5/ 100

B · Ready with gaps

Waymark scored intercom.com 76.5/100 (B) on 24 Aug 2026.

intercom.com is usable with gaps. Access is the strongest layer, and Usability is the open one. Next: login or docs link.

FindMixed
14.8/20
11 of 18 checks passed
DoorMixed
25.1/30
13 of 19 checks passed
ToolsMixed
28.9/40
5 of 8 checks passed
Pay
N/A
No cart or pay rail — out of the denominator.

What should the prompt cover?

16 findings · 16 selected

Failures (13)

Warnings (3)

Group by
1. Can an agent discover and trust you?ROBOTSSITEMAPDISCOVERYSKILLS 68/100

Whether an agent can find this origin from public files and treat it as the real one.

pass
HTTPS reachable 2/2
Evidence. Homepage responded 200 over HTTPS.
Probed homepage.
pass
robots.txt present 2/2
Evidence. Valid robots.txt with User-agent rules.
Probed robots.txt.
pass
XML sitemap 2/2
Evidence. Found sitemap.xml or sitemap index.
failed
Well-known AI catalog 0/1
Evidence. No ai-plugin.json or ai-catalog.json.
Recommended fix. Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.
failed
AGENTS.md 0/1
Evidence. agents.md status 404.
Probed public URLs named in the evidence.
Recommended fix. Publish /agents.md with agent-oriented usage notes.
partial
robots.txt AI policy Required 1/2
Evidence. robots.txt present but no named AI crawlers.
Probed robots.txt.
Recommended fix. Name GPTBot, ClaudeBot, Google-Extended, PerplexityBot and state allow or deny.
pass
Sitemap for agents Recommended 2/2
Evidence. Sitemap document fetched.
Probed sitemap.
pass
HTTP Link header bonus 1/1
Evidence. Link: <https://developers.intercom.com/_bundle/docs/references/@2.15/rest-api/api.intercom.io.yaml>; rel="service-desc"; type="application/yaml", <https://developers.
Probed public URLs named in the evidence.
failed
ai-plugin.json bonus 0/1
Evidence. No /.well-known/ai-plugin.json.
Probed well-known paths.
Recommended fix. Optionally publish a plugin-style capability manifest.
pass
API catalog linkset bonus 2/2
Evidence. api-catalog found.
scanner error
Wikipedia sitelink bonus 0/4
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
scanner error
Wikidata official website bonus 0/3
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
scanner error
Brand official-website match Recommended 0/3
Evidence. Wikidata SPARQL The operation was aborted
Scanner error — not counted as a site fail and not in the score denominator.
pass
Public MCP registry listing bonus 1/1
Evidence. Registry hit at https://registry.modelcontextprotocol.io/v0/servers?search=intercom.
Probed public URLs named in the evidence.
failed
Package homepage match bonus 0/1
Evidence. No npm package homepage matching intercom.com.
Probed homepage.
Recommended fix. Publish an official package whose homepage is this domain.
failed
Sitemap lastmod bonus 0/1
Evidence. Sitemap without lastmod.
Recommended fix. Add lastmod dates to sitemap entries.
n/a
related-website-set bonus 0/1
Evidence. No related-website-set (N/A unless multi-origin).
n/a
ads.txt bonus 0/1
Evidence. No ads inventory (N/A).
2. Do you welcome agents?ROBOTSCRAWLBOT AUTH 88/100

Whether crawlers and signed bots are allowed through rather than blocked at the door.

pass
AI crawlers not blanket-blocked 2/2
Evidence. No blanket Disallow: / for common AI bots.
n/a
robots Crawl-delay bonus 0/1
Evidence. No Crawl-delay (optional).
n/a
Web Bot Auth keys Recommended 0/2
Evidence. No http-message-signatures-directory.
partial
CORS / API hint 0.5/1
Evidence. No CORS header or obvious API path.
Recommended fix. If you expose an API, send Access-Control-Allow-Origin for intended clients.
pass
CSP or X-Frame-Options 1/1
Evidence. CSP or X-Frame-Options present.
3. Does an agent understand who you are and what you do?HTMLJSON-LDLLMS.TXTSKILLSDOCSNLWEB 92/100

Whether the site explains the product in language a model can ingest.

pass
Title and description 2/2
Evidence. Title and meta description present.
pass
JSON-LD structured data 4/4
Evidence. application/ld+json script found.
pass
html lang attribute 1/1
Evidence. html[lang] is set.
pass
JSON-LD entities Recommended 4/4
Evidence. Recognized schema.org types in JSON-LD.
pass
JSON-LD sameAs bonus 2/2
Evidence. sameAs present.
pass
Open Graph basics bonus 2/2
Evidence. Open Graph plus canonical.
pass
llms.txt 2/2
Evidence. Found /llms.txt with content.
pass
llms.txt index Recommended 2/2
Evidence. llms.txt has content.
pass
llms.txt size and links Recommended 2/2
Evidence. llms.txt 8148 chars, 64 URL(s).
failed
llms-full.txt bonus 0/1
Evidence. llms-full.txt status 404.
Probed public URLs named in the evidence.
Recommended fix. Optionally publish /llms-full.txt for one-shot ingest.
n/a
Section llms.txt bonus 0/1
Evidence. No /docs/llms.txt.
n/a
NLWeb schemamap bonus 0/1
Evidence. No schemamap (N/A unless you offer NL search).
pass
Trust pages Recommended 2/2
Evidence. Trust links found.
n/a
Speakable markup bonus 0/1
Evidence. No SpeakableSpecification (N/A unless voice content).
n/a
humans.txt bonus 0/1
Evidence. No /humans.txt (optional).
pass
security.txt Recommended 1/1
Evidence. RFC 9116 security.txt with Contact.
failed
RSS or Atom feed 0/1
Evidence. No RSS/Atom link.
Recommended fix. Expose an RSS or Atom feed for machine subscribers.
n/a
RSS or Atom document bonus 0/1
Evidence. No /feed or /rss.xml document.
4. Can an agent integrate with you?LINKSSKILLSDOCSAPIOPSMCPSDK 77/100

Whether there is a documented machine door into the product.

n/a
OpenAPI / Swagger link 0/2
Evidence. No OpenAPI/Swagger link in HTML.
Probed OpenAPI.
failed
Login or docs link 0/3
Evidence. No login/docs/developers link.
Recommended fix. Link to login and developer documentation from the homepage.
pass
MCP well-known card 2/2
Evidence. MCP server card found under .well-known.
Probed well-known paths.
failed
MCP SSE / HTTP hint 0/1
Evidence. No MCP/SSE hint on the homepage.
Probed homepage.
Recommended fix. Document an MCP HTTP or SSE endpoint.
n/a
openapi.json fetchable 0/0
Evidence. No HTTP API surface (N/A).
failed
Webhook or API docs 0/2
Evidence. No webhook/API docs mention.
Recommended fix. Document webhooks and REST/RPC APIs for agents.
n/a
Agent skills index 0/2
Evidence. No agent-skills index (N/A unless you publish skills).
n/a
OpenAPI document Required 0/7
Evidence. OpenAPI probe.
Probed OpenAPI.
pass
Public API surface Recommended 7/7
Evidence. Docs or API paths look callable.
pass
Developer portal Recommended 6/6
Evidence. Developer hub found.
pass
MCP server Recommended 5/6
Evidence. MCP probe.
pass
MCP server card Recommended 2/2
Evidence. MCP card JSON found.
n/a
Agent Skills files bonus 0/2
Evidence. No SKILL.md surface (N/A).
n/a
CLI tool Recommended 0/3
Evidence. No CLI mention.
pass
GraphQL GET hint bonus 2/2
Evidence. GraphQL GET or docs mention.
n/a
OpenAPI UI page bonus 0/1
Evidence. No swagger-ui/redoc page.
n/a
OpenAPI (legacy slot) 0/0
Evidence. No HTTP API surface detected (N/A).
5. Is your integration well-built?APIMCP 100/100

Whether the integration surface is complete enough to call with confidence.

n/a
MCP initialize Required 0/3
Evidence. OAuth-gated MCP at https://mcp.intercom.com/mcp (HTTP 401) — not scored.
Probed public URLs named in the evidence.
pass
MCP server card Recommended 2/2
Evidence. MCP card JSON found.
6. Can an agent use you reliably in production?MCPAPIOPS 100/100

Whether errors, idempotency, and limits are visible before a call fails.

n/a
Rate limit signal Recommended 0/2
Evidence. No HTTP API surface (N/A).
n/a
Idempotency signal Recommended 0/3
Evidence. No HTTP API surface (N/A).
n/a
Machine-readable errors Recommended 0/4
Evidence. No HTTP API surface (N/A).
pass
Honest 404 Recommended 2/2
Evidence. 404/410 on probe path.
7. Can an agent authenticate to you?SDKOAUTHAUTH.MDMCP 50/100

Whether an agent can obtain access without a human in the loop.

partial
OAuth / OIDC well-known 1/2
Evidence. No oauth-authorization-server or openid-configuration.
Recommended fix. Publish /.well-known/openid-configuration or oauth-authorization-server if you authenticate agents.
n/a
OAuth 2.0 surface Required 0/5
Evidence. No delegated-access surface (N/A).
n/a
OAuth AS metadata Required 0/3
Evidence. No AS metadata (N/A unless you run an AS).
n/a
PKCE S256 Required 0/2
Evidence. No OAuth metadata to evaluate PKCE.
n/a
OAuth protected resource Recommended 0/2
Evidence. No OAuth resource metadata (N/A).
n/a
Scoped permissions Recommended 0/5
Evidence. No named OAuth scopes.
n/a
auth.md bonus 0/2
Evidence. No /auth.md (optional).
n/a
change-password well-known bonus 0/1
Evidence. No account door (N/A).
8. Can an agent transact with you?PRICINGX402MPPUCPACPAP2 100/100

Whether an agent can price, pay, or check out on a documented rail.

n/a
x402 payment bonus 0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
Agentic checkout (ACP) bonus 0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
ACP delegated payment bonus 0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
Universal Commerce Protocol bonus 0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
n/a
Machine Payments Protocol bonus 0/0
Evidence. No cart/SKU/checkout and no live payment rail (Pay N/A).
pass
Pricing page Recommended 3/3
Evidence. Fetched /pricing.
Probed public URLs named in the evidence.
n/a
pricing.md bonus 0/2
Evidence. No /pricing.md (optional).
9. Can a user act through an agent?APPS 0/100

Whether a person can finish a job through an agent-facing UI.

failed
MCP Apps UI hint bonus 0/1
Evidence. No MCP Apps hint (N/A unless you return UI).
Recommended fix. If you return UI, declare io.modelcontextprotocol/ui resources.
n/a
A2A agent card Required 0/2
Evidence. No agent-card.json (N/A unless A2A).
n/a
Web app manifest bonus 0/1
Evidence. No web app manifest (N/A).
10. Can an agent operate your website directly?MARKDOWNA11YHTMLWEBMCPNLWEBLLMS.TXT 33/100

Whether an agent can read and operate the site itself when there is no API or MCP.

failed
Markdown negotiation bonus 0/1
Evidence. Homepage did not negotiate markdown.
Probed homepage.
Recommended fix. Respond to Accept: text/markdown with a markdown body.
failed
/index.md fallback bonus 0/1
Evidence. index.md status 404.
Probed public URLs named in the evidence.
Recommended fix. Serve a markdown homepage at /index.md.
n/a
WebMCP page tools bonus 0/1
Evidence. No in-page WebMCP (N/A).
n/a
NLWeb /ask bonus 0/1
Evidence. No NLWeb /ask (N/A).
pass
Agent mode view bonus 1/1
Evidence. mode=agent responded.
Probed public URLs named in the evidence.
n/a
NodeInfo bonus 0/1
Evidence. No nodeinfo (N/A).
n/a
oEmbed discovery bonus 0/1
Evidence. No oEmbed (N/A unless embeddable).

About this snapshot & how to cite it

Public technical signals observed by Waymark. A score describes this snapshot; it does not guarantee that an agent will complete a task. Private and authenticated workflows are outside this scan.

Snapshot: . Cite the domain, score, scan time, and report URL. This URL serves the latest completed snapshot and can change after a rescan.

Methodology and limits · Markdown · JSON evidence

Scanner issues (not site fails): , , .

Share this snapshot

Embed the latest score. A badge is a public snapshot, not a certification.

Waymark score badge for intercom.com
Open badge SVG ↗

Also on the Board

Same-category snapshots, ordered by score. Scan times may differ.

Email me if this score changes

Join the monitoring waitlist. Monitoring is not active yet. This saves your interest; it does not schedule scans or send change alerts.

By joining, you agree to save your email and this domain for monitoring launch contact, for up to 180 days. Request removal via Contact. No billing.

Email this report

Send the current snapshot and a link. One email. Not a list.

We'll send intercom.com as it stands on this page.