Credits

Claudex Credit Policy

Claudex Credits are service-budget units for managed AI production. One Claudex Credit equals one U.S. dollar of service budget, but credits are not cash or standalone raw provider tokens.

Last updated: July 23, 2026

Customer summary

Credits track customer-facing production budget; raw provider token usage stays internal.

Studio includes 150 monthly credits; Production includes 250 monthly credits and 4 managed request slots; Operator includes 350 monthly credits and 10 slots; Delivery Retainer includes 750 monthly credits and one active workstream.

Customers can buy fixed 10, 100, 500, or 1,000-credit packs or custom 10 to 10,000-credit top-ups.

CRM/app builds never auto-start from a raw request and require reviewed estimate approval gates.

What Credits Cover

Credits may cover model/API usage, agent/operator workflow time, QA and human review, retries, infrastructure, orchestration, delivery risk, and other production work needed to complete approved outcomes.

Customer-facing statements show Claudex Credits. Claudex does not expose raw OpenAI, Gemini, video, image, cloud, or automation provider token usage in the customer credit view.

Included And Purchased Credits

Studio includes 150 monthly Claudex Credits. Production includes 250 monthly Claudex Credits and 4 managed request slots per month. Operator includes 350 monthly Claudex Credits and 10 request slots per month. Delivery Retainer is $2,499 per month and includes 750 monthly credits plus one active workstream. Each slot is a reviewed request slot; actual execution consumes separately approved Claudex Credits, and larger scoped work still follows the applicable SOW approval rules.

Subscription credits expire at the end of their applicable billing period and do not roll over unless a written agreement says otherwise. Purchased top-up credits do not expire while the account remains in good standing, subject to refunds, disputes, chargebacks, account closure, and the other limits in this policy.

Claudex applies usage to credits with the nearest expiration first. Expiring subscription credits are therefore used before non-expiring top-up credits, preserving purchased top-up capacity for later approved work.

When a customer upgrades, Stripe charges the prorated price difference before the higher plan activates. Claudex grants the prorated positive difference in included monthly credits for the remaining period after payment succeeds. Downgrades take effect at the next renewal and do not trigger an immediate credit reversal.

Customers may buy fixed 10, 100, 500, or 1,000-credit top-ups, custom 10 to 10,000-credit top-ups, or custom enterprise packages through a statement of work.

A customer may confirm a top-up against a saved Stripe payment method after reviewing the exact amount and card identifier. This is a one-time purchase, not an automatic recurring top-up, and credits are added only after successful payment.

Credits are not stored value, gift cards, cash equivalents, transferable balances, or financial accounts. Credits attach to the customer workspace and may be limited by plan, scope, account status, or written agreement.

Approval Gates

Requests estimated at 50 credits or less can be auto-estimated but still start as draft scopes. Requests from 50 to 250 credits require customer approval. Requests above 250 credits require internal Claudex review before the customer sees an approved estimate.

Requests above 1,000 credits require enterprise approval or SOW. Requests above 10,000 credits require CEO or PM approval. CRM and app builds never auto-start from a raw user request.

AI-generated estimates and draft scopes are non-binding until reviewed and approved by Claudex. Work begins only after customer approval and applicable credit or deposit authorization.

Expensive media, video, provider-heavy, or high-risk production work must pause before exceeding approved credits.

Delivery Modes

Fast API Mode uses official API or provider paths for faster turnaround and may carry a 1.2x to 2.0x credit multiplier for urgency or throughput.

Managed Production Mode uses a slower queue, agent, operator, and review workflow for cost-controlled production and may carry a 0.7x to 1.0x multiplier. It remains a compliant managed production workflow.