Pricing

You can think of tokens as pieces of words used for natural language processing. For English text, 1 token is approximately 4 characters or 0.75 words. As a point of reference, the collected works of Shakespeare are about 900,000 words or 1.2M tokens.

To learn more about how tokens work and estimate your usage…

• Experiment with our interactive Tokenizer tool(opens in a new window).

• Log in to your account and enter text into the Playground. The counter in the footer will display how many tokens are in your text.

We generally recommend that developers use either GPT-4o or GPT-3.5 Turbo, depending on the complexity of your tasks. GPT-4o generally performs better on a wide range of tasks, while GPT-3.5 Turbo is fast and inexpensive for simpler tasks. We recommend experimenting with these models in Playground(opens in a new window) to investigate which models provide the best price performance trade-off for your usage.

Log in to your account to view your usage tracking dashboard(opens in a new window). This page will show you how many tokens you’ve used during the current and past billing cycles.

You can set a monthly budget in your billing settings(opens in a new window), after which we’ll stop serving your requests. There may be a delay in enforcing the limit, and you are responsible for any overage incurred. You can also configure an email notification threshold to receive an email alert once you cross that threshold each month. We recommend checking your usage tracking dashboard(opens in a new window) regularly to monitor your spend.

For customers managing work with Project, you can set and manage billing restrictions per project(opens in a new window) in the Dashboard.

No, OpenAI APIs are billed separately from ChatGPT Plus, Teams, and Enterprise. The API has its own pricing, which can be found at openai.com/pricing. ChatGPT subscription pricing can be found at openai.com/chatgpt/pricing/.

Yes, we treat Playground usage the same as regular API usage.

Chat completion(opens in a new window) requests are billed based on the number of input tokens sent plus the number of tokens in the output(s) returned by the API.

Your request may use up to num_tokens(input) + [max_tokens * max(n, best_of)] tokens, which will be billed at the per-engine rates outlined at the top of this page.

In the simplest case, if your prompt contains 200 tokens and you request a single 900 token completion from the gpt-3.5-turbo-1106 API, your request will use 1100 tokens and will cost [(200 * 0.001) + (900 * 0.002)] / 1000 = $0.002.

You can limit costs by reducing prompt length or maximum response length, limiting usage of best_of/n , adding appropriate stop sequences, or using engines with lower per-token costs.

There are two components to fine-tuning pricing: training and usage.

When training a fine-tuned model, the total tokens used will be billed according to our training rates. Note that the number of training tokens depends on the number of tokens in your training dataset and your chosen number of training epochs(opens in a new window). The default number of epochs is 4.

(Tokens in your training file * Number of training epochs) = Total training tokens

Once you fine-tune a model, you’ll be billed only for the tokens you use. Requests sent to fine-tuned models are billed at our usage rates.

We will be publishing an SLA soon. In the meantime you can visit our Status page(opens in a new window) to monitor service availability and view historical uptime. If your company or application has specific requirements, please contact our sales team.

Yes. Azure customers can access the OpenAI API on Azure with the compliance, regional support, and enterprise-grade security that Azure offers. Learn more(opens in a new window) or contact our sales team.