thecontextcompany.com

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

• ✓Sitemap present & freshrequired4/4

  Sitemap at https://thecontextcompany.com/sitemap.xml: 219 entries, freshest <lastmod> 2026-08-10 (8 days ago)

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

  spec ↗report issue
• ◐Brand search discoverabilityrequired2/4

  Search "The Context Company" cited thecontextcompany.com (https://docs.thecontextcompany.com/llms.txt, https://www.thecontextcompany.com/solutions), but search "The Context Company developer tools" did not cite your domain

  fix → Your domain doesn't surface when agents search "The Context Company developer tools". 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: 10 User-agent group(s), 0 Sitemap line(s)

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

  spec ↗report issue
• ✗AI crawler policyrequired0/5

  robots.txt blocks 6 of 12 AI crawler user-agents from /: GPTBot, ClaudeBot, Google-Extended, CCBot, meta-externalagent, Bytespider

  fix → robots.txt blocks GPTBot, ClaudeBot, Google-Extended, CCBot, meta-externalagent, Bytespider. Add explicit `User-agent: <bot>` / `Allow: /` groups for the AI agents you welcome; a blanket Disallow makes you invisible to them.

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

  report issue
• ◐Content Signals directivesemerging1/2

  1 Content-Signal line(s) found in robots.txt but none parse as `key=yes|no` pairs (e.g. `search=yes,ai-train=no,use=reference`)

  fix → Fix the Content-Signal syntax to comma-separated `key=yes|no` pairs, e.g. `Content-Signal: search=yes, ai-train=no`.

  Looked for Content-Signal lines in robots.txt

  spec ↗report issue
• ✗Agent user-agent paritybetarequired0/4

  Both bot UAs are blocked while the browser UA gets HTTP 200: ClaudeBot → HTTP 403; GPTBot → HTTP 403

  fix → Your WAF serves HTTP 403 / HTTP 403 to ClaudeBot and GPTBot while browsers get 200. Allowlist verified AI crawler UA/IP ranges in your bot-protection rules.

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

  report issue
• !agents.mdrecommendederror

  agents.md probes failed at the network layer: https://thecontextcompany.com/agents.md (Request budget exhausted), https://thecontextcompany.com/AGENTS.md (Request budget exhausted)

  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: "The Context Company provides an AI observability platform for monitoring AI agents in production, understanding user behavior, and improving customer outcomes.")

  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 "The Context Company", 17 markdown link(s)

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

  spec ↗report issue
• ✓llms-full.txtbonusrecommended2/2

  /llms-full.txt serves 32481 chars of markdown

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

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

  2 JSON-LD block(s) on homepage and pricing page (types: Organization); Organization block is well-formed

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

  spec ↗report issue
• ✓Markdown content negotiationrecommended3/3

  https://thecontextcompany.com/ returns markdown for `Accept: text/markdown` (content-type text/markdown)

  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://docs.thecontextcompany.com/ (via homepage link, 2197 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 qualityrecommended0/3

  Docs at https://docs.thecontextcompany.com/ scored clarity 4/5, completeness 2/5, runnable examples 0/5, agent-friendliness 3/5 (mean 2.3/5)

  fix → Docs scored 0/5 on runnable examples. The documentation is incomplete, as it explicitly states to fetch the complete index from a file that is not provided in the given context.

  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

  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://thecontextcompany.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 858ms, payload 173KB, Content-Encoding: br

  Measured homepage TTFB, payload size, and compression

  report issue
• !security.txtrecommendederror

  Fetch of https://thecontextcompany.com/.well-known/security.txt failed at the network layer (Request budget exhausted)

  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.thecontextcompany.com/pricing (via homepage link) with legible price signals ("$400/month$0.001 / run after 2").

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

  report issue
• ✓Machine-readable pricingrecommended5/5

  LLM extracted 2 numerically-priced plan(s) from https://www.thecontextcompany.com/pricing at confidence 1.00: developer USD 0/month; pro USD 400/month; custom (contact sales).

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

  spec ↗report issue
• !x402 payment supportbonusrecommendederror

  Could not fetch /.well-known/x402 (Request budget exhausted).

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

  spec ↗report issue
• !AP2 readinessemergingerror

  Could not probe /.well-known/ap2: Request budget exhausted; no AP2 hints in fetched artifacts.

  Scanned fetched artifacts and well-known paths for AP2 hints

  spec ↗report issue
• !Agentic Commerce Protocolemergingerror

  Could not probe /.well-known/acp: Request budget exhausted; no Agentic Commerce Protocol hints in fetched artifacts.

  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://docs.thecontextcompany.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 200 (text/html); GET /ask?query=hello returned HTTP 200 (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 3924 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