> ## Documentation Index
> Fetch the complete documentation index at: https://docs.apollospace.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# How Apollo Space pricing works

> The billing mechanism explained for someone evaluating Apollo Space, before you're inside the app: Stars, plans, packs, and caps — and where the actual dollar figures live.

<Note>
  **This page explains the mechanism, not the price list.** Apollo Space is in early
  access and the current plan prices, Star allotments, and pack sizes live in **Settings
  → Billing** inside the app, or on the public pricing page — not duplicated here, so
  this page never goes stale the moment a number changes. What follows is genuinely
  useful before you sign up: how the billing model is structured and what determines
  whether it fits your usage.
</Note>

## The short version

Apollo Space charges for **usage**, not for a seat. Every billable action — an LLM call
inside an agent conversation, a public web search, a WhatsApp or email send, an
enrichment/scraping call — draws from your organization's **Stars** balance. There is no
per-user license fee layered on top of that; inviting a teammate costs nothing, only
their actual usage does.

## One wallet, two ways to fund it

<CardGroup cols={2}>
  <Card title="Monthly plan (subscription)" icon="calendar">
    A recurring monthly Stars credit, sized to the plan you choose, renewing with your
    billing cycle. Unused monthly credit **expires** at the end of the period — it's
    built to cover typical usage, not to bank up.
  </Card>

  <Card title="One-time packs (top-ups)" icon="box">
    A Stars purchase you make on demand, in different sizes. It **never expires** — it
    sits available until consumed, independent of your subscription status.
  </Card>
</CardGroup>

When a billable action happens, Apollo Space draws from the **monthly** balance first
(because it expires) and only then from the **pack** balance. Full mechanism: [Stars](/en/billing/stars).

## What decides the right plan size

Plans scale along three dimensions, not just a flat tier ladder:

| Dimension | What changes |
| - | - |
| **Monthly Stars included** | Sized to cover typical monthly usage at that tier |
| **Unlocked features** | Higher tiers add capabilities like custom reporting, more simultaneous integrations, SSO |
| **Support** | Self-serve on base plans, a dedicated SLA on enterprise plans |

The exact allotments and prices per tier are in-app and on the public pricing page,
because — as with any usage-based product — they're the number most likely to change
as the platform evolves. What doesn't change is the shape: pick the plan that covers
your typical month, keep a pack on hand for spikes, and avoid using a pack as a
permanent substitute for a right-sized plan (packs price worse per-Star at small
volumes than a plan built for that volume).

## Spending caps — the budget guardrail, before you even ask for one

A common evaluator question: "what stops an agent from running away with cost?" Apollo
Space checks budget at up to four layers before any billable call executes — wallet
balance, then an optional monthly org cap, an optional daily per-agent cap, and an
optional monthly per-user-per-agent cap. Any layer you don't configure simply doesn't
block anything; the wallet-balance check alone already puts a hard ceiling on total
exposure. Full detail: [Spending Caps](/en/billing/caps).

## What's genuinely free

* Inviting teammates — you only pay for what they actually use, not a seat fee.
* Most Composio-connected tool calls.
* The welcome bonus every new account receives — sized to cover initial exploration
  without needing a plan or a pack first.

## Third-party vendor costs — BYO-key, no markup arbitrage

For most external vendors that agents call on your behalf (Tavily for search, Twilio
for WhatsApp/SMS, Apify for scraping), you connect **your own account**. The vendor
invoices you directly — Apollo Space isn't a billing intermediary reselling vendor
capacity at a markup. The Stars deducted for these calls are an internal usage counter
that feeds the caps system, not a hidden vendor margin.

## Where to get the actual numbers

<CardGroup cols={2}>
  <Card title="In-app" icon="gauge-high">
    **Settings → Billing** inside the app shows the live plan comparison, current
    pricing, and your organization's real-time Stars balance across both compartments.
  </Card>

  <Card title="Public pricing page" icon="globe">
    The current plan tiers and prices are published on Apollo Space's public pricing
    page — the source of truth for anyone evaluating before signing up.
  </Card>
</CardGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Stars — overview" icon="star" href="/en/billing/stars">
    The wallet mechanism in full detail.
  </Card>

  <Card title="Plans and packs" icon="box" href="/en/billing/plans-and-packs">
    How subscriptions and top-ups work, upgrade/downgrade/cancellation rules.
  </Card>

  <Card title="Spending caps" icon="gauge-high" href="/en/billing/caps">
    Configuring hard limits per org, per agent, and per user.
  </Card>

  <Card title="Agents" icon="robot" href="/en/concepts/agents">
    What draws from the wallet in the first place — the anatomy of an agent's budget.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.