sourcebot.dev

agent readiness score · scanned Aug 18, 2026 · 4s · Developer Tools

#23 of 979 · #9 in category

81/ 100B+

Sourcebot is a self-hosted developer tool that helps humans and AI agents search, navigate, and understand complex enterprise codebases, offering code search, AI-powered code understanding, and an agent context layer.

badge

Discovery 20/20

Access 30/30

Usability 21/40

Payments 10/10

Top fixes

  1. agents.md

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

    +6

  2. Docs quality

    Docs scored 0/5 on runnable examples. The documentation provides an overview of Sourcebot's features and configuration options but lacks specific API endpoints, request/response formats, or detailed integration steps for an AI agent.

    +6

  3. MCP server discovery

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

    +5

  4. security.txt

    Publish RFC 9116 /.well-known/security.txt with a Contact and a future Expires.

    +2

1.Can an agent discover and trust you?

8/8

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://www.sourcebot.dev/sitemap.xml: 28 entries, freshest <lastmod> 2026-07-21 (27 days ago)

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

    spec ↗
  • ✓Brand search discoverabilityrequired4/4

    Both searches ("Sourcebot" and "Sourcebot developer tools") cited sourcebot.dev: https://www.sourcebot.dev/changelog/share-links, https://www.sourcebot.dev/, https://app.sourcebot.dev/, https://docs.sourcebot.dev/docs/features/mcp-server

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

  • —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 ↗

2.Do you welcome agents?

13/16

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 ↗
  • ✓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, …)

  • ✓Content Signals directivesemerging2/2

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

    Looked for Content-Signal lines in robots.txt

    spec ↗
  • ✓Agent user-agent paritybetarequired4/4

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

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

  • ✗agents.mdrecommended0/3

    No agents.md: https://sourcebot.dev/agents.md → HTTP 404, https://sourcebot.dev/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 ↗

3.Does an agent understand who you are and what you do?

16/18

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: "Sourcebot is a self-hosted developer tool that helps humans and AI agents search, navigate, and understand complex enterprise codebases, offering code search, AI-powered code understanding, and an agent context layer.")

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

  • ✓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 ↗
  • ✓llms.txtrecommended4/4

    /llms.txt is valid llmstxt.org shape: H1 "Sourcebot", 13 markdown link(s)

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

    spec ↗
  • ✗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 ↗
  • ✓JSON-LD structured datarequired4/4

    3 JSON-LD block(s) on homepage and pricing page (types: Organization, SoftwareApplication, FAQPage); Organization block is well-formed

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

    spec ↗
  • ✓Markdown content negotiationrecommended3/3

    https://sourcebot.dev/ returns markdown for `Accept: text/markdown` (content-type text/markdown)

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

4.Can an agent integrate with you?

watch →6.5/9

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

  • —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 ↗
  • ✓Docs discoverablerequired4/4

    Docs found at https://docs.sourcebot.dev/docs/overview (via homepage link, 1651 chars of readable text)

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

  • ◐MCP server discoveryrequired2.5/5

    MCP evidence found only as a mention in llms.txt: "MCP server" — 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 ↗
  • —npm SDKrecommendedna

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

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

  • —PyPI SDKrecommendedna

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

    Searched PyPI for an official, domain-verified SDK package

5.Is your integration well-built?

watch →0/3

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

  • ✗Docs qualityrecommended0/3

    Docs at https://docs.sourcebot.dev/docs/overview scored clarity 4/5, completeness 2/5, runnable examples 0/5, agent-friendliness 2/5 (mean 2.0/5)

    fix → Docs scored 0/5 on runnable examples. The documentation provides an overview of Sourcebot's features and configuration options but lacks specific API endpoints, request/response formats, or detailed integration steps for an AI agent.

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

  • —Quickstart / getting startedrecommendedna

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

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

  • —MCP tool qualityrecommendedna

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

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

6.Can an agent use you reliably in production?

watch →3/4

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

  • ✓TLS & redirect hygienerequired2/2

    http://sourcebot.dev/ 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

  • ✓Response speed & weightrequired1/1

    Homepage TTFB 167ms, payload 92KB, Content-Encoding: br

    Measured homepage TTFB, payload size, and compression

  • ✗security.txtrecommended0/1

    https://sourcebot.dev/.well-known/security.txt returned HTTP 404

    fix → Publish RFC 9116 /.well-known/security.txt with a Contact and a future Expires.

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

    spec ↗

7.Can an agent authenticate to you?

watch →2/2

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 ↗
  • —OAuth protected resource metadatarecommendedna

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

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

    spec ↗
  • ✓Auth documentationrecommended2/2

    Auth documentation found at https://docs.sourcebot.dev/docs/api-reference/authentication (linked from https://docs.sourcebot.dev/docs/overview) with code examples

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

8.Can an agent transact with you?

watch →10/15

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

  • ✓Pricing discoverablerequired5/5

    Pricing page found at https://www.sourcebot.dev/pricing (via homepage link) with legible price signals ("$20per user / monthStart 14-da").

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

  • ✓Machine-readable pricingrecommended5/5

    LLM extracted 2 numerically-priced plan(s) from https://www.sourcebot.dev/pricing at confidence 1.00: Basic USD 0/lifetime; Pro USD 20/month; Enterprise (contact sales).

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

    spec ↗
  • ✗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 ↗
  • ✗AP2 readinessemerging0/1

    No AP2 hints found — scanned llms.txt, docs page (https://docs.sourcebot.dev/docs/overview); /.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 ↗
  • ✗Agentic Commerce Protocolemerging0/1

    No Agentic Commerce Protocol hints found — scanned llms.txt, docs page (https://docs.sourcebot.dev/docs/overview); /.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 ↗
  • ✗Other agent payment protocolsbonusemerging0/1

    No UCP/MPP hints found — scanned llms.txt, docs page (https://docs.sourcebot.dev/docs/overview).

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

    Scanned fetched artifacts for UCP/MPP protocol hints

9.Can a user act through an agent?

—

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

  • —MCP handshake & tools listrequiredna

    No MCP endpoint known — nothing to handshake with

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

    spec ↗
  • —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

10.Can an agent operate your website directly?

7/9

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 ↗
  • ✓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

  • ✓Content readable without JavaScriptrequired2/2

    Homepage raw HTML contains 3888 chars of visible text without JavaScript

    Measured visible text in the raw, unrendered homepage HTML

  • ✓Accessibility basicsrequired2/2

    Homepage accessibility: 4/5 checks passed — failing: labeled inputs (2/2 unlabeled)

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

  • ✗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 ↗