Terms

Terms of Service

Claudex Labs provides managed AI production for apps, automations, CRM, websites, and short-form media. Provider API usage may be bundled into AI-agent workflows, but customers buy workflow access, managed production, reviewed deliverables, and Claudex Credits, not standalone raw API access or provider token passthrough.

Last updated: July 23, 2026

Customer summary

You buy reviewed production outcomes, not raw API resale or unlimited model access.

Draft AI scopes are non-binding until Claudex reviews and approves them.

Work starts only after customer approval and applicable credit or deposit authorization.

Deliverables, revisions, acceptance criteria, and handoff rules are set by the request, quote, or SOW.

Service Model

Claudex may use AI models, official APIs, cloud infrastructure, automation tools, affiliated companies, subcontractors, operators, and human reviewers to produce requested outcomes.

We do not promise unlimited usage, provider availability, or a particular third-party model. Delivery depends on scope, approvals, provider uptime, safety systems, and available production capacity.

Customer Responsibilities

Customers are responsible for the accuracy, ownership, legality, and completeness of the inputs they provide, plus timely approvals when work requires a credit estimate, scope decision, or acceptance review.

Customers may not use Claudex for unlawful, abusive, infringing, deceptive, harmful, or policy-evading activity, or to generate content that violates third-party provider rules.

Credits, Scope, And Revisions

Claudex Credits are service-budget units used to estimate and track managed production work. They are not cash, stored value, gift cards, transferable balances, standalone raw API tokens, or a right to unlimited usage.

AI-generated estimates and draft scopes are non-binding until reviewed and approved by Claudex. Claudex does not send draft AI output as a final quote.

Work begins only after customer approval and applicable credit or deposit authorization.

Revision limits, turnaround windows, acceptance criteria, repo handoff expectations, and delivery scope are set by the workspace request, plan, quote, or statement of work. Larger or risky work may pause for approval before more credits are used.

Billing, Cancellations, And Refunds

Stripe handles checkout, subscriptions, invoices, payment methods, billing details, and eligible tax collection. Subscription cancellation and invoice access are handled through the billing portal where available.

Subscription upgrades take effect only after Stripe successfully collects the applicable prorated charge. Eligible additional monthly credits are prorated for the remaining billing period. Subscription downgrades are scheduled for the next renewal so current-period access and credits are not removed early.

Customers may buy fixed or custom top-ups. Custom top-ups currently range from 10 to 10,000 Claudex Credits, where one credit equals one U.S. dollar of managed production budget.

When a customer confirms a saved-card top-up, the customer authorizes the displayed one-time charge to that payment method. A top-up does not create or change a subscription, does not authorize automatic recurring top-ups, and grants credits only after Stripe confirms payment.

Refunds are reviewed case by case. Completed production work, approved credit usage, third-party provider costs, and already-delivered custom work are generally not refundable unless Claudex confirms otherwise in writing.

Credits associated with refunded, reversed, disputed, or charged-back payments may be suspended or revoked. A canceled subscription stops future monthly grants; existing access and grants remain subject to the applicable billing period and account status.

Output And IP

After payment and subject to third-party provider terms, Claudex hands off the deliverables created for the customer. Software deliverables may be handed off in a customer-owned GitHub repository, public or private depending on the engagement. Customers are responsible for reviewing outputs before publishing, shipping, or relying on them.

Claudex remains the customer-facing contracting party unless a written agreement says otherwise. Claudex may give approved operators or subcontractors limited access to customer repositories and systems for the assigned scope, subject to applicable confidentiality, security, and intellectual-property obligations.

Claudex may retain reusable know-how, workflow patterns, generalized tooling, and non-customer-specific operational improvements developed while providing the service.