Skip to main content
Answers from your docs, with citations.

​
The picture

Ask “how long do card refunds take?” and the agent looks it up instead of guessing. The answer arrives with a Sources row under it, one chip per cited document.
A Maple answer about card refund timing with a Sources row of five citation chips, one open on the snippet it quoted and the document it came from
Each chip opens the snippet the answer came from. When your docs do not cover the question, the turn says so plainly instead of inventing an answer. VENDO_API_KEY is the whole setup. The knowledge slot fills with the Cloud engine, and the agent picks up its vendo_knowledge_search tool with no code change.

​
Load your docs

1

Add them in the console

Open console.vendo.run and go to Knowledge. Upload files takes documents straight off your machine. Crawl a URL points the crawler at a docs site you already publish.Indexing takes a few seconds and the page does not spin while it runs. Refresh, and the document count tells you the corpus is searchable.
2

Prove it in the Playground

Still in the Knowledge tab, open Playground and ask something your docs answer. The passage under the green Would answer banner is the one the agent answers from; a passage marked Below the bar was retrieved but not cited.
That is the whole setup. In your app the same search tool runs on its own.

​
Docs that live in your repo

If your documentation sits next to your code, push it from the repo instead of uploading by hand.
add only records the source in .vendo/knowledge.json. sync is the one verb that moves content: it upserts what changed against the hash manifest at .vendo/knowledge-manifest.json and removes what vanished, so a second run over unedited files pushes nothing.

​
Say what shape a file is

--kind decides how a file is cut up. docs, the default, chunks prose at heading boundaries. glossary and api make every heading its own chunk, which is what makes an exact term lookup return the term rather than a fuzzy paragraph.
A source added with --visibility internal answers your own host-wired callers only: end-user turns never see those documents, and the prompt’s index does not name them. Every verb and flag is in the CLI reference.

​
Keep it synced from CI

Run vendo knowledge sync after a docs change merges, with VENDO_API_KEY set as a secret. Commit .vendo/knowledge-manifest.json so each run only pushes the documents that changed.