Keep costs predictable with rate limiting
The fear with usage-based AI is the surprise bill. Stark Chat puts you in control: cap what each question can cost and how many can run per hour, on every chatbot — so usage can never run past what you have decided to spend.
Limits you set, per chatbot
Every chatbot has two dials: how much a single query can spend, and how many queries are allowed per hour. Spend is measured in credits — the usage unit included with every plan — so capping credits per query caps what one question can cost. Set both once in the dashboard and the chatbot enforces them for you.
Different chatbots can have different limits — generous for your internal team, tighter for anything public-facing.
Make public chatbots safe to run
A public chatbot means anyone can ask it questions — which is the point, but also the risk. Rate limits cap what any visitor can consume, so a burst of traffic or a bad actor cannot run up your bill.
That makes it practical to put a chatbot on your website for customers and prospects, not just behind a login for staff.
Predictable spend, no surprises
With per-query and per-hour ceilings in place, your worst-case spend is a number you chose, not one you discover on the invoice.
Adjust the limits any time as usage grows — no redeploy, no support ticket, just a change in the dashboard.
Set your spending caps in the dashboard and let the chatbot enforce them — costs stay exactly where you put them.
Try for freeSpend what you decide, nothing more
Cap what each question can cost and how many run per hour on every chatbot — usage can never run past the limits you set.