Skip to main content
Every API request and MCP tool call consumes tasks — the unit Sacra uses to meter usage across all plan tiers. Each plan includes an allocation of tasks, and usage beyond that allocation is billed as overages up to a defined maximum.

​
What is a task?

A task is consumed each time you query a company. Requests that touch a single company consume 1 task. Requests that query multiple companies at once (such as a batch news or events call) consume 1 task per company queried, with a minimum of 1 task per request.
A /news request for 5 companies at once consumes 5 tasks.
Agent and MCP usage follow the same model: tasks are consumed for initiating a request, executing MCP tool calls, and querying companies. Agents often perform multiple tool calls and company lookups in order to complete a single request, so more complex workflows will consume more tasks than simple requests. Tasks are shared across all Sacra products and interfaces, including the Sacra web application, API, MCP integrations, and Sacra Agent. This includes both programmatic usage and end-user activity.

​
Tasks by plan

For a full breakdown of what’s included in each plan, see Pricing.

​
Overages

After exhausting your included tasks, requests continue at $0.05 per additional task. Overages accumulate until either your task limit or your charge limit is reached — whichever comes first. Once you reach your task limit, requests will be blocked until the next billing cycle. Once you reach your charge limit, overage charges stop accruing but you can continue making requests until you reach your task limit.
For most customers the task limit is reached before the charge limit. The charge limit is primarily relevant to Platform customers with custom high-volume task allocations.