For the complete documentation index, see llms.txt. This page is also available as Markdown.

4.2 What's included: the subscription

The foundation of Orbit's pricing is a subscription — a recurring fee for access to the platform. It is the predictable, pay-for-access part of the model: what a firm has, before any question of how much it runs. A subscription gives a firm the connected data, the application, and the means to reach both, and it comes in two forms depending on how a firm works.

What every subscription includes is the platform itself. That means the Knowledge Base — the global corpus, the entity master, and the structured and document layers described in Part 2 — and Orbit Insight, the application through which a team queries it, runs the off-the-shelf agents and use-case library, and builds its own agents. It also includes the access surfaces: as well as working in the application, a subscriber can reach Orbit through its API and through MCP, so the platform's data and agents can be used inside a firm's own tools and AI systems, not only in Orbit's interface. A subscription is, in short, full access to the platform and everything needed to put it to work.

Every subscription also includes a base allowance of agent consumption. Running agents and workflows draws on consumption — the subject of 4.3 — but a subscription does not start at zero. It comes with an allowance built in, enough to use the agents and use cases as part of normal work, so that ordinary day-to-day use is covered by the subscription itself. Consumption pricing applies on top of that allowance, when usage goes beyond it; it is not a charge on every action from the first one.

The subscription comes in two forms.

Individual subscription. Priced per user, this is the working subscription for the people doing research — analysts, PMs, quants. It includes everything above: full access to the data and the application, the API and MCP surfaces, and a base allowance of agent consumption sufficient for an individual's normal work. For a single user putting Orbit to work, including connecting it into their own tools, the individual subscription is self-contained — access and everyday use, in one fee.

Enterprise subscription. For firms operating at scale — many users, and in particular firms connecting Orbit into their own environment programmatically at volume — the subscription takes an enterprise form. The distinction that matters here is volume of access. An individual subscription includes MCP and API access for a person's own use; but a firm that wants to connect Orbit into its systems at scale — for example, feeding Orbit's data and agents into its own deployment of a general-purpose AI assistant across the organisation through MCP — is generating load well beyond individual use, and at that scale the programmatic access itself becomes consumption-based rather than bundled. The enterprise subscription is the framework for that: platform access across an organisation, with high-volume MCP and API usage treated as consumption, sized and priced with the Orbit team.

The shape to take away is that the subscription is what a firm has — access to the whole platform, the surfaces to reach it, and enough included consumption to work normally. What a firm runs beyond that, and what it builds at scale, are the next two chapters. Pricing for either form of subscription is set with the Orbit team, because the right configuration — how many users, what volume of access, what scale — depends on how a firm intends to use the platform.

Last updated