OpenAI API token pricing (serverless, per 1M tokens, 2026-10-04 list price)

USD per 1M TOKENS, LIST PRICE, observed 2026-10-04. Standard tier, gpt-6.1-sol: input $2.00, cached input $0.10, cache write $2.50, output $10.00 (short context). Long-context (>=200k prompt) doubles every column: input $4.00, cached $0.20, write $5.00, output $15.00. Standard tier flagship gpt-6-astra: short input $10.00 / cached $1.00 / write $12.50 / output $50.00; long context $20.00 / $2.00 / $25.00 / $75.00. Cheapest standard model gpt-6-luna: short input $0.10 / cached $0.01 / write $0.125 / output $0.50; long context $0.20 / $0.02 / $0.25 / $0.75. Same-page tier multipliers observed on gpt-6.1-sol short-context input: Batch $1.00, Flex $1.00 (i.e. 50% off Standard), Fast $4.00 (2x), Ultrafast $8.00 (4x). price_usd carries the input rate of gpt-6.1-sol as the single representative number PERISHABLE-FIGURE STAMP (added 2026-10-04, uniform across data/supply/ so it is greppable). PRICE CLASS: PUBLISHED LIST PRICE - an asking rate a new customer is quoted, NOT a realised, discounted or negotiated transaction rate. A real bill is at or below this and typically well below it once commitments, credits and committed-use discounts apply. OBSERVED: 2026-10-04 RE-VERIFY BY: 2027-01-04 - the repo's quarterly re-verification bar. After that date this figure is presumed drifted and must be re-checked against its source before it is quoted again. A price without its observation date is noise; this stamp exists so a reader can tell a fresh figure from a stale one without reading prose. UNIT: USD per 1M TOKENS, LIST PRICE, observed 2026-10-04 READING RULE: No further perishable flag is published for this figure.

lead_time_weeks is null because NO NUMBER APPLIES, and the reason is specific rather than generic: this record prices a metered service term (tokens, egress, storage) rather than hardware capacity, so there is no order-to-delivery interval to report at all. Calling this 'no published lead time' would be wrong in the other direction - nothing was withheld.

no EAR citation: no controlled item is transferred by this transaction; not an EAR citation: provider service terms and end-use policy (the AI Diffusion Rule briefly tiered service access before its 2025-05-13 rescission)

MECHANISM: a token-priced API, so no accelerator crosses a border and the 3A090 hardware licence regime does not attach to the transaction. Export control becomes an END-USER AND TERMS question instead: the provider applies geographic and end-use restrictions to service access, and a customer can still be refused under sanctions or end-use policy wherever the compute sits. A reader targeting a restricted destination should read the provider's terms, not the EAR.

THESE ARE LIST PRICES AND THEY ARE THE FASTEST-STALING NUMBERS IN THE REPO. Two structural things a reader must not miss. (1) OpenAI prices by TIER as well as by model, and the tiers are the same underlying model: Batch and Flex are both exactly 50% of Standard, Fast is 2x, Ultrafast is 4x on the same gpt-6.1-sol row. Quoting an OpenAI price without naming the tier is meaningless - the same tokens differ 8x between Flex and Ultrafast. (2) Every model has TWO price rows, short context and long context, and the split is not a gentle surcharge - it is exactly 2x on the current lineup. xAI and Anthropic do the same thing (see rent-anthropic-api-token-pricing and rent-xai-api-token-pricing). Never mix a long-context input rate with a short-context output rate; that is an easy 4x error. Non-token charges on the same page that belong in a total-cost model: file search storage $0.10/GB/day (1 GB free), web search $10.00/1k calls plus search-content tokens billed at model rates, tool calls $2.50/1k calls, hosted-shell/code-interpreter containers $0.03/$0.12/$0.48/$1.92 per 20-minute session for 1/4/16/64 GB, Realtime audio billed per 1M tokens on a separate column set from text. OpenAI publishes NO GPU hourly rate and NO region list - the serving fleet is not a purchasable product, which is why this record has an empty accelerator_ids list rather than a guess. EXPORT CONTROL (2026-10-04): NOT APPLICABLE IN THE HARDWARE-SHIPMENT SENSE - this record prices a token-based API, so no accelerator is transferred across a border and the ECCN 3A090 hardware licence regime does not attach to the transaction. Recorded null rather than false precisely because a token API is where export control instead becomes an END-USER/TERMS question: the provider applies geographic and end-user restrictions to service access (the AI Diffusion Rule briefly put a tiered country structure on exactly this kind of service before being rescinded on 2025-05-13), and a customer can still be refused under sanctions or end-use policy regardless of where the compute sits. Anyone reading this record for a restricted destination should look at the provider's terms, not at the EAR. Sources for the regime: spl-bis-2025-05-ai-diffusion-rescission, spl-bis-2026-05-d5-guidance. EXPORT CONTROL (2026-10-04): NOT APPLICABLE IN THE HARDWARE-SHIPMENT SENSE - this record prices a token-based API, so no accelerator crosses a border and the ECCN 3A090 hardware licence regime does not attach to the transaction. Recorded NULL rather than false precisely because a token API is where export control instead becomes an END-USER and TERMS question: the provider applies geographic and end-user restrictions to service access (the AI Diffusion Rule briefly put a tiered country structure on exactly this kind of service before being rescinded and unenforced from 2025-05-13), and a customer can still be refused under sanctions or end-use policy regardless of where the compute sits. For a restricted destination, read the provider's terms, not the EAR. Sources: spl-bis-2025-05-ai-diffusion-rescission, spl-bis-2026-05-d5-guidance. LEAD TIME: null - correct and not a gap. A token-priced serverless API is provisioned on request, so there is no lead time to publish; the binding constraint when a model is at capacity is provider-side queuing and any per-account concurrency limit, which this repo records in notes where a vendor publishes one (see the DeepSeek concurrency figures already here). Deliberately NOT recorded: any 'model capacity lead time' estimate, because vendors publish none and the SEO 'GPU lead time' numbers that circulate do not apply to a rented endpoint. Probe log in source spl-negative-no-oem-publishes-lead-time.