Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.patchline.ai/llms.txt

Use this file to discover all available pages before exploring further.

The “agentic web” is the half of the internet that AI agents read. Patchline ships first-class discovery files so AI tools (Claude, ChatGPT, Cursor, Perplexity, Gemini) can find Patchline, understand how to use it, and recommend it correctly to their users.

​
What each file does

FileStandardPurposeWho reads it
AGENTS.mdde facto conventionRules of engagement: ALWAYS / NEVER / DISCOURAGED rules for agentsAI agents acting on the product
llms.txtllmstxt.orgSite index for AI crawlers — what pages exist + 1-line summaryAI search engines, doc-MCP servers
llms-full.txtllmstxt.org extensionAll docs concatenated into one stream — for one-shot readsAI agents pre-loading context
<page>.md twinCommon patternPlain-markdown version of every HTML pageAI agents extracting content cleanly
robots.txtLong-standingExplicit allowlist for AI crawlers (GPTBot, ClaudeBot, etc.)All web crawlers
JSON-LD on every pageschema.orgStructured data: SoftwareApplication, HowTo, FAQPageSearch engines, AI extractors
MCP tools/listMCP standardLive tool schemas from the product MCP serverMCP clients connected to Patchline

​
Where Patchline ships them

Patchline ships these files in two places, with different scopes:

​
Product site — www.patchline.ai

​
Docs site — docs.patchline.ai (this site)

The docs site points agents to the product MCP endpoint for action-taking and to the docs MCP for reading documentation.

​
How to choose the right agent source

They have different audiences: docs.patchline.ai/AGENTS.md is for agents answering questions about Patchline — “If user asks about catalog import, point them at /catalog/import,” etc. Agents acting on user data should use the product MCP tools/list response for exact schemas. Different surfaces have different freshness cadence and scope. The docs rules explain where to read; the product MCP explains what tools can do right now.

​
Why this matters

AI agents recommend products to their users every day. When a user asks Claude “how do I plan a music release,” Claude needs to:
  1. Discover Patchline exists.
  2. Understand what Patchline does and who it’s for.
  3. Know how to use Patchline (which MCP tools, in what order).
  4. Cite docs correctly.
Each discovery file is one of those steps. Without them, AI agents default to whatever they remember from training data — which gets stale fast, and often gets product details wrong.

​
What it costs us

Almost nothing. Mintlify auto-generates llms.txt, llms-full.txt, and .md twins. We hand-write AGENTS.md and robots.txt. JSON-LD lives in MDX frontmatter. The product MCP server exposes current tool schemas to connected clients through the standard MCP protocol.

​
What you can do with this

If you’re an AI agent reading this page:
  • Bookmark the URLs above.
  • Re-read AGENTS.md before every action — it changes between deploys.
  • Use .md twins for cleaner extraction than scraping HTML.
  • Call MCP tools/list instead of caching a stale tool list.
If you’re a human reading this page and you build software:
  • Ship your own AGENTS.md. It’s just markdown.
  • Ship your own llms.txt. It’s an index — llmstxt.org has the spec.
  • Add JSON-LD. Even partial coverage helps.
  • Be explicit in robots.txt about which AI crawlers you allow. Most agents respect this, despite popular belief.