Pricing reference

A source-generated pricing reference, not an observation of the running deployment. Code-default billing rails distinguish default-off gates from live activation. Repricing follows the deployment's effective instant; native quotes may also resolve pricing-book overrides. Inspect a provider tool's estimate and basis with oxygen tools get <tool-id> --view pricing --json, or preview the exact request before spending.

What a credit is worth

Plans

Included credits are face value ($1 = 100 credits) plus the plan's volume bonus, which is already counted in the column. An existing subscriber to a plan with a volume bonus receives that volume bonus from their next renewal. For the separate agency partner bonus and its first-grant timing, see Billing. Plan prices are before tax. New yearly plans commit for twelve months and pay the discounted monthly amount, never the year upfront. The term total is twelve actual rounded monthly payments; credits arrive after each paid monthly invoice. Yearly commitments renew annually unless renewal is turned off; monthly payments continue until the term ends. They are offered when annual_monthly_billing_available is true; existing prepaid yearly subscriptions keep their paid periods and monthly credit slices (yearly billing).

Trial, grants, and grace

Credit top-ups

These are source comparisons, not current production quotes. With the repricing epoch unset, the source-default packs are:

A custom top-up runs from 800 credits to 100,000 credits in steps of 100. Purchased credits stack like plan grants and do not expire. Without an amount, oxygen billing topup only reads a quote. Selecting credits or a pack creates Stripe Checkout; payment is separate. Top-up tax treatment is not established by this reference or the quote: review the tax and final total in Checkout.

From the 2026-09 repricing's effective date a top-up costs $1.30 per 100 credits and these packs are sold instead; oxygen billing topup --json reports the rate and packs in force, and the ones scheduled once the date is set.

AI columns, Copilot, and Agents

Copilot and Agent turns bill managed inference against the same credit balance. A Copilot session has no budget to set: a person is watching it and can stop any turn, and the platform backstop bounds each attended turn. An Agent run spends within the max_credits approved when it starts. On your own AI model credential the model provider bills inference directly and OXYGEN charges no inference credits or platform fee. Managed web-grounding calls and workflow steps retain their separate charges. Native data-provider calls on your own key instead pay the applicable 0.05-credit OXYGEN platform fee per successful call, including successful misses, separately from vendor charges. See billing and own-key fees and retries.

Enrichment and research

These are the sheet's typical values. The price that actually bills is the one on the operation descriptor, which varies by provider and request shape — read it with oxygen tools get <tool-id> --json, or preview the exact request with a dry run before spending.

Email infrastructure

A Google Workspace and a Microsoft 365 inbox share one price, and an Azure tenant is one flat monthly charge for its domain whatever it carries; from the 2026-09 repricing's effective date every inbox on it also holds the 100-credit ($1.00) monthly connection. Staff can re-price these rows in the pricing book, so the pricing page and oxygen managed-inboxes list --json (under prices) show the price in force, and every order preview quotes the exact order before anything is bought. A domain holds at most 5 Google Workspace or Microsoft 365 inboxes, or 100 on an Azure tenant.

Sending seats

These dollar seats apply to the legacy sending_seats model. Read oxygen billing estimate --json for sender_billing: credit_reservations uses connected-account credits instead, though every sending account connects only on a paid plan, and oxygen billing seats --json reports status: seats_retired. The legacy gate (OXYGEN_SENDING_SEAT_GATE_ENABLED) enforces purchased or grandfathered seats while that model applies. oxygen billing seats --json reports the price, what is purchased, what is grandfathered, what is connected, and what is left. This reference does not observe production flag state. Before authorization, oxygen billing commitments --view connection-prices --json reports current deployment credit prices and billing timing for LinkedIn, WhatsApp, X and sending-mailbox connections, separate from this dollar-seat table.

Seats belong to the billing owner. A workspace linked to another organization's plan with oxygen orgs billing-link connects senders against that organization's seats and buys them there — oxygen billing seats set inside a linked workspace is refused with shared_billing. An OXYGEN-sold managed mailbox already includes its seat; the email seat above is for a mailbox you bring yourself.

LinkedIn and WhatsApp

Individual LinkedIn actions and WhatsApp message sends are 0 credits. Monthly connected-account prices are separate: inspect oxygen billing commitments --view connection-prices --json before authorizing an account; use oxygen billing commitments --json and oxygen billing seats --json for workspace commitments and coverage. Workflow step charges follow the workflow section below.

Voice

Voice settles on the telephony provider's status webhook after the call ends. A connected call bills its talk time, with a started minute counted as a whole one; a call nobody answered costs nothing. There is no separate per-call charge. A rented phone number is priced under connected-account reservations.

Connected-account reservations

