Knowledge base

Agents answer from your content, not from vibes. Attach documents and they are chunked, embedded, and retrieved per turn during calls and messages.

Adding knowledge

curl -X POST https://klaw-voice.netlify.app/api/v1/agents/$AGENT_ID/knowledge-base \
  -H "Authorization: Bearer $KLAW_KEY" -H "Content-Type: application/json" \
  -d '{"name": "Services and pricing", "content": "...up to 100KB of text..."}'

Response 201: {"knowledge_base_id", "document", "chunks"} — the text is split into chunks and embedded immediately; the very next call can use it.

From a website

During onboarding, pasting a website URL scrapes the site and attaches the text as a knowledge document automatically. The same works via the public preview route + the endpoint above if you're scripting it.

How retrieval works on calls

Each caller turn runs a vector search over the agent's chunks (embeddings + Postgres/pgvector) under a tight latency budget, and the best passages are injected into the reply prompt. Short acknowledgements ("yes", "okay") skip retrieval to keep the conversation snappy. Details in How KlawVoice works.

Tips

• Prefer several focused documents ("Hours & location", "Pricing", "FAQ") over one blob.
• Write like you'd talk: retrieval surfaces sentences, and the agent speaks them.
• Update by adding fresh documents; the newest content is available immediately.