Billing & credits

Pay-as-you-go credits, top-ups, auto-reload, subscription plans, and enterprise invoicing.

Credits

Conduix bills in credits. 1 credit ≈ $1 of model spend. You buy credits in advance via Stripe, and every successful API call deducts the per-token rate of the model that served the request. Failures don't cost anything.

Watch your balance at /dashboard/billing and your per-model burn at /dashboard/usage.

Topping up

Buy credits one-off via Stripe Checkout. Tier amounts are operator-configured — typical tiers are $10, $50, $100, $500. Each top-up creates a Stripe invoice you can download from /dashboard/billing.

Auto-reload

Skip the "account paused" emails. Configure auto-reload to charge your saved card whenever your balance drops below a threshold:

Threshold

When to trigger (e.g. balance < 50 credits)

Reload amount

How many credits to buy each time

Card

Whichever payment method is on file with Stripe

Auto-reload only runs after the threshold is crossed, never speculatively. Toggle on/off from billing settings.

Subscription plans

Three plans with included credits and feature differences. Full breakdown at /pricing:

Explorer

Free tier — 50 credits to start, no card needed

Builder

Monthly subscription, included credits, higher rate limits

Scale

Higher tier — SSO, audit log retention, priority support

On the Builder and Scale plans, included credits roll into your wallet at the start of each billing period. Excess usage above the included amount draws from your wallet (top-ups, auto-reload, or invoiced).

Enterprise — NET-30 invoicing

For volume customers who need PO numbers, custom MSAs, or DPA paperwork, Conduix offers invoice billing on NET-30 terms instead of card-on-file. Contact sales@conduix.ai — we'll set up the customer record, mode-switch the org to billing_mode = "invoice", and route usage through monthly invoices.

Volume discounts. Custom unit pricing on Builder and Scale plans for committed monthly volume. Tell sales your projected spend and timeline; you'll get a proposal within 2-3 business days.

Spend caps

Hard caps per organization stop runaway spend before it happens. Configured at /dashboard/settings:

Daily cap

Hard ceiling per UTC day

Monthly cap

Hard ceiling per UTC month

Alert threshold

Warn at e.g. 80% of cap before blocking

When a cap is exceeded, requests fail with HTTP 402 spend_cap_exceeded — the provider call never runs. See Governance.

What an "insufficient credits" error looks like

HTTP 402 response

{
  "error": {
    "message": "Insufficient credits. Current balance: 12 credits.",
    "type": "insufficient_quota",
    "code": "insufficient_credits"
  }
}

Top up at /dashboard/billing or set up auto-reload to avoid this.

Cache hits are free

Identical deterministic requests (temperature: 0, same messages, same model) served from cache are not billed. Look for x-conduix-cache: HIT in the response headers.

Models & pricing Observability