loom.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.loom.com/sitemap.xml is valid XML with 372 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 discoverabilityrequired0/4

  Neither search ("Loom", "Loom productivity") cited loom.com. Cited instead: https://support.atlassian.com/loom/docs/inspect-video-data-and-generate-usage-reports/, https://support.atlassian.com/loom/docs/engagement-insights-data-exports/, https://support.atlassian.com/loom/docs/use-ai-workflows/, https://support.atlassian.com/loom/docs/access-user-reports-enterprise-only/, https://support.atlassian.com/loom/docs/capture-console-and-network-logs/

  fix → Your domain doesn't surface when agents search "Loom". Strengthen brand pages, structured data, and third-party citations (docs portals, GitHub, directories).

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

  report issue
• —MCP registry listingsrecommendedna

  No MCP server detected for this product

  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: 6 User-agent group(s), 1 Sitemap line(s)

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

  spec ↗report issue
• ◐AI crawler policyrequired2/5

  robots.txt blocks 1 of 12 AI crawler user-agents from /: GPTBot

  fix → robots.txt blocks GPTBot. Add explicit `User-agent: <bot>` / `Allow: /` groups for AI agents you welcome.

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

  report issue
• ✗Content Signals directivesemerging0/2

  No Content-Signal lines in robots.txt

  fix → Declare Content Signals in robots.txt (e.g. `Content-Signal: search=yes, ai-train=no`) to express AI usage preferences machine-readably.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✓Agent user-agent paritybetarequired4/4

  All three UAs get HTTP 200; bot bodies are ClaudeBot 100%, GPTBot 100% of the browser response (206990 bytes)

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

  report issue
• ✗agents.mdrecommended0/3

  No agents.md: https://loom.com/agents.md → HTTP 404, https://loom.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: "Loom is an AI-powered screen recording and video messaging tool for Mac and PC that helps teams communicate and collaborate more efficiently through shareable video messages with editing, transcription, and integration capabilities.")

  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.txtrecommended2/4

  /llms.txt exists (908 chars) but is missing at least one markdown link [name](url)

  fix → Your /llms.txt is missing at least one markdown link [name](url). Follow llmstxt.org: start with `# YourName`, add a `>` summary line, then sections of curated links.

  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 datarequired2/4

  1 JSON-LD block(s) on homepage and pricing page (types: Corporation) but none is a substantive type, or Organization/WebSite lacks name+url

  fix → Embed Organization + WebSite JSON-LD with name and url on your homepage (plus logo, sameAs) and Product/Offer JSON-LD on pricing.

  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 (2 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://www.atlassian.com/blog/loom/loom-ai-workflows (via homepage link, 8217 chars of readable text)

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

  report issue
• ◐MCP server discoveryrequired2.5/5

  MCP evidence found only as a mention in llms.txt: "https://mcp.atlassian.com/v1/sse" — no well-known server card

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

  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 qualityrecommended0/3

  Docs at https://www.atlassian.com/blog/loom/loom-ai-workflows scored clarity 1/5, completeness 0/5, runnable examples 0/5, agent-friendliness 0/5 (mean 0.3/5)

  fix → Docs scored 0/5 on completeness. The documentation is a marketing blog post and does not contain any technical details or API specifications for integration.

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

  report issue
• —Quickstart / getting startedrecommendedna

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

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

  report issue
• —MCP tool qualityrecommendedna

  MCP endpoint is auth-gated — tools could not be listed unauthenticated

  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://loom.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 & weightrequired1/1

  Homepage TTFB 96ms, payload 202KB, Content-Encoding: br

  Measured homepage TTFB, payload size, and compression

  report issue
• ✓security.txtrecommended1/1

  Valid security.txt at https://loom.com/.well-known/security.txt: Contact https://www.atlassian.com/trust/security/report-a-vulnerability, Expires 2027-02-04

  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.loom.com/pricing (via homepage link) with legible price signals ("$0Sign upKey Features25 videos").

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

  report issue
• ✓Machine-readable pricingrecommended5/5

  LLM extracted 3 numerically-priced plan(s) from https://www.loom.com/pricing at confidence 1.00: Starter $ 0/month; Business $ 18/user / month; Business + AILoom AI $ 24/user / month; Enterprise (contact sales).

  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 403. 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://www.atlassian.com/blog/loom/loom-ai-workflows); /.well-known/ap2 returned HTTP 403.

  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://www.atlassian.com/blog/loom/loom-ai-workflows); /.well-known/acp returned HTTP 403.

  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://www.atlassian.com/blog/loom/loom-ai-workflows).

  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 listrequired0/4

  MCP endpoint https://mcp.atlassian.com/v1/sse returned 401/403 without resolvable resource_metadata in WWW-Authenticate

  fix → MCP endpoint https://mcp.atlassian.com/v1/sse failed handshake: auth-gated without RFC 9728 metadata. If auth-gated, return resource_metadata in WWW-Authenticate so agents can discover how to authenticate.

  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 403 (application/xml); 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 structurerequired1.5/3

  4/6 semantic signals present on the homepage (missing: <header>/<footer>, text-to-markup ratio ≥ 0.10)

  fix → Add the missing structure: <header>/<footer>, text-to-markup ratio ≥ 0.10. Agents parse structure, not pixels.

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

  report issue
• ✓Content readable without JavaScriptrequired2/2

  Homepage raw HTML contains 4609 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