specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Bland AI
providerId: bland-ai
created: '2026-05-08'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-08, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-08'
reconciled: true
tags:
- AI
- Voice
- Agents
- Phone
- Realtime
- Rate Limiting
- Quotas
- Throttling
description: >-
  Bland AI rate-limits voice agent usage primarily through plan-based concurrent call caps and
  daily call quotas. HTTP rate limits beyond standard 429 are not publicly documented;
  enterprise contracts can lift concurrency caps.
notes: Concurrency and daily call caps are documented per plan; enterprise plans remove caps.
sources:
- https://www.bland.ai/pricing
- https://docs.bland.ai/
responseCodes:
  throttled: 429
limits:
- name: Concurrent Calls (Start)
  scope: account
  metric: concurrent_calls
  limit: 10
  notes: Start tier concurrency cap.
- name: Concurrent Calls (Build)
  scope: account
  metric: concurrent_calls
  limit: 50
  notes: Build tier concurrency cap.
- name: Concurrent Calls (Scale)
  scope: account
  metric: concurrent_calls
  limit: 100
  notes: Scale tier concurrency cap.
- name: Daily Calls (Start)
  scope: account
  metric: calls_per_day
  limit: 100
  notes: Start tier daily call cap.
- name: Daily Calls (Build)
  scope: account
  metric: calls_per_day
  limit: 2000
  notes: Build tier daily call cap.
- name: Daily Calls (Scale)
  scope: account
  metric: calls_per_day
  limit: 5000
  notes: Scale tier daily call cap.
- name: Voice Clones (Start)
  scope: account
  metric: voice_clones
  limit: 1
- name: Voice Clones (Build)
  scope: account
  metric: voice_clones
  limit: 5
- name: Voice Clones (Scale)
  scope: account
  metric: voice_clones
  limit: 15
policies:
- name: Backoff Strategy
  description: Clients should implement exponential backoff with jitter and honor any Retry-After header.
- name: Concurrency Planning
  description: Plan to upgrade tiers when concurrent call demand approaches the documented cap.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com