Linkup · Rate Limits

Linkup So Rate Limits

Linkup applies per-account throttling on its API and returns HTTP 429 when a client exceeds its allowed request rate. Spend is governed primarily by a credits balance rather than fixed published RPM/RPS tiers: a 402 Payment Required is returned when credits are exhausted. The asynchronous Research endpoint must be polled no faster than roughly once per second or the poll is rate-limited. Specific per-account RPM/RPS values are not publicly reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests and credits.

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

Tagged areas include AI, LLM, Web Search, Grounding, and RAG.

3 Limits Throttle: 429
AILLMWeb SearchGroundingRAGRate LimitingQuotasThrottling

Limits

Requests Per Account account
requests
see provider documentation
Per-account request throttling; exceeding it returns HTTP 429.
Credits Balance account
credits
account credit balance
Calls consume credits; exhausting credits returns HTTP 402 Payment Required.
Research Polling account
requests
~1 poll per second
Polling GET /research/{id} faster than about once per second is rate-limited.

Policies

Credit-Governed Usage
Usage is metered against a prepaid/free credit balance rather than fixed RPM tiers.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and poll async research tasks no faster than once per second.

Sources