Pricing

Pay for input and output tokens. The rates below are loaded from the model_prices table. The estimator lists those rates next to reference prices for the same token counts.

Model idNameInputOutputStatus
Loading prices…

Free tokens, then credits

After email verification, a new account receives a one-time credit of 10,000,000 tokens. Input and output tokens share that pool. Free tokens are spent before prepaid credits. This is not a timed trial. Buy more credits with Stripe Checkout from the billing page. A batch is accepted only when free tokens plus the available balance cover the estimate. When the job completes, batchrate spends free tokens first and debits the paid remainder at the prices in config.

The grant amount is FREE_TOKENS_ON_SIGNUP. Minimum top-up $10, preselected amount $25, from min_topup_cents and default_topup_cents. File size and line limits live in app_config too.

Batch cost estimator

Pick a model and average sizes, or paste a sample JSONL file. Token counts stay in the browser. The approximate tokenizer matches the server: message text length divided by 4, rounded up, at least 1 token when the line has messages. Output tokens are an estimate.

A pasted or uploaded file is tokenized here and replaces the averages above. Prompt text is not uploaded.

FAQ

How long are files kept?

Input files are deleted 7 days after the batch reaches a terminal state, or 7 days after upload if the file is never used. Output and error files are deleted 30 days after they are created. Those periods are INPUT_RETENTION_DAYS and OUTPUT_RETENTION_DAYS. Delete a file sooner with DELETE /v1/files/{id} or the button in the console. An input file that a batch is still running has to be cancelled first. Deletion removes the object immediately. Credit ledger rows stay for accounting.