Limits & usage

REST and MCP share one account allowance across all connected clients. These initial Pro pilot limits apply equally to individual and business integrations. A designated business Pro account does not receive a separate or larger allowance.

Request budget

Limit	Initial pilot allowance
Data calls per account	100 per day
Data calls per account per minute	6
Daily reset	Midnight in Africa/Dar_es_Salaam
Keyword searches	Also consume the account’s shared Fisk Web search allowance
Minimum Pro keyword-search interval	10 seconds

Fisk also applies a shared pilot capacity ceiling. A request can be limited even when the account has remaining allowance. The initial shared ceiling is 1,000 data calls per day and 30 per minute across the pilot.

Concurrent requests and calls through additional clients use the same counters. API access is not a way to bypass account limits.

Response bounds

Operation	Maximum
Company search	20 companies
Documents, financials or events	20 rows per request
Paged-list offset	100
Document page	6,000 text characters
Document keyword search	5 excerpts, at most 2,000 characters each
Event date range	366 days
MCP JSON request body	16 KB

There is no unrestricted archive crawl, bulk export or JSON-RPC batching in this pilot.

Read your allowance

Successful results include daily quota metadata:

{
  "quota": {
    "limit": 100,
    "remaining": 99
  }
}

This is the connector allowance, not a separate balance for each MCP client. Search can additionally fail on its shared search allowance.

When a limit is reached

REST returns HTTP 429, a stable error code and Retry-After when supplied. MCP tool calls return an error with the corresponding code and retry context.

Stop making dependent calls until the wait has elapsed. Do not switch accounts, clients or transports to work around the limit.

See errors and retries for specific handling.