> For the complete documentation index, see [llms.txt](https://docs.orbitfin.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.orbitfin.ai/part-4-pricing-and-packaging/4.3-agent-consumption.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.orbitfin.ai/part-4-pricing-and-packaging/4.3-agent-consumption.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.