--- title: "Billing" description: "Fund managed agent work with prepaid credits and inspect usage by model and task." canonical_url: "https://hoplite.sh/docs/workspace/billing" markdown_url: "https://hoplite.sh/docs/workspace/billing.md" --- # Billing URL: /docs/workspace/billing LLM index: /llms.txt Description: Fund managed agent work with prepaid credits and inspect usage by model and task. Related: /docs/threads/cost, /docs/agent/models, /docs/workspace # Billing Hoplite bills on **prepaid credits**. Your workspace holds a credit balance; agent runs draw it down based on the tokens they actually use, at per-model rates. ## Free plan Free workspaces receive **140 credits each month** and can have up to **two projects**. Up to 60 of the included credits can be used per UTC day; purchased prepaid credits remain available after that daily included-credit ceiling is reached. A project can contain multiple repositories, so the limit counts projects rather than repositories attached to them. ## Credits One credit represents US$1 of billable usage. The billing page under **Settings → Workspace → Billing** shows: | Balance | Meaning | | --- | --- | | **Available** | What you can spend right now | | **Held** | Credits reserved by in-flight runs, released back (minus actual usage) when they finish | | **Granted / used** | Lifetime totals, including any starter grant | ## Top-ups Buy credits through Stripe checkout from the billing page; a Stripe billing portal handles receipts and payment methods. If a run stalls on an empty balance, an **Add credits** dialog appears right in the thread so you can top up and retry without losing your place. You can also [commit and push the run's uncommitted edits](/docs/threads/run#save-work-after-an-out-of-credits-stop) before topping up. ## Free signup and Pro trials On hosted Hoplite, enrolling a newly created workspace in the Free plan opens a Stripe setup checkout for a billing address and card. This saves the payment method without charging it during Free enrollment. Prepaid cards are not accepted; this is separate from Hoplite's **prepaid credits**, which are the workspace balance used for agent runs. Existing Free workspaces and workspaces downgrading from a paid plan do not repeat the enrollment gate, and local or self-hosted deployments do not use the hosted signup flow. Eligible Free workspaces can start a one-time **14-day Pro trial** for up to three seats. Billing offers the trial only while the offer is active and the workspace has no subscription or previous trial history. A trial's included credits are granted for one seat whatever its seat count, and are subject to a per-UTC-day ceiling; purchased prepaid credits are never capped. Each card can start one trial: a trial started with a card that already ran one is cancelled. Plus is still in development and is not available yet. Hosted Hoplite offers Free and Pro to new purchasers; existing Scale subscriptions remain supported but Scale is no longer offered for new purchases. ## Plans, seats, and subscription changes Owners and admins preview plan, billing-interval, and paid-seat changes before applying them. Changes that take effect immediately — including a trial conversion — open a hosted Stripe confirmation page; ending a trial this way ends it immediately, and any amount shown is due now. Return to Hoplite after Stripe confirms the update so Billing can refresh the authoritative state. No-charge downgrades can be scheduled for renewal. Billing shows the pending change and lets you cancel it to keep the current plan, interval, and seat count. **Change seats** opens a seat-only dialog that keeps the current plan and billing interval. The seat count can't go below the workspace's members plus pending invitations, and the dialog shows the new total before you confirm. While a scheduled change is pending, cancel it before adding seats; removing seats replaces it. A pending renewal change must be cancelled before a different immediate change can be confirmed. ## After access expires Projects, threads, history, settings, and billing remain readable after subscription access expires or the seat limit is exceeded. Owners can restore access from Billing. New cloud runs and resumptions are blocked, and active cloud runs are cancelled after access ends. Automation triggers, review-loop passes, and preview starts or resumes are also blocked. An already-active preview is not proactively stopped solely by the billing transition. Explicit local-agent threads remain usable. ## What's metered Each model call records input, output, cached, and reasoning tokens with its provider, model, run, and cost. Reasoning tokens are billed as output. [Model routing](/docs/agent/models) determines whether a call uses workspace credits, a connected subscription, or your provider key. Hoplite pays for the [Slack](/docs/integrations/slack) and iMessage assistant's own conversation, so it draws no workspace credits and never uses a member's subscription or your provider keys. It has a daily limit per person and per workspace; when one is reached, the assistant replies with when it resets. Coding threads the assistant starts or messages are billed normally. Sandbox charges are shown only when the provider supplies itemized workspace billing. Daytona records can arrive up to 48 hours late, so a deleted workspace may retain **Pending** VM cost while charges settle. Modal does not supply the per-workspace records required for this attribution; Hoplite shows metering as unavailable rather than an authoritative zero. ## ChatGPT subscription models Calls routed through your connected ChatGPT subscription use that plan and incur zero Hoplite workspace-credit cost. Selecting an OpenAI model alone does not guarantee that route: eligible calls can use platform billing or BYOK instead. Check the payer in the thread's cost breakdown or Usage, and see [model routing](/docs/agent/models#automatic-chatgpt-api-routing) for eligibility and fallback behavior. Automatic context compaction normally appears in usage attribution with zero workspace-credit cost because Hoplite runs that summarization on a platform-funded model. If platform summarizer resolution fails, compaction falls back to the thread's session model and follows that model's normal workspace-credit, BYOK, or ChatGPT-subscription attribution. ## Usage **Settings → Workspace → Usage** charts spend by model per day or week and breaks it down by member, so you can see exactly where credits go. Owners can also break it down by project and open a member's projects and threads, and **Export CSV** downloads the selected period. Usage tracking is available on Pro and Scale. Owners and admins can also configure **Settings → Workspace → Billing → Usage limit**. When enabled, this is a monthly cap on on-demand workspace usage: Hoplite stops a new run before its credit hold would push the workspace over the limit. Disable the policy to remove the cap, or raise it and send the message again; the usage limit does not add credits to the workspace balance. ## Cost per thread Spend is also visible where the work happens. Each thread's context-gauge card shows running cost, attributes usage to individual runs, and marks runs billed to your own provider keys with a BYOK badge — see [Track cost](/docs/threads/cost). Compatible Anthropic and OpenAI provider keys are configured under **Settings → Workspace → Models** when BYOK is enabled. ## Sitemap Sitemap discovery is not enabled for this deployment.