Landbase Rate Limits
Landbase has no rate-limit page in its documentation, but it does publish real numbers — they are scattered across the CLI guide, the contacts-import reference and, most usefully, the Agent Skill Landbase ships to Claude Code and Codex, which states the concurrency ceiling and the client's retry behaviour outright. The runtime signal is a 429 with Retry-After, surfaced to the caller as a RATE_LIMITED error carrying meta.retry_after_seconds. Quota, as opposed to rate, is enforced commercially in credits rather than in requests — see plans/landbase-plans-pricing.yml.
Landbase Rate Limits is the machine-readable rate-limit profile for Landbase on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions, measuring concurrent_runs, leads_per_batch, batches_per_minute, and guidance.
Limit state is signalled in the retry_after, ratelimit_limit, ratelimit_remaining, and ratelimit_reset response headers, and an exhausted limit returns HTTP 429.
The profile also includes response codes documented for throttled and edge_timeout.
Tagged areas include Company, Go-To-Market, Sales, Marketing, and B2B Data.
retry_afterratelimit_limitratelimit_remainingratelimit_reset
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.