Repository navigation
[assemblyai] Verify regional pricing, cache rates, and decision models - #1020
Open
mayankjain-panw wants to merge 8 commits into
Open
mayankjain-panw wants to merge 8 commits into
mayankjain-panw wants to merge 8 commits into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use live AssemblyAI model rates. Apply the missing Gemini regional uplift and expose global rates through custom pricing regions. Include the documented Decisions models; leave the unavailable Jev price explicitly null. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use the same Jev 1.13 input rate as TypeSafe and OpenRouter: 0.0000042 cents per token, with zero output-token cost. This follows the requested cross-provider model-rate convention; AssemblyAI-specific Jev pricing remains unconfirmed. No cache discount or regional surcharge is inferred. Validated actual model selection, usage extraction and cost calculation against the TypeSafe rate for 0, 1000 and 1000000 input tokens, including nonzero output usage. Pricing JSON formatting, lint, syntax and duplicate-key checks pass. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Update the AssemblyAI catalog and pricing PR with current main while preserving its provider entries. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the DashScope-only formatting change introduced by the merge commit hook. AssemblyAI catalog and pricing entries are unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Billing correctness depends on unavailable gateway behavior and an unverified inherited Jev rate for AssemblyAI, requiring human confirmation before rollout.
No open issues 🎉
What changed in this PR
Adds AssemblyAI model metadata and pricing to the repository’s catalog, which supplies rates through the existing pricing sync.
Changes:
- Registers speech, text-to-speech, chat, and Decisions models with capabilities and output limits.
- Adds per-unit pricing, regional/global overrides, and supported cache rates.
- Includes the inherited Jev pricing assumption and zero placeholders for unpublished Sync pricing.
| File | Description |
|---|---|
pricing/assemblyai.json |
Adds AssemblyAI rates, regional overrides, cache pricing, and unpriced defaults. |
general/assemblyai.json |
Adds model IDs, capabilities, output limits, and playground restrictions. |
Review effort: Balanced
Cover all 60 public LLM Gateway models with regional and cache prices. Set Sync and Dictation duration billing without token double charging. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep the reviewed AssemblyAI model catalog and published synchronous audio rates unchanged while incorporating current main. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Final qualification - 2026-11-17
Merged current main without rewriting history. Both CI validation checks pass. Both review threads are resolved with product-specific pricing sources and end-to-end evidence.
Qualification report. No real AssemblyAI credential or invoice was used.
Summary
Add the AssemblyAI catalog and pricing in the repository's existing cents per billable unit format. Current head:
29fb9ba062412726adb2f6ad1d6919f28b2874fc. Includes main atc12277ef98ffc7145ff557840f47597b6e6e7e98.Models is the source of truth. Gateway and Albus bundle generated copies through their existing configuration mechanisms; they do not maintain independent rates.
Coverage and rates
global,us,euandregional_increase_percentdata is represented. Forty models have regional uplifts. Three Nemotron models have explicit US/EU rates. No unpublished cache prices, long-context tiers or other dimensions were invented.universal-3-5-pro-syncanduniversal-3-6-pro-sync: 0.5 cents/minute = $0.30/hour. This replaces the earlier, now-stale assumption that Sync pricing was unpublished.assemblyai-dictation: 62/60 cents/minute = $0.62/hour, including LLM cleanup. Duration is charged throughadditional_units.request_audio_token; token prices are zero to avoid double charging.Sources checked 2026-11-16
Validation
general/scenario-ai.json, reproduced on exact main. That unrelated file is unchanged.No authenticated AssemblyAI calls or invoice reconciliation were performed: no approved test credential was supplied.
Rollout and companions
Publish this data to the normal remote catalog/pricing store before enabling priced Gateway traffic. Existing negative pricing-cache entries can survive for an hour. The normal Gateway pricing-sync workflow is manually triggered and opens a PR/MR; it does not deploy automatically.
The companion Gateway MR includes the local rate-card bundle, TS index, Rust loader and registry coverage. Albus includes the offline model-config bundles and provider-row SQL migration. Existing deployments must apply that SQL through their normal deployment process.