When sender_billing is credit_reservations, connected accounts reserve monthly credits on their own monthly anchors instead of occupying dollar sending seats. The reservation model has its own switch and takes effect only after its required repricing epoch is effective. oxygen billing estimate --json reports the workspace's model and current prices; oxygen billing commitments --json lists its commitments. The table shows the code's before/after repricing schedule. The deployment's effective instant, enabled billing path, workspace coverage and any pricing-book override determine the applicable quote. Before authorization, inspect oxygen billing commitments --view connection-prices --json for deployment unit prices and disclosed billing timing for LinkedIn, WhatsApp, X and sending mailboxes. It does not determine workspace coverage or affordability. For a phone number, oxygen voice numbers buy previews the selected number purchase by default. oxygen billing commitments --json lists recorded forward commitments; it is not this cycle's settled debit total.

Workflow automation

The workflow and BYOK rates above are the repriced schedule values, applicable from the deployment's effective instant: 1,000 tool steps cost 50 credits ($0.50). A loop bills its tool steps on every pass and a retried step bills again; previews and dry runs cost nothing. Two older shapes bill differently: an older revision whose code step embeds a durable recipe bills that step like a tool step, and a legacy step-list workflow bills each of its steps. When charged, workflow steps and BYOK platform fees settle in aggregate and count toward the run's max_credits and a trigger's per-delivery ceiling. AI calls on your own model key are not charged the BYOK platform fee.

Read Workflow prices and budget state

Before creating a Workflow, oxygen billing balance --json reports the current step price at automation_actions.credits_per_step (MCP: oxygen_billing_balance). If automation_actions is null, that read did not establish the price. HubSpot sequencer setup previews also return current unit prices under template_preflight.credits.quote; their usage examples are hypothetical, and an unknown total stays unknown.

Legacy included_actions and remaining_actions fields describe an action quota when numeric. Null does not mean unlimited credits or free automation. Current plans bill from workspace credits; available balance, unsettled usage, the run ceiling and any applicable budget policy still constrain admission. overage_enabled: false with null action fields does not create a monthly action allowance. A missing allowance object means its lookup is unavailable.

For an already armed cron, a hard budget refusal skips due slots before creating a run and leaves the trigger armed. Its metadata records scheduler_budget_block_reason and scheduler_budget_blocked_at, and the next scheduled time advances past those slots. A warning policy allows admission. When the applicable window resets or the cap is raised, a later slot can run; skipped slots are not replayed. Automation quota or credit refusals appear as trigger.automationPaused in oxygen workflows get; monthly quota pauses carry a reset time, while credit or unknown refusals carry no promised resume date. Adding credits permits the scheduler to retry a future slot. Manually disabled Workflows remain disabled until explicitly enabled.

Code-default billing rails

These rails default to off in code. Boolean enable switches require exactly true; CREDIT_COMMITMENT_BILLING_KINDS is a comma-separated valid-kind allowlist. An unset or malformed enable switch does not enable the rail. This table does not observe deployed flags, pricing-book overrides or workspace eligibility, and does not claim that these resources are free. A dash means no numeric price is mapped in this table, not a zero quote.

A gate or tracked commitment alone does not prove a payable debit. Inspect oxygen billing commitments --view connection-prices --json for current deployment unit prices and disclosed billing timing for LinkedIn, WhatsApp, X and sending mailboxes; use oxygen billing seats --json for workspace seat coverage, oxygen billing commitments --json for its forward commitments; and oxygen billing allowance --json for settled current-cycle charges. These native reads distinguish the deployed billing path from this source reference.

Default spend ceilings

These are source comparisons with the repricing epoch unset and synthetically in force; they do not observe deployed limits. Spend defaults scale with plan size. An autonomous trigger or table auto-run armed without an explicit cap is backstopped by its plan's default, resolved when it fires; an explicit cap always wins.

The source delivery default is 10% of the paid plan's monthly credits; Free is 50 credits in both comparisons. These source rows do not establish your deployment's limits. Grandfathered plans take 10% of their own monthly credits: Starter 990 (otherwise the Oxygen $99 column), Pro 2,490 (otherwise the Oxygen $199 column), Team 7,490 (otherwise the Oxygen $999 column). Legacy scale plans read the Oxygen $1,999 column, and Enterprise has no implicit trigger-delivery default. oxygen limits show names your plan size and returns every size's values under plan_bands; the web app shows the same values under Settings → Plan limits.

The paired trigger, Agent and daily-guard rows compare the source with the repricing epoch unset and synthetically in force. oxygen limits show reports which value is in force for your workspace. Enterprise uses the $1,999 Agent row: after the switch that is 2,500 credits total and 1,250 for model calls, with no separate contract default.

