4.3 Agent consumption

Running agents and workflows draws on consumption. Each subscription includes a base allowance of consumption for everyday use; usage beyond that allowance is billed as additional consumption. This is the usage-based part of the pricing model, separate from the fixed subscription fee.

How it works. Consumption is measured in credits — the unit in which the platform's work is counted. Running an agent, processing documents, and executing a workflow each draw credits. A subscription's base allowance is an amount of included credits; when usage exceeds it, additional consumption applies.

What's covered by the allowance. Normal day-to-day research — querying the data and running agents as part of regular work — is designed to sit within the included allowance. Consumption beyond the subscription applies to higher-volume use, such as running automated workflows across a large universe continuously.

How cost scales. Consumption is proportional to usage: the more work a firm has the platform do, the more it draws. Light use stays within the allowance; heavy or large-scale automation draws additional consumption.

Programmatic access at volume. For enterprise firms connecting Orbit into their own systems through the API or MCP at organisational scale, that access is itself consumption-based, as described in 4.2. Access for an individual user's own work is included in the subscription; high-volume programmatic access draws on consumption.

Credit allowances, what each kind of work draws, and pricing for additional consumption are configured with the Orbit team, based on a firm's scale, workflows, coverage, and any programmatic access.