Before your next AI renewal, compare what you pay through the app with the final web price. Match the same plan, tax and fees; then check for seats you no longer use. This can reduce your bill before you change a single prompt.
For agents and API work, check included access, caching, resets and retries. Keep the result useful, then reduce its cost.
TL;DR
- Subscriptions: match final web/app totals and review unused seats before optimizing prompts.
- Already paying: try suitable included tools before buying another subscription or API credits.
- API agents: inspect cache reads and writes; a saved conversation can become expensive to process again.
- At a usage cap: check the exhausted meter, natural reset and offer expiry before redeeming a reset or upgrading.
- Repeated tasks: count useful results, every failed attempt and your review time. Cheaper tokens can buy more cleanup.
Prioritize reset timing for an urgent deadline, caching for high-volume API use. This is advice, not a measured savings ranking.
Check your bill · Use included access · Check caches · Time a reset · Save the monthly checklist
Compare no-payment routes and their restrictions. The new DeepSeek V4.1 Flash Free offer explains the temporary OpenCode route and its privacy terms; OpenCode Go remains paid.
Where to look first
Check your bill before your prompts
Dated example, October 7, 2026: Apple’s Cambodia storefront listed Claude Max 20x at US$299.99/month, against Anthropic’s US$200 web base price. The $99.99 gap would mean 33.3% less if those were your matched final prices. The mobile listing was nearly 50% above the web base; that is not 50% savings. Anthropic’s Max pricing.
Compare the same tier and billing period, using your legitimate billing location, currency, tax, payment fees and renewal benefits. Gaps vary: the US Apple listing in that review was $249.99. Listings are not checkout quotes or settled charges.
Record who bills you and the full next renewal. Before cancelling or switching, check access, data and grandfathered terms. Avoid overlap; cancellation does not transfer billing. Use the Claude bill checklist, with its dated Thai checkout example and renewal steps.
Use what your subscription already includes
Before buying another tool, check your subscriptions’ included access, permitted use, allowance and shared meters. Count a saving when an actual charge is avoided; retain the subscription bill and setup/review time.
October 17 update: ChatGPT Pro 100 is our October value pick for sustained Chat, Work and Codex use, with Sol 6.1 as the everyday workhorse. The buying guide covers the latest Chat improvements and a practical split between Sol, Astra and a dot.
Included dots access, rechecked October 17. OpenAI describes gradual access for Pro 100/200/500 users over 18 outside the EEA, UK and Switzerland, Business Premium worldwide, and Enterprise worldwide with administrator enablement. Plus is not listed; eligibility does not guarantee immediate access. Dots access.
- Conversation with a dot: does not count toward ChatGPT usage limits.
- Deeper work: has an included allowance and extended first-month limits; numerical quota and exact expiry are unspecified.
- Work/Codex tasks it starts or manages: consume those products’ limits as usual; Work and Codex share usage.
The first dot is included at no extra cost with eligible Pro and Business Premium plans. Check the dot terms, Work/Codex pricing and your dashboard before acting. The separate Pro 200 transition does not establish a dot-benefit expiry.
Try one brief or plan review with a stopping point. Record acceptance, attempts, review minutes and meter changes, including downstream tasks. Dot quotas, savings and CAR remain unmeasured by AIHackers. Proposed trial · October subscription choices · Temporary launch terms.
The conversation you paid for can become expensive again
A saved conversation stores history; a prompt cache reuses computation for an unchanged request prefix. Anthropic documents a default five-minute lifetime, refreshed by reuse, and an optional one-hour duration at a higher write price. After expiry, retained history can need processing again. Claude cache mechanics.
Vendor example, checked September 27: a 100,000-token Fable 5.1 prefix cost $1.25 for a five-minute cache write versus $0.025 for a read (about $0.03 rounded). Exact rates imply 50× for that prefix; rounded arithmetic does not. The comparison excludes output, new input and tools. It is not a 50× whole-session bill or a subscription-quota formula. Example · Rates.
Expiry, a model change, or changes before the reusable prefix can cause a miss. Instructions, tool definitions and effort/thinking settings can affect it; the scope varies by model and API. Some per-message changes are supported, and OpenAI documents a GPT-6 configuration-update route that preserves earlier context. OpenAI cache guidance.
Do this: continue a useful warm thread, investigate an unexpected miss, or make a compact handoff at a task boundary. Keep the objective, revision, relevant files, decisions, failed attempts and next check. Compaction can lose evidence and require another cache write. Change model or effort when quality warrants it, then inspect usage fields. Use the miss checklist and logging recipe.
Sol 6.1 example, checked October 3: 900K cached reads, 100K writes and 100K output across short Standard requests cost $1.34, versus $1.43 on Sol 6—6.3% lower for that mix. It establishes neither a typical 90% hit rate nor cheaper accepted work. Assumptions and exclusions · Cold-start and output-heavy scenarios. API prices cannot estimate subscription capacity.
Check when the weekly clock starts
Weekly windows do not accumulate: two idle weeks are not a budgetable 2× allowance. Check the dashboard: is the clock running or usage-triggered? A small useful task can start a usage-triggered window before a larger session. Weekly-clock guide.
Rechecked October 17, OpenAI’s banked-reset instructions say a full reset refreshes both Codex windows and changes the weekly reset date. The old scheduled refill does not also arrive. Availability and expiry depend on the account and offer.
Illustrative timeline: today is Tuesday; your dashboard shows a Friday refill and a banked reset expiring Monday.
| Choice | Effect | Suitable when |
|---|---|---|
| Redeem and resume Tuesday | Weekly refill moves to around the next Tuesday; no Friday refill | Valuable work cannot wait |
| Wait for Friday | Banked reset remains available until expiry | Remaining capacity or another route covers the wait |
| Wait past Monday | Unused banked reset expires | No useful workload needs it |
Waiting can preserve the imminent refill, without guaranteeing double useful compute. Demand, allowance and expiry decide the benefit. Read the clock after redemption.
Purchased weekly resets are separate: OpenAI’s documented rule pulled the next allowance forward, with the next automatic reset seven days after the first subsequent request. They were not top-up credits. Recheck the capacity guide and signed-in offer before buying.
Follow reset reports: use Codex Resets for source-linked announcements, then check your own usage screen. An automatic reset cannot be saved like a banked reset. Our reset-report and timing guide explains the distinction and the limits of the secondary cache report. Schedule useful work around capacity; generating throwaway output does not create value.
Ask “20x of which limit?”
In the October 7 review, Anthropic defined Max 5x/20x against Pro’s per-session allowance, with five-hour resets and a separate weekly cap. That did not establish 20× weekly capacity. Max limits.
November 1 update: OpenAI canceled the planned Pro 200 reduction. Claude Max 20x is now Ultra; its old session label cannot be compared directly with the new weekly multiplier. Use the current usage and API-credit comparison for both providers’ separate recurring credits, rollout and expiry. The October 7 Claude observation above remains historical; this does not renew the playbook’s other source checks.
Identify the exhausted meter—session, week, model, tool or workspace—and confirm the upgrade changes it. Check shared usage and the full renewal bill. The Claude limits evidence separates documented limits from account reports.
Maintain instructions like dependencies
Duplicated rules, obsolete commands and mandatory reads can make agents repeat work. Keep security boundaries, acceptance criteria and release checks; put task-specific detail behind short pointers. Test a representative task before and after editing instructions. Shorter is better only when correct behavior survives. OpenAI’s Astra instruction guidance.
Stop paying twice for the same failure
Use code for sorting, arithmetic, parsing and validation. For judgment, try the least expensive candidate that passes your checks; bound escalation. Multiple agents duplicate context and coordination; compare their total cost with one agent.
Name the failure before retrying: missing evidence needs retrieval, a broken tool needs repair, unclear scope needs clarification, and a capability gap may need another model. Bound transient-error retries and set a deadline. The worked workflows give stopping rules.
Check offers without turning model shopping into a job
Verify enrollment, region, expiry, cashback delay and ordinary renewal. Unresolved eligibility is not an available saving. Include migration, privacy requirements, integration and learning time before switching. Keep a tested fallback when continuity matters; that need not mean another recurring seat. Offer checks.
The ten-minute cost audit
Start with renewal totals. For repeated work:
- Pick a representative task set; define acceptance, deadline and retry budget.
- Record access route, every attempt, accepted results, spend and review/cleanup minutes. Mark missing evidence unknown.
- Choose one change below and rerun the same tasks under the same rules.
- Compare completion rate, cost and time. Keep the change only if it meets your needs.
Keep separate spending ledgers
| Cost or allowance | Record separately |
|---|---|
| Subscription | Full bill, included access, measured use and unused capacity |
| Purchased product credits | Price and product-specific rules; not necessarily a refill |
| API | Model, tool, cache and service-tier charges |
| Promotion | Eligibility, expiry and unreconciled debit |
| Local inference | Hardware, power, setup and maintenance |
| Human work | All retry, review, correction and integration time |
Subscription allowance is not portable API credit. Check the active billing route: API-key authentication can produce a separate bill. Unused allowance is not money saved. Capacity rules.
A promotional-account example: TypeSafe
The Jev inbox example separates token-value arithmetic, task cash purchases and unreconciled promotional debit. Its dated $5 account report is not a universal offer. Reference agreement alone does not establish full CAR; review/cleanup time and reconciled cost evidence are still needed. Promotion eligibility.
The savings stack, in order
- Define acceptance first. Fix outputs, checks, sources, deadline and stopping budget.
- Remove deterministic work. Parse, sort, calculate and validate with code where rules are known.
- Choose access. Compare suitable included capacity, API, purchased credits and local inference.
- Bound context. Retrieve relevant ranges; keep the evidence needed to verify the result.
- Route by task. Start with a candidate that passed representative checks; bound escalation.
- Cache and batch where suitable. Measure hits; defer independent tasks only when the completion window fits.
- Check timing and offers. Verify clocks, eligibility, expiry, final charges and renewal terms.
- Compare accepted-result cost. Count all attempts and review time across the same submitted tasks.
Stable text alone does not guarantee a cache hit. Check OpenAI cache rules, Anthropic cache rules and the chosen provider’s batch window and supported tasks. OpenAI Batch guide · Caching implementation guide.
Three worked workflows
1. Interactive coding
- Input: a bounded change, repository revision and named files.
- Acceptance rule: behavior passes required tests; review finds no unresolved correctness issue.
- Cost intervention: tools handle search, formatting and checks; give the model relevant excerpts and errors.
- Stopping condition: stop after tests and diff review pass, or record rejection and the blocker at the retry/time cap.
2. Bulk structured extraction
- Input: fixed source records, a schema and examples.
- Acceptance rule: each row passes validation and matches its source; reject ambiguity as declared.
- Cost intervention: parse first; send semantic or rejected rows to the model, caching/batching when suitable.
- Stopping condition: every submitted record is accepted or explicitly rejected; include bounded retries and original coverage.
3. Source-backed research
- Input: one decision question, date cutoff, primary sources and research budget.
- Acceptance rule: consequential claims have supporting passages and dates; gaps/conflicts remain unresolved.
- Cost intervention: retrieve targeted sections, deduplicate, then compare and draft; manually check claim-bearing passages.
- Stopping condition: stop at the evidence standard or budget; report gaps instead of paying for repeated guesses.
Measure Cost per Accepted Result
CAR = (model/tool cost + human review and cleanup hours × loaded hourly rate) / accepted tasks
Use equal submitted task coverage: the same tasks, acceptance rules, deadline and retry policy. Count every attempt, including failures and retries, plus all review and cleanup. Report accepted/submitted counts so skipping hard tasks cannot look efficient. Count each accepted task once.
Allocate subscription cost over a stated period and consistent share of measured use. Report the full seat bill and unused capacity separately. For local inference, include hardware depreciation or rental, power, setup and maintenance over the same period and attributable use. Count setup time once and show how utilization changes the allocation.
Report cash and minutes separately first. Without a defensible hourly rate, combined CAR is undefined. A lower CAR can mean time saved without cash returned. For renewal, compare the full future bill; an already-paid seat is a sunk cost only in the current period.
Hypothetical comparison—not an AIHackers result: both lanes receive the same four submitted tasks, at $60/hour for review and cleanup.
| Lane | All model/tool attempts | Accepted | Review/cleanup | CAR |
|---|---|---|---|---|
| A | $0.60 | 2/4 | 72 minutes | ($0.60 + 1.2 × $60) / 2 = $36.30 |
| B | $4.00 | 4/4 | 24 minutes | ($4.00 + 0.4 × $60) / 4 = $7.00 |
These invented totals exclude subscription/local costs. The larger model bill buys lower accepted-result cost under these assumptions.
Zero accepted results means no finite CAR. Report spend, review time and 0/N; mark CAR undefined. Missing evaluation or evidence means not-run or incomplete, not zero cost. CAR is distinct from token price, quota consumption and benchmark/session cost. Show latency and failure notes; small samples, subjective acceptance and allocation limit comparisons. Benchmark-literacy guide.
DeepSeek is still not-run
AIHackers’ DeepSeek CAR remains not-run. The dated connectivity preflight proves tooling access, not accepted-result performance. Task decisions, receipts and review time are still required.
The $1 AI showcase tested three frozen tasks with bounded attempts: one packing batch passed; two browser artifacts failed. Its unreconciled costs and failures remain part of the evidence. Full CAR remains not-run.
Choose your next step
Current buying guidance
Use the October buying guide for subscriptions and metered routes, Sol 6.1 economics for OpenAI pricing examples, Free Stack for no-payment/trial boundaries, and AI Value for other guidance. Route details: OpenCode, Z.AI, local inference. Each guide has its own review date.
Evaluate another low-cost model
Candidates: MiMo, DeepSeek, Luna, budget comparison. Premium: Opus 5.5 and Sol/Astra. Test accessible routes on your acceptance rules; there is no universal cheapest model.
Before changing a Codex plan, check the reset state
Check meters and renewal terms. The reset chronology retains account-specific reports, not a universal defect or workaround.
Check where your Claude subscription is billed
Use the bill checklist for matched totals and renewal steps.
Claude Code: reduce session context overhead
The command guide covers inspection, clearing and compaction. Measure useful work after a change.
Timing and offers
Check the Deals ledger, including ChatGPT referrals and the Kimi draw. Verify eligibility and ordinary renewal when acting. Expired offers are history. Promotions/referrals never change AIHackers’ recommendations, benchmarks or CAR.
Five-minute monthly audit
Save this for your next renewal. Change one thing at a time.
| |
Last full documentary review: October 7, 2026. Billing, cache mechanics, resets, renewal/expiry, limits and linked sources were checked. Dollar examples are listings or vendor calculations, not AIHackers receipts. Account entitlement, meters and runtime behavior were not tested. Claude’s new-cloud-credit claim status remains unresolved after a failed live check; no cutoff timezone or existing-credit spending expiry is inferred. Historical examples keep their original check dates; this shorter presentation is not a new full fact-check.
Next planned review: November 2026, with earlier rechecks after consequential source changes. A reminder is not a completed review. Recheck your own checkout, offers and clocks before acting. Report a correction.
Frequently asked questions
What is the best first step for reducing LLM costs?
For subscriptions, compare final renewal bills and remove unused overlap. For a repeated AI task, define a useful result before comparing models; include retries and human cleanup.
Are subscription limits the same as API credits?
No. Included subscription allowance, purchased product credits, promotional access, and metered API billing are separate ledgers with different rules.
When should an LLM task use Batch processing?
Use Batch for asynchronous, independent work that can tolerate the provider’s completion window and that has a machine-checkable output contract.
Does AIHackers have a DeepSeek cost-per-accepted-result finding?
No. Connectivity and tooling preflight are not accepted-result evidence. AIHackers’ DeepSeek CAR remains not-run.
October 17 update: OpenAI subscription recommendation, Dots accounting and banked-reset mechanics rechecked; current DeepSeek and campaign links added. The full documentary review remains October 7. No account-meter or accepted-result test was added.