<!-- Generated from public website sources; do not edit this file. -->

> DSSUB design reference. Account, payments and API are not connected; prices, policies and setup examples require independent launch verification.

# Choose a plan
Compare a fixed allowance with token-based API charges for your workload.

## Start with availability
DSSUB purchases are not connected. Prices and allowances are design references. First check the [model directory](/models/index.md) and [service availability](/service-status/index.md); roadmap families do not have confirmed access.

## Estimate your actual usage
Use the [calculator](/compare/#cost-calculator). Enter uncached input, cached input and output separately, then add the busiest 5-hour and 7-day token volumes. The selected model's multiplier applies to the whole example workload.

## Choose a billing period
A one-time plan is designed for one calendar month with no renewal. Monthly billing is recurring; annual billing charges the full year upfront. The monthly equivalent of an annual price is not a monthly charge. All three periods share the same design allowances.

## Check fit before price
Check both usage windows, model inclusion and any eventual rate or concurrency limits. High total usage does not guarantee a plan is cheaper if the workload arrives in bursts or leaves much of the allowance unused. A high cache-hit workload can reduce API costs.

## Review the full terms
Before a future purchase, confirm the seller, total charge, delivery, renewal and cancellation rules. These will need to match the independent DSSUB service. Current [terms](/terms/index.md) and [refund information](/refunds/index.md) describe preview scope only.

---

HTML source: [Choose a plan — dssub Tutorials](/docs/choosing-a-plan/)
