Chatbase · Rate Limits

Chatbase Rate Limits

Chatbase enforces account-level usage governance primarily through monthly message credits tied to the subscription plan (Free 50, Hobby 500, Standard 4,000, Pro 15,000, Enterprise custom). Every AI response consumes credits, and per-response cost depends on the chosen model. In addition, the REST API applies request rate limiting per API key; specific per-endpoint request-per-minute values are not published and are not reconciled in this artifact. Training-data size and number of agents are also capped per plan.

Chatbase Rate Limits is the machine-readable rate-limit profile for Chatbase on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring credits, requests, agents, and bytes.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include AI, Chatbot, AI Agent, Customer Support, and Conversational AI.

4 Limits Throttle: 429
AIChatbotAI AgentCustomer SupportConversational AIRate LimitingQuotasThrottling

Limits

Monthly Message Credits account
credits
plan-based (Free 50 / Hobby 500 / Standard 4,000 / Pro 15,000 / Enterprise custom)
Each AI response consumes credits; per-response cost depends on the model.
API Requests Per Minute api_key
requests
see provider documentation
REST API requests are rate limited per API key; exact RPM not published.
AI Agents account
agents
plan-based (Free 1; more on paid plans; extra agents available as add-on)
Number of agents is capped per plan.
Training Data Size account
bytes
plan-based (Free 400 KB / Hobby 10 MB / Standard 20 MB / Pro 40 MB)
Total size of training sources per account is capped per plan.

Policies

Credit-Based Metering
Usage is governed by monthly message credits that reset each billing cycle; auto-recharge add-on credits can extend capacity.
Tiered Limits
Credit allotments, agent counts, training size, and feature access (including API access) increase with the subscription tier.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses and honor any Retry-After header.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/chatbase-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.