Skip to content

Docs / Billing

Billing

Seats, entitlements, spend caps and the Stripe portal — and why inference never appears on our invoice.

We charge for orchestration. We do not charge for inference, and we do not charge for the minutes your own machines spend running your own jobs.

What we never bill for

Tokens. BYOK is the only mode: the agent calls your provider with your key, on your account, and your provider invoices you directly. We are not a reseller and there is no markup, because we are not in the billing path at all. See BYOK.

CI minutes. Jobs run on boxes you own. There is no per-minute meter, no cache egress charge and no static-IP fee. See self-hosted CI.

The seat model

A seat is one AI dev: one concurrent AI-dev runner.

A seat buys Amount
Concurrent AI-dev runners 1
Enrollable servers 3 (inclusive of the AI-dev box)
Queue depth 50 waiting tasks
Code review Full — merge-gating, can drive auto-merge

Boxes are fungible: the two servers beyond the AI-dev box serve CI, tests and review at no extra charge. Enrolling past seats × 3 returns 402 Payment Required rather than silently accepting the box.

Work beyond your concurrency waits in the queue. It is not rejected and it is not billed differently — you are buying parallelism, not permission.

Tiers

Current prices are on the pricing page; this page describes the shape rather than restating numbers that live in one place.

Tier Shape
Solo Self-serve. A graduated ladder — later agents cost more than the first, and the per-agent price levels off at the top band.
Pro Self-serve. Flat price per seat.
Enterprise Custom contract. No self-serve checkout.
OSS Donor Flat monthly donation. Your runners pull the OSS donation queue, not your own work.
OSS Verified Waived. For approved public repositories — see below.
Free Personal accounts only. No AI-dev seats; review is off.

Only Solo and Pro can be bought self-serve. Enterprise is a conversation; OSS Donor goes through the donation flow.

OSS verification

Public repositories can apply for verified OSS status, which waives the bill. Apply from the dashboard. A human reviews it — submitting the application grants nothing, and approval is not automatic. Verified accounts get full review in advisory mode (comments, never a merge gate) and are never metered.

Auto-merge stays opt-in on free and OSS-verified accounts.

Buying and managing

# Start a checkout for N seats (solo or pro only)
curl -X POST https://api.developerz.ai/v1/billing/checkout \
  -H "Authorization: Bearer dev_pat_…" \
  -H "content-type: application/json" \
  -d '{"tier":"pro","seats":3}'

Scope: write:billing (owner or admin). Seats are granted by the Stripe webhook after payment settles, not by the checkout response — so a completed checkout and an active seat are two separate moments, usually seconds apart.

Invoices, cards and cancellation live in the Stripe billing portal, not in our dashboard. POST /v1/billing/portal returns a one-time redirect URL. We do not mirror your invoices into a second system that could disagree with the first.

Method Path Scope
GET /v1/billing/entitlements read:billing
GET /v1/billing/usage read:billing
POST /v1/billing/checkout write:billing
POST /v1/billing/portal write:billing
PATCH /v1/billing/cap write:billing

Spend caps

A spend cap is a guard on your exposure, and it exists because BYOK means the variable cost is yours.

  • Default account cap: $1000 / month.
  • A brand-new account is capped at $100 for its first 30 days.
  • A donated BYOK key defaults to a $50 / month cap.

You get an email when you cross 50% and 80% of the cap, one per crossing. At 100% dispatch stops until the window rolls or you raise the cap with PATCH /v1/billing/cap.

Usage-metered accounts (the non-seat tiers) are charged $1.00 per handled issue or PR with the first 50 each month free, where "handled" means a session that completed or escalated — a failed session never bills. In practice both personal accounts and OSS-verified accounts are waived, so this rarely produces a charge; it is documented because you can see the counters in GET /v1/billing/usage and should know what they mean.

The billing window is the UTC calendar month.

Payment failure

A failed invoice pauses the account: dispatch stops, the pause is written to the audit log, and you are emailed. Paying resumes it and re-drains the work that was waiting. Nothing is deleted, and nothing runs silently in the meantime.

  • Teams & roles — who in your org can spend money.
  • BYOK — the other half of your bill, and why we never see it.
  • Rate limits — API budgets, which are not billing.