Chatbase Hobby

Retrieval over your own documents, wired to a chat widget, using a pipeline that has been standard since 2023 and is available free in several open tools.

WRAPPER

An interface and a system prompt over a public API. This describes an architecture, not a vendor’s conduct: shipping one is legal, common, and sometimes exactly what a customer wants.

Vendor
Chatbase
Category
Support
Tier
Hobby
Price / month
$40
Est. API cost
$6.43
Est. markup
6.2×
Price checked
13 Aug 2026
Verification
verified
§1 · Billing

What the price actually is

Billed monthly. Tiers are bounded by message credits and the number of chatbots rather than by seats, and messages beyond the allowance are billed on top of the subscription.

§2 · Assumption

The usage this is priced against

A small business support bot answering 1,000 messages a month over its own documentation: each answer retrieves a few passages, sends roughly 6,000 tokens of context, and returns 400.

Someone using it half as much sees double the multiple. The assumption is the argument — if you disagree with it, the number below is not about you. Change it in the calculator.

§3 · Arithmetic

The cost math, in full

Estimated monthly inference cost

6,000,000 input tokens$4.80

Small fast text model at $0.80 / 1M input tokens · 1,000 answers over retrieved passages

400,000 output tokens$1.60

Small fast text model at $4.00 / 1M output tokens

1,500,000 embedded tokens$0.03

Text embedding model at $0.02 / 1M embedded tokens · embedding the site and documentation the bot answers from

Estimated cost$6.43
Price paid (Hobby)$40
Estimated markup6.2×

Rates come from a dated rate card of representative published API prices, not from the vendor. Nobody outside these companies knows what they actually pay; volume discounts and in-house serving both push real costs below these figures, which makes every multiple here a floor rather than a ceiling.

§4 · Reasoning

Why this verdict, not the number

Point it at a website, chunk, embed, retrieve, answer. The hosting, the widget and the ingestion of awkward source formats are real work, and for a small business with no engineer they are the entire reason to pay. What the price is not buying is anything about the answering itself, which runs on a licensed model doing the most documented task in the field. Compare this against Intercom Fin in the same category: one charges for a bot, the other charges only when a conversation is actually resolved, and that difference is the whole argument.

What the price buys besides tokens

  • UX craft
  • Integrations

Ingesting a messy website into a usable index without anyone writing a scraper, and a widget that drops into a page. For a business without engineers that is a genuine service; it is also the part that is easiest to replace as the tooling commoditises.

§5 · Leaving

What you lose if you leave

Hosting, the embed widget, and never thinking about chunking. Someone has to run the thing, and if it is not the vendor it is you.

The honest cheaper path

Open tools such as AnythingLLM, Flowise or Open WebUI do the same pipeline over your own key, self-hosted. Cheaper per message by a wide margin, and you own the uptime.

§6 · Your numbers

Recompute it for yourself

Recompute this for your own usage

Your estimated cost
Your markup
Cost per unit of our assumption

Scaling assumes your usage has the same shape as ours, just more or less of it. If your mix is different — far more output than input, say — the estimate drifts. It is an estimate either way.

§7 · Sources

Where every number came from

Price recorded 13 Aug 2026 · entry last reviewed 13 Aug 2026. Think something here is wrong? File a correction — we publish them, including the ones that embarrass us.