Skip to main content
Rate limits vary by API. The limits below apply to the Agent tier. An overall throughput cap applies across every endpoint, and individual endpoints carry their own sub-limits.
The three Company Data enrichment variants (standard, concise and markdown) draw from a single shared pool of 25,000 requests per month. Calls to any of them count against the same quota.

​
What counts as a request?

Every call to a News Signals, Company Data, List Generation, Alternative Signals or Supporting API endpoint counts as one request. Requests count toward:
  1. The overall throughput limit of 1,000 requests per minute.
  2. The per-endpoint sub-limit for that endpoint, where one applies.
A request that fails validation or returns an error still counts. Requests that are rejected by the rate limiter itself do not. Each Alternative Signals endpoint enforces two independent limits. A burst of more than 100 requests in a minute is throttled even when the monthly quota is far from exhausted.
Usage for all endpoints is charged in credits. Rate limits control request throughput; credit usage controls billing. Staying inside your rate limits does not cap your credit consumption.

​
Handling rate limit responses

When a limit is exceeded, the API returns HTTP 429 Too Many Requests. Build clients to retry with exponential backoff rather than retrying immediately, and spread bulk jobs across the window instead of firing them in a single burst. For the daily and monthly limits, track consumption on your side so long-running pipelines fail gracefully rather than mid-batch.

​
Pricing

Rate limits are separate from pricing. For cost information, see Pricing.

​
Need higher limits?

If you need higher throughput, custom endpoints, de-duplicated feeds, or committed-volume pricing, contact sales@akta.pro with your expected usage volume and requirements.