# Pricing

Source: https://docs.generalaugment.com/pricing/
Description: GA plan limits and launch packaging.

General Augment pricing is built around **agent turns**, not raw stored messages. An
agent turn is one app/user request plus one assistant result through `/v1/responses`,
in-app chat, WhatsApp, SMS, Telegram, or an app-owned scheduled/background job that
calls `/v1/responses`.
Stripe Meter export uses agent-turn events for the customer-facing usage meter; stored
message events remain internal conversation/history accounting.

## V1 Self-Serve Launch Packaging

This is the GA public rate card for implementation, self-serve onboarding, and customer
launch packets.

| Plan | Price | Included MAU | Included agent turns | Tools | Logs | Support |
| --- | ---: | ---: | ---: | ---: | --- | --- |
| Free | $0/month | 100 | 3,000/month | 5 | 7 days | community |
| Build | $20/month | 500 | 10,000/month | 10 | 14 days | email |
| Pro | $79/month | 5,000 | 50,000/month | 50 | 60 days | priority email |
| Team | $249/month | 10,000 | 100,000/month | 100 | 90 days | priority email |
| Enterprise | Custom | Custom | Custom | Custom | Custom | signed agreement |

`Logs` is the default customer-facing lookup window for project message logs and trace
drilldowns through the dashboard and admin APIs. Usage rollups for billing
reconciliation are separate from the raw log/trace lookup window.

Current usage-credit behavior for configured Stripe tenants:

| Plan | Credit grant behavior | Balance behavior |
| --- | --- | --- |
| Free | self-serve signup grants the first free project a `$2.50` one-time promotional usage credit from the shared pricing tier definition | hard stop at zero funded balance with credit billing enabled for the funded sandbox |
| Build | paid invoice or subscription activation webhook grants `$25` of `subscription_included` credits for the billing period from the shared pricing tier definition | paid top-up Checkout can add prepaid credits |
| Pro | paid invoice or subscription activation webhook grants `$100` of `subscription_included` credits for the billing period from the shared pricing tier definition | paid top-up Checkout can add prepaid credits |
| Team | paid invoice or subscription activation webhook grants `$350` of `subscription_included` credits for the billing period from the shared pricing tier definition | paid top-up Checkout can add prepaid credits |
| Enterprise | custom grant, invoice, or commit terms | custom balance, BYOK, and support policy |

This V1 public rate card is still gated by the commercial readiness boundary: live
production Price IDs, Stripe secrets, checkout/webhook smoke proof, purchase-order
workflows, and customer billing policy checks must be attached before a tenant treats
public card collection as launch-ready.

Credit grants are General Augment retail credits, not raw provider-cost dollars. When
credit billing is enabled and no active balance remains, cost-bearing platform-funded
`/v1/responses` calls fail with a stable `402 insufficient_credits`.

V1 overage policy after included turns:

| Usage | V1 overage rate |
| --- | ---: |
| Build balanced Gemini agent turns | $3.00 per 1,000 turns |
| Pro balanced Gemini agent turns | $2.00 per 1,000 turns |
| Team balanced Gemini agent turns | $1.50 per 1,000 turns |
| Complex/Pro model usage | provider cost plus margin |
| SMS/WhatsApp/RCS | provider pass-through plus platform margin |
| Telegram | no provider delivery cost; still counts as agent turns |

Usage based pricing starts from agent turns. Production tenants bring their own
model-provider, channel-provider, and cost-bearing tool/API
credentials by default. General Augment bills for orchestration, governance, memory,
traces, dashboard/CLI, approval/audit controls, and support scope; provider bills stay
with the tenant unless a pooled-capacity agreement explicitly says otherwise.

## No over-billing controls

General Augment is designed to stop before unfunded provider spend is created.

- Cost-bearing `/v1/responses` calls reserve credit before the runtime starts. If no
active funded balance is available, the call returns `402 insufficient_credits`
instead of running the model.
- Settled charges come from the completed turn. If the actual turn burns less than the
reservation, the ledger releases the unused amount through a lower-burn refund entry.
- Runtime failures release the reservation through a cancellation entry, so a failed
turn does not remain as a customer charge.
- Public self-serve plans keep finite daily agent-turn, tool-call, and token gates.
Invalid runtime overrides are ignored rather than silently removing spend controls.
- Auto top-up can be configured for a tenant, but automatic off-session charges remain
disabled until that tenant explicitly opts in and accepts the failed-payment, retry,
tax, refund, and expiry policy.
- Tenant-paid provider usage stays separate from General Augment billing unless a signed
pooled-capacity agreement explicitly includes platform-managed capacity.

Usage limits are enforced before a turn reaches the runtime. When a project hits a daily
limit, users receive a friendly retry-later response and developers see the usage state
in the portal.

The backend enforces daily equivalents of public-plan usage so Free, Build, Pro, and Team
tenants cannot accidentally create an unlimited spend path:

| Plan | Agent turns/day | Tool calls/day | Tokens/day | Agents | Seats |
| --- | ---: | ---: | ---: | ---: | ---: |
| Free | 100 | 50 | 500,000 | 1 | 1 |
| Build | 300 | 750 | 1,500,000 | 2 | 1 |
| Pro | 1,500 | 5,000 | 10,000,000 | 5 | 3 |
| Team | 3,500 | 15,000 | 20,000,000 | 10 | 5 |
| Enterprise | Custom | Custom | Custom | Custom | Custom |

Operators can tune runtime values through validated configuration, but public
self-serve plans must keep finite `agent_turns_per_day`, `tool_calls_per_day`, and
`tokens_per_day` gates. The same pricing tier definition owns included and promotional
usage-credit amounts, so webhook credit grants and public pricing copy stay aligned.

## Commercial Billing

General Augment has
usage events, daily rollups, project usage APIs, budget gates, usage-credit grants,
reservations, settlement, lower-burn refunds, cancellation releases, dashboard credit
state, billing exports, billing webhooks, hosted Build/Pro/Team Checkout, customer-paid credit
top-up Checkout, Customer Portal endpoints when Stripe is configured, stored
invoice/payment-failure event history, subscription-included grants, paid-top-up grants,
Stripe Tax/Smart Retry sandbox proof, and optional Stripe meter export when configured.
Customer launch packets should attach the matching live-mode Stripe readiness artifact
when live checkout is in scope.

Auto top-up settings, attempt history, and the preflight worker are implemented. The
worker records threshold crossings and blocker codes, but automatic off-session
PaymentIntent charges remain disabled unless the tenant explicitly opts in and the
failed-payment, retry, tax, refund, and expiry policy is accepted.

Production billing mechanism, effective rates, included usage, overages, and payment
terms are handled through the selected plan, checkout, explicit commercial agreement,
or manual operator process. Tenant-paid provider usage is separate from General Augment
revenue unless a pooled-capacity agreement says otherwise.

See [Concepts](/getting-started/concepts/) for usage event definitions and
[Developer Support](/guides/support/) for GA support posture.