An Agent run may spend up to its approved max_credits. The plan ceiling above is its default: one run or trigger may carry a higher max_credits when you approve it explicitly (--approve-above-default, or the card in the web app), up to 25,000 credits, and Enterprise uses the $1,999 plan default. The Copilot allowance covers paid work up to its per-call and per-session amounts without an approval card; sends, launches and other external writes always ask, at any price, and one attended Copilot turn is bounded at 3,000 credits on every plan. A dash means no default. The daily spend guard is a runaway backstop, not a spend ceiling: Free has no guard with the epoch unset and a 1,000-credit warning / 5,000-credit block after its effective date; on paid plans it warns at 5x and hard-blocks at 20x the plan's monthly credits spent in one day, monthly reservations and managed mailbox subscriptions do not count toward it, and your own org daily budget replaces it. Run oxygen limits show or oxygen budget list to see the exact credit thresholds for your plan. BYOK daily call caps are monitoring thresholds and warn rather than stop a run unless OXYGEN_BYOK_DAILY_CAPS is set to enforce.

To inspect an Agent trigger's ceiling before creating it, run oxygen limits show --section spend --json (MCP: oxygen_limits_show with {"section":"spend"}). spend_safety_defaults.agent_run_max_total_credits is the current workspace default; agent_run_approved_max_credits is the global 25,000-credit approved maximum. A proposed cap above the default requires the separate approve_above_default approval; reading these fields grants none and creates no trigger. A missing default is unknown. Existing trigger reads report their explicit max_credits and above_default_ceiling_approved_at.

API rate limits

Request rates scale with plan size. Every /api/cli/* call counts against a per-key and a per-workspace total a minute; the operation limits below apply first to the calls a script makes most. Limits guard against runaway loops: they are never sold and never billed.

Windows are fixed: a per-minute limit resets at the start of each minute, an hourly one at the start of each hour. A request over a limit is refused with HTTP 429 and rate_limit_exceeded; wait the seconds in the Retry-After header (also error.details.retry_after_seconds) before retrying. error.details.bucket names the limit that was hit, error.details.limits_url opens the web app's Plan limits page with every plan size's rates, and the CLI exits with code 6. Live AI calls and live tool calls are separate buckets with the same limits. A row budget counts one unit per row a request reads or writes, shared by every key in the workspace; a single-row request still counts toward it but is never refused by it, only by the per-minute rates. Bulk work belongs in a durable table run, which these per-request limits do not pace. oxygen limits show --json returns your plan's rates under api_rate_limits and every plan size's under plan_bands.

Webhook ingress

Inbound webhooks accept more deliveries a minute on bigger plans. The limit applies to each target on its own: a Table webhook endpoint, a workflow or Agent webhook trigger, and the workspace's RB2B receiver. The target and the sender IP are counted separately, and one sender IP may use the whole per-target rate, so a form tool or CRM posting from one address is not held to less. A second endpoint has its own allowance. A delivery counts once however many rows it carries.

Windows are fixed and reset at the start of each minute. A delivery over the limit gets HTTP 429 with a Retry-After header; redeliver after that many seconds. Nothing is written for a refused delivery, so a sender that retries loses nothing. For a steady flow above your plan's rate, batch several rows into one delivery with --items-path on oxygen tables webhook create; a delivery may be up to 1 MB of JSON. A refused delivery is not recorded in oxygen tables webhook deliveries. oxygen limits show --json returns your plan's rate under webhook_ingress, the tables webhook commands report the endpoint's under rate_limit, and a workflow or Agent webhook trigger reports its own under rate_limit in oxygen workflows get, oxygen workflows apply, oxygen agent trigger-create and oxygen agent triggers.

Table and signal limits

Storage, import size, columns per auto-run and the signals feed scale with plan size too. Like the rates above they are guards, never sold and never billed. This table compares source limits with the repricing epoch unset and synthetically in force, not current production limits. A slash shows epoch-unset / post-effective-date values; a pending rows-per-Table capacity test is separate and has no inferred date. Read oxygen limits show --json for deployed plan_bands, storage_capacity and pricing_schedule.

The table publishes source limits before and after the repricing epoch. Applying an epoch also requires each workspace’s persisted tenant guard to be synchronized; a tenant still using its legacy guard has not acquired the new limits. Read oxygen limits show --json for the workspace’s effective guard and usage. The 5-million and 10-million rows-per-Table targets remain held for the capacity test.

CSV and JSONL files stream, so they import up to the file size above. JSON and XLSX files are read whole, so on every plan they stop at 100 MiB; save a larger file as CSV or JSONL. Rows per Table still cap how many rows one import can load.

A request over one of these is refused with an error that names the limit. oxygen limits show --json returns every plan size's values under plan_bands.

Ledger categories

Every credit ledger entry carries one of these 19 categories. oxygen billing usage --json returns them.

Ledger transaction types

What costs nothing