-
Notifications
You must be signed in to change notification settings - Fork 10.4k
WAI pricing update #20118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
WAI pricing update #20118
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
11 changes: 11 additions & 0 deletions
11
src/content/changelog/workers-ai/2025-02-20-updated-pricing-docs.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| --- | ||
| title: Workers AI updated pricing | ||
| description: Granular pricing in units and neurons | ||
| date: 2025-02-20T11:00:00Z | ||
| --- | ||
|
|
||
| Updating Workers AI pricing page to reflect the latest models and pricing. Pricing is presented in units (tokens, audio seconds, etc) but will continue to be charged in neurons. The price per neuron remains the same as it has always has been at $0.011 per 1000 neurons. | ||
|
|
||
| Having per-model pricing (instead of buckets) allows us to be more flexible on what models are charged. As we optimize each model, we can then pass on savings for that model. | ||
|
|
||
| Going forward, models will be launched in GA with pricing. Dashboard changes are coming to reflect usage in units and neurons. Docs redesign is incoming to show pricing directly on the respective model pages. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would love to see this pull from the model info in the future. LGTM for clarity now!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, agree that we'd want this pulled programmatically if possible.
The other bit here is -- if the data is pulled in programmatically -- we'd just want a pricing-specific section of the models pages (and likely not have direct pricing here). Dev lift for that is pretty minimal... dev lift for also showing those prices here is heavier.