> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Knowledge Base

> Control exactly what the partner support agent knows - crawl your websites, add snippets and documents, and connect live tools over MCP.

export const Headless = ({prompts = []}) => {
  const PromptRow = ({prompt}) => {
    const [copied, setCopied] = useState(false);
    const copy = () => {
      try {
        navigator.clipboard?.writeText(prompt);
      } catch {}
      setCopied(true);
      setTimeout(() => setCopied(false), 1600);
    };
    return <div className="group flex items-center justify-between gap-3 px-4 py-3 transition-colors hover:bg-[#FD90FF]/[0.06]">
        <span className="text-sm leading-relaxed text-zinc-700 dark:text-zinc-200">{prompt}</span>
        <button type="button" onClick={copy} aria-label={copied ? "Copied to clipboard" : "Copy prompt"} className={`shrink-0 rounded-md p-1.5 transition-all hover:bg-[#FD90FF]/10 focus:opacity-100 focus:outline-none ${copied ? "text-[#FD90FF] opacity-100" : "text-zinc-400 opacity-0 group-hover:opacity-100 dark:text-zinc-500"}`}>
          {copied ? <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M20 6L9 17l-5-5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg> : <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <rect x="9" y="9" width="11" height="11" rx="2" stroke="currentColor" strokeWidth="2" />
              <path d="M5 15V5a2 2 0 0 1 2-2h10" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>}
        </button>
      </div>;
  };
  return <>
      <p>
        Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
        Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
        action written straight back to your CRM source of truth. The portal is one surface, never the only one.
      </p>

      {prompts.length > 0 ? <div className="not-prose my-6 overflow-hidden rounded-2xl border border-zinc-200/80 bg-white shadow-sm dark:border-white/10 dark:bg-white/[0.02]">
          <div className="flex items-center gap-2 border-b border-zinc-200/80 bg-gradient-to-r from-[#FD90FF]/10 via-[#FD90FF]/5 to-transparent px-4 py-2.5 dark:border-white/10">
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4 text-[#FD90FF]" aria-hidden="true">
              <path d="M12 2.5l2 5.5 5.5 2-5.5 2-2 5.5-2-5.5L4.5 10l5.5-2 2-5.5z" fill="currentColor" />
              <path d="M18.5 14l1 2.6 2.6 1-2.6 1-1 2.6-1-2.6-2.6-1 2.6-1 1-2.6z" fill="currentColor" opacity="0.55" />
            </svg>
            <span className="text-xs font-semibold uppercase tracking-wider text-zinc-500 dark:text-zinc-400">
              Try it from your LLM
            </span>
          </div>

          <div className="flex flex-col divide-y divide-zinc-100 dark:divide-white/[0.06]">
            {prompts.map(prompt => <PromptRow key={prompt} prompt={prompt} />)}
          </div>

          <a href="/headless" className="flex items-center justify-between gap-2 border-t border-zinc-200/80 px-4 py-2.5 text-sm font-medium text-zinc-600 no-underline transition-colors hover:text-[#FD90FF] dark:border-white/10 dark:text-zinc-300">
            <span>See the full headless playbook</span>
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M5 12h14M13 6l6 6-6 6" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
          from Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

> An agent is only as good as what it knows. The knowledge base is where you feed the partner support agent your websites, snippets, and documents - and connect live tools - so its answers are accurate, current, and specific to your program.

## What it does

The knowledge base is where you manage everything the partner support agent draws on. You can crawl
websites so the agent learns from your public content, write snippets to teach it specific facts or
answers, and upload documents like PDFs as sources. The agent also uses live, portal-scoped data,
announcements, tiers, commissions, assets, and CRM objects, automatically, scoped to each partner.

For richer capabilities, you can connect MCP servers so the agent can call live tools beyond your
content. You control every source, so you decide what the agent knows and can keep it current as your
program changes.

## The problem it solves

A generic agent gives generic, wrong answers:

* **Answers are vague or made up** → Grounded sources keep answers accurate.
* **Content is scattered** → Websites, snippets, and documents in one knowledge base.
* **Knowledge goes stale** → Re-crawl and update sources as things change.
* **The agent cannot reach live systems** → MCP servers give it live tools.

## From problem to solution

The knowledge base puts you in control of the agent's brain. Add the right sources, keep them
current, and connect live tools, so the partner support agent answers like an expert on your program.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  sources["Add sources"] --> tools["Keep current and connect tools"]
  tools --> answer["Agent answers like an expert"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Ground the agent" icon="circle-check">
    Feed it accurate sources.
  </Card>

  <Card title="Reuse existing content" icon="circle-check">
    Crawl sites and upload docs.
  </Card>

  <Card title="Teach specific answers" icon="circle-check">
    Add snippets for key facts.
  </Card>

  <Card title="Extend with tools" icon="circle-check">
    Connect MCP servers.
  </Card>
</CardGroup>

## Impact

* **AI-native** - The agent answers from sources you control.
* **Low total cost of ownership** - Partner ops manages knowledge with no engineering.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Operations" icon="user">
    Curates and updates knowledge sources.
  </Card>

  <Card title="Partner Marketing" icon="user">
    Adds content and key answers.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Partner Support Agent" icon="robot" href="/features/ai/partner-support">
    Grounds the partner support agent's answers.
  </Card>

  <Card title="Asset Library" icon="folder-open" href="/features/content/asset-library">
    Indexes your library so answers cite real content.
  </Card>

  <Card title="MCP" icon="code" href="/features/developer/mcp">
    Exposes the same knowledge to AI clients.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"What does our partner agreement say about renewals?",
"Summarize the latest product release notes for partners.",
"Which onboarding docs cover certification?",
]}
/>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>