Lorikeet · Rate Limits

Lorikeet Rate Limits

Lorikeet does not publish specific API rate-limit values; its authoritative API reference is access-gated and rate limits are typically governed per account/contract. As an enterprise AI support agent, throughput is bounded more by contracted resolution/conversation volume than by a public per-endpoint RPM. Standard HTTP throttling conventions (HTTP 429 with Retry-After and exponential backoff) are assumed for the inbound management API. Outbound tool/action calls Lorikeet makes into your systems are subject to your systems' own limits.

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

It captures 4 rate-limit definitions, measuring requests, events, and jobs.

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

Tagged areas include AI, Customer Support, AI Agent, Rate Limiting, and Quotas.

4 Limits Throttle: 429
AICustomer SupportAI AgentRate LimitingQuotasThrottling

Limits

Conversations API (requests) account
requests
see provider (account/contract governed)
Not publicly documented; governed per account/contract.
Messages API (requests) account
requests
see provider (account/contract governed)
Not publicly documented.
Webhook Deliveries account
events
see provider
Outbound event deliveries; retried on failure per Lorikeet's delivery policy.
Knowledge Ingestion account
jobs
see provider
Ingestion is asynchronous; concurrency governed per account.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429.
Contract-Governed Volume
Effective throughput is bounded by contracted resolution/conversation volume rather than a public per-endpoint RPM.

Sources