> ## 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. # Stars — Apollo Space's currency > How your organization's balance works: Stars, monthly credits, add-on packages, and where the balance is spent. Your agents are working while you aren't watching. The Chief of Staff sends a follow-up over WhatsApp, Scout runs a handful of web searches to enrich a lead, an enrichment actor pulls a company's contacts — each action costing real money, to a different vendor, in a different unit. Stars turn that sprawl into one number. You see what your company's AI is spending and you set the limits, without ever reconciling a vendor invoice yourself. ## What are Stars **Stars (★)** are Apollo Space's internal currency. Every billable action — a public search, an outbound email, a WhatsApp message, an external tool execution — draws Stars from your organization's wallet. Instead of reconciling the heterogeneous costs of each vendor (LLM tokens, Twilio per-country cents, Tavily per call), Apollo Space gives you a single unit to track all platform usage. ## The wallet has two compartments Included in your **subscription plan**. Renews automatically every month alongside your plan billing cycle. The monthly balance **expires** at the end of the period — unused credits do not roll over to the next month. It is designed to cover typical monthly usage, not to accumulate. **When to use:** covers predictable, recurring usage by your team. Purchased on demand (top-up) in Settings → Billing. Available in different sizes — the larger the package, the better the per-Star rate. Package balance **never expires** — it stays available until consumed, regardless of plan renewals or cancellations. **When to use:** seasonal spikes, a safety buffer, or using Apollo Space without an active monthly subscription. **Deduction order:** when a billable call is made, Apollo Space debits **the Monthly balance first** (because it expires) and only then the Package balance. You can see each compartment's balance separately under the **Billing** tab in your org settings. ## Where Stars are spent Every time an agent triggers a capability with an underlying cost: | Category | Examples | | ------------------------- | ------------------------------------------------------------------------------ | | **LLM** | Language model tokens — every agent conversation goes through here | | **Public search** | Web searches performed by [Scout](/en/agents/scout) | | **Outbound** | WhatsApp and SMS via [Twilio](/en/integrations/whatsapp) | | **Enrichment + scraping** | [Apify](/en/integrations/apify) actors — map searches, site contact extraction | | **External integrations** | [Composio](/en/integrations/composio) tools that carry a cost (most are free) | The up-to-date pricing table is available in **Billing → Usage by category** inside the app. Rates may change in line with vendor agreements — always communicated in advance. ## How Apollo Space protects your budget Before each billable call, Apollo Space checks at **multiple levels** whether the action fits within the org's budget: ```mermaid theme={null} flowchart TD A[Agent wants to perform a billable action] --> B{Wallet balance > 0?} B -->|No| Z1[Blocked: insufficient balance] B -->|Yes| C{Org cap OK?} C -->|Exceeded| Z2[Blocked: org cap] C -->|OK| D{Agent cap OK?} D -->|Exceeded| Z3[Blocked: agent cap] D -->|OK| E{User cap OK?} E -->|Exceeded| Z4[Blocked: user cap] E -->|OK| F[Execute action] F --> G[Debit from Monthly compartment first] G --> H[If needed, debit from Package] H --> I[Record in append-only history] ``` If the wallet is empty, no new billable calls are authorized — regardless of agent or user. You can set **spending limits** per organization, per agent, and per user. Once a cap is reached, Apollo Space blocks new calls in that dimension without affecting the others. Details on each cap level are in [Spending Caps](/en/billing/caps). ## BYO-key — you own the vendor account For most external vendors (Tavily, Twilio, Apify), you connect **your own account**. Here's why: * The **actual vendor invoice** goes directly to you — Apollo Space is not a payment intermediary * You keep control of your credentials and can revoke them at any time * The Star deduction inside Apollo Space is an **internal counter** — it serves the caps system and gives you a unified view of consumption In short: you are never dependent on Apollo Space credit to use external vendors. ## History and audit trail Every wallet transaction — credit received, usage debit, manual adjustment — creates a row in the history log, **append-only**. Nothing is deleted or edited retroactively. The result: you can answer "what happened to my balance on day X?" with precision at any time. The history is **isolated per organization** — no one from another org can see yours, nor can internal Apollo Space operators without explicit privilege. See [Multi-tenant](/en/trust/multi-tenant) for the isolation model. ## Refunds and adjustments * **Refunds** (disputed charge, retroactive plan cancellation) are processed automatically when the event arrives via Stripe * **Manual adjustments** (welcome bonus, promotional credit, incident remediation) are made by the support team with a full trail in the history log ## Next steps Overview of available plans and how to purchase packs. How to configure limits per org, per agent, or per user. How balances are isolated between organizations. What connects and what does (or doesn't) draw from the balance.