Halfbill Code — Supplemental Terms
Effective date: [EFFECTIVE DATE PLACEHOLDER]
Last updated: September 11, 2026
Code plan terms in plain English
A human-readable summary of the key points. This overview is for convenience only and is not legally binding — the full text below is what governs.
These Code plan terms add to the Halfbill Terms of Service, which still govern everything not covered here — accounts, credits, liability, governing law and disputes.
Code Starter, Code Pro and Code Max each grant a monthly allowance of Halfbill credits. It resets every cycle and does not roll over, except when you upgrade mid-cycle. Past the allowance, requests pause or (opt-in) continue from your credit balance.
Use your key from coding agents and SDKs for your own development work. Serving your own product's traffic or batch pipelines through a Code plan is not allowed — use credits for that.
Code plans are for one person on one account. Extra accounts or reused payment cards to claim the allowance twice get cancelled.
We keep request metadata — tokens, cost, model, latency — for 30 days to power your dashboard. Prompts and responses are not stored, except stateful Responses API items, kept up to 30 days.
Cancel within 14 days of your first payment for a refund minus the allowance used (self-serve below 20% usage). Abuse, key sharing or bad-faith disputes can end every related account without a refund.
Halfbill Code (“Code plans”) is a service operated by Halfbill SRL, [PLACEHOLDER: registered company name and address], Bucharest, Romania, VAT [RO-XXXXXXXX] (“Halfbill”, “we”, “us”). These Supplemental Terms govern your subscription to a Code plan, the website at code.halfbill.uk, the Code dashboard and the API key issued with your plan (together, the “Service”).
These Supplemental Terms are an addendum to, and incorporate by reference, the Halfbill Terms of Service (the “Base Terms”), including the Refund Policy, the Acceptable Use Policy and the Privacy Policy. The Base Terms apply in full and govern everything not specifically addressed here — accounts and security, prepaid credits, intellectual property, warranties, limitation of liability, termination, governing law and disputes. Capitalized terms not defined here have the meaning given in the Base Terms.
Order of precedence. Where these Supplemental Terms and the Base Terms conflict on a point that concerns Code plans, these Supplemental Terms control for that point only.
1. What a Code plan is
A Code plan is a monthly subscription that grants an allowance of Halfbill credits for use with the models in the Halfbill catalog through the Halfbill API (OpenAI- and Anthropic-compatible endpoints). The plan is intended for interactive software development by one developer through coding agents, editors and SDKs such as Claude Code, Cursor, Codex CLI, Cline, Continue and OpenCode.
A Code plan is not a general-purpose API subscription. You may not use the key issued with your plan to serve your own applications, products or services to third parties, to run batch or automated pipelines, or for any workload other than your own interactive development. The plan price assumes interactive, human-in-the-loop use; other workloads must be paid for with prepaid credits under the Base Terms.
2. Plans, allowance and fair use
This section supplements section 3 of the Base Terms.
- Tiers. Code Starter, Code Pro and Code Max. The price and the allowance of each tier are those shown on the pricing page at the time you subscribe or renew. Prices are in USD and exclude VAT, which is added at checkout where applicable.
- Allowance. Each billing cycle grants the tier's allowance as Halfbill credits, valid for that cycle only. Usage is metered per token at the Halfbill prices published in the models catalog and deducted from the allowance. Unused allowance does not roll over at renewal and has no cash value.
- Premium fair use. Models classified as premium in the catalog additionally count against a weekly fair-use allowance of 12% (Code Starter), 15% (Code Pro) or 18% (Code Max) of the monthly allowance, measured over a rolling seven-day window. Standard models are not subject to a weekly cap. Reset Passes, where included or purchased, restart the weekly window and do not add to the monthly allowance.
- Overflow to credits. Once the allowance is used, requests are declined until the next renewal. If you enable overflow in the dashboard, further usage is charged to your organization's prepaid credit balance at the same prices, under the Base Terms.
- Catalog changes. We may add, replace or retire models, and may change the premium classification of a model, in line with section 1.3 of the Base Terms. If we remove all models included in your plan during a paid month, section 2.3 of the Refund Policy applies.
3. Billing, plan changes and cancellation
Plans are billed monthly in advance through our payment processor. By subscribing you authorize us to charge your payment method each cycle until you cancel.
Upgrades take effect immediately by default: we charge the full price of the new tier, your billing cycle restarts that day and you receive the new tier's full allowance, plus whatever remained of the allowance being replaced. That carried-over amount expires at the next renewal. You may instead schedule an upgrade for your next renewal. Downgrades take effect at your next renewal; you keep the current tier until then.
Cancellation. You may cancel at any time in the dashboard. The plan stays active until the end of the paid month and does not renew. There is no cancellation fee.
Refunds. The Refund Policy applies. In particular: if you cancel within 14 days of the first payment for a plan, we refund that payment minus the value of the allowance used at Halfbill prices during those days. While less than 20% of the allowance has been used, you can issue this refund yourself from Billing in the dashboard; the refund ends the plan immediately. Otherwise email support@halfbill.uk. Consumers in the EU keep their statutory 14-day right of withdrawal; by using the allowance before that period ends you ask us to start the service immediately and acknowledge that the refundable amount is reduced by the value consumed.
4. One account per developer
A Code plan is sold to one developer on one account. The following are not allowed:
- Opening more than one Code plan per person to multiply the allowance.
- Reusing the same payment card, device or address across accounts for that purpose. We check the card used at checkout against existing Code plans; a duplicate subscription is cancelled and not activated.
- Cancelling and re-subscribing under a new account to reset the allowance or the weekly window before renewal.
- Sharing the plan's API key with other people or using it on behalf of a team or company. Teams should use prepaid credits or a Teams arrangement under the Base Terms — write to hello@halfbill.uk.
If these rules are broken we may cancel every related plan, revoke the keys concerned and refuse future signups, and we may retain fees paid for the cycle in progress since the allowance has already been provisioned. Section 12 of the Base Terms applies.
5. Acceptable use
The Acceptable Use Policy applies. In addition, you agree not to use a Code plan for non-development workloads as described in section 1, not to attempt to circumvent allowances, fair-use windows or rate limits, and not to resell access. We may rate-limit, suspend or downgrade a plan that shows sustained traffic patterns inconsistent with interactive development.
6. Data
Data handling is described in the Code plan Privacy Policy, which supplements the Halfbill Privacy Policy. In short: request metadata is kept for 30 days to power your dashboard; prompts and responses are not stored, except stateful Responses API items, which are kept for up to 30 days so response chaining works.
7. Contact
Questions about these Supplemental Terms or the Base Terms: legal@halfbill.uk.
Halfbill SRL
[PLACEHOLDER: registered company name and address]
Bucharest, Romania
Halfbill is an independent service and is not affiliated with, endorsed by, or sponsored by OpenAI or Anthropic. Model names are trademarks of their respective owners.