# Docs Chatbot

Answers questions about a library's functions by looking up structured documentation.

> For the complete documentation index, see [llms.txt](/llms.txt). Markdown variants are available by appending `.md` to any URL or sending an `Accept: text/markdown` header. An agent skill is available at [/.well-known/agent-skills/site-skill.md](/.well-known/agent-skills/site-skill.md).



<DocsBaseSwitcher base="flue" agent="docs-chatbot" />

<AgentPreview
  agent="docs-chatbot"
  framework="flue"
  inputFields="[
  {
    name: &#x22;query&#x22;,
    label: &#x22;Question&#x22;,
    placeholder: &#x22;Tell me about the getPlanetaryData function.&#x22;,
    type: &#x22;text&#x22;,
  },
]"
/>

## Summary [#summary]

The **Docs Chatbot Agent** answers questions about a code library's API. It looks
up structured function documentation — signatures, parameters, and examples — and
answers using only what the docs say. Reach for it to drop a grounded "ask the
docs" assistant into a docs site, an IDE, or a support channel.

## Install [#install]

```bash
npx shadcn@latest add @agentcn/flue/docs-chatbot
```

## Composition [#composition]

```text
agents/
└── docs-chatbot.ts      # Agent with the lookup_docs tool
tools/
└── lookup-docs.ts       # Looks up functions by name or keyword
data/
└── functions.json       # Sample documentation source
```

## Customization [#customization]

* **Point at your docs.** Replace `data/functions.json` with your generated API
  docs, or change `lookup-docs.ts` to fetch from a remote source.
* **Improve matching.** Swap the substring filter for embeddings-based search.
* **Expose it as MCP.** Wrap the tool in an MCP server for other clients.
* **Swap the model.** Change the `model` field on the agent.