# Shared points, quotes and failed runs Canonical: https://llmcitely.com/docs/points-and-usage Publisher: LLM Citely Reviewed: 2026-10-31 Understand the confirmed monthly point allowances, the ordinary collection rate and the distinction between a reservation, final charge and supplier expense. ![Read points and supplier costs separately. Illustrative lifecycle of an approved operation.](https://llmcitely.com/images/editorial/shared-point-lifecycle.svg) Illustrative lifecycle of an approved operation. A supplier expense does not authorize a second customer charge. Higher-cost work needs a quote. Original explanatory diagram; illustrative counts and states are not customer measurements. ## Start with the approved monthly packages The confirmed USD monthly packages before applicable tax are: | Plan | Monthly price before tax | Shared points | Project limit | |---|---:|---:|---:| | Starter | $39 | 4,000 | 1 | | Pro | $129 | 15,000 | 3 | | Agency | $399 | 50,000 | 10 | Purchasing remains closed in this preview. The prices and allowances are confirmed; that does not establish a production payment service, verified tax configuration or final commercial terms. Review the [pricing page](https://llmcitely.com/pricing) for the current purchase boundary. Points are a shared usage unit. They are not a promise of unlimited prompts, all models or every type of operation at the same cost. Prices exclude applicable taxes. If tax applies, the tax amount and final total will be shown before payment. See the [tax display policy](https://llmcitely.com/pricing#tax-policy); live tax collection is not enabled in this preview. ## Count executions before estimating points One ordinary collection execution uses one point under the approved policy. Count the workload as questions × observation surfaces × markets × collection rounds, then check the quote for the actual operation. **Illustrative plan:** 25 questions, two supported surfaces, one market and four rounds produce 200 planned executions. At the ordinary one-point rate, that is a 200-point planning estimate. It is not evidence that both surfaces are currently enabled or that all higher-cost operations share that rate. The [platform table](https://llmcitely.com/platforms#platform-readiness) controls current scope. Unsupported or unquoted higher-cost work must not quietly borrow the ordinary rate. ## Read the usage entry through its lifecycle A requested operation can reserve points before work starts. The reservation protects the available allowance while the result is pending; it should be distinguished from the final usage settlement. When reviewing an entry, keep the operation, quote, reserved amount, final charged amount and any returned amount together. A failed collection and its point settlement are related records, not interchangeable labels. If an entry is still pending, investigate the run status and the usage history before assuming the points were permanently consumed. This lifecycle is shown in the diagram below. It is an explanatory example, not a receipt from a live provider or a charge to a customer. ## A supplier expense is not a second customer charge A supplier may report an expense even when a customer-facing operation failed. The internal cost ledger records that liability separately from customer points. An internal invoice mismatch does not authorize an extra customer deduction. Higher-cost work needs a supported quote and cost boundary before it runs. If the supplier rate is not established, the route should remain unavailable rather than relying on an optimistic margin estimate. For a questioned usage entry, preserve the run identifier, period and usage record. Avoid sharing API keys, payment data or private answer text through a public form. The [contact page](https://llmcitely.com/contact) describes the current contact-channel availability. ## Review a retry as another operation Open the original run and identify whether it is queued, submitting, collecting or terminal. Do not launch another copy merely because the first has not finished. A deliberate new attempt can have a separate quote and usage entry. Record the new run alongside the original. Keep failed coverage out of the valid-answer denominator and explain any change in market, surface or question wording. The [collection-status guide](https://llmcitely.com/docs/collection-status-and-retries) explains this handoff. An agency report should show the work performed, evidence received and unresolved coverage. It should not turn an internal cost figure into a claim about customer ROI. ## When unused monthly points expire Monthly points are valid only within the paid billing period and do not carry over. Cancelling renewal preserves unused points until the current paid period ends. The cutoff follows your actual billing period; it is not a single calendar-month cutoff for every customer. This is the approved allowance policy for rollout. Live subscription and payment acceptance remain pending. Point expiry describes the spending allowance, not a rule for deleting project records. Read the [pricing policy](https://llmcitely.com/pricing) and [terms preview](https://llmcitely.com/terms) for the remaining commercial decisions. ## Questions, answered ### Does every operation cost one point? The confirmed rate applies to an ordinary collection. A higher-cost operation requires its own supported quote and limits. ### Are the listed packages available to buy now? No. The approved package values are shown for planning; production purchasing remains closed. ### Does a supplier charge mean I owe another point charge? No. Supplier liability and customer-point settlement are separate records. ## Sources and further reading - [LLM Citely approved package and point policy](https://llmcitely.com/pricing) Examples marked illustrative are not customer measurements. ## Continue with the next step - [Review the package and workload planner](https://llmcitely.com/pricing) - [Review a pending or failed run](https://llmcitely.com/docs/collection-status-and-retries) - [Plan client delivery](https://llmcitely.com/for-agencies) - [Keep coverage in the client report](https://llmcitely.com/templates/geo-report) ## Your next step [Review the package and workload planner](https://llmcitely.com/pricing)