Everything a small FAQ bot needs, nothing it does not.
Unibot keeps the moving parts few: accounts, bots, answers, and two ways to ask a question.
Keyword answers
Each question is matched against your stored questions and answers. Words found in a stored question count double. You get the best match plus up to three alternatives.
Public ask route
GET /v1/bots/{slug}/ask?q= returns JSON and needs no key for public bots. Private bots never answer here.
MCP server
Four tools over Streamable HTTP at /mcp: list your bots, create one, add answers, and ask. Tools act as the user whose token you send.
Email one-time codes
Confirm sign-up with a six-digit code sent to your inbox. Passwords work for later logins once your email is verified.
Owner-only data
Only the owner can list, read, change or delete a bot and its answers. Rules are enforced by the API, not by the client.
Markdown docs
Every documentation page also exists as markdown, listed in llms.txt, so agents can read them cheaply.
What is not included
Unibot does not generate answers with a language model, scrape websites, or train on your content. A bot only ever returns text you wrote yourself. That makes it predictable, fast and easy to audit.