-
Notifications
You must be signed in to change notification settings - Fork 2.5k
fix: add missing Vertex AI models and us-south1 region #7726
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -294,6 +294,60 @@ export const vertexModels = { | |
| outputPrice: 1.15, | ||
| description: "Meta Llama 4 Maverick 17B Instruct model, 128K context.", | ||
| }, | ||
| "gpt-oss-120b-maas": { | ||
| maxTokens: 8192, | ||
| contextWindow: 128_000, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 2.0, | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is the decimal format for pricing intentional here? I notice existing models use integers (15, 75) while these new models use decimals (2.0, 8.0). Would it be better to maintain consistency by using |
||
| outputPrice: 8.0, | ||
| description: "GPT OSS 120B model via Model-as-a-Service.", | ||
| }, | ||
| "gpt-oss-20b-maas": { | ||
| maxTokens: 8192, | ||
| contextWindow: 128_000, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 0.5, | ||
| outputPrice: 2.0, | ||
| description: "GPT OSS 20B model via Model-as-a-Service.", | ||
| }, | ||
| "deepseek-r1-0528-maas": { | ||
| maxTokens: 8192, | ||
| contextWindow: 128_000, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 1.0, | ||
| outputPrice: 4.0, | ||
| description: "DeepSeek R1 0528 model via Model-as-a-Service.", | ||
| }, | ||
| "deepseek-v3.1-maas": { | ||
| maxTokens: 8192, | ||
| contextWindow: 128_000, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 0.8, | ||
| outputPrice: 3.2, | ||
| description: "DeepSeek V3.1 model via Model-as-a-Service.", | ||
| }, | ||
| "qwen3-coder-480b-a35b-instruct-maas": { | ||
| maxTokens: 8192, | ||
| contextWindow: 128_000, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 3.0, | ||
| outputPrice: 12.0, | ||
| description: "Qwen3 Coder 480B Instruct model via Model-as-a-Service.", | ||
| }, | ||
| "qwen3-235b-a22b-instruct-2507-maas": { | ||
| maxTokens: 8192, | ||
| contextWindow: 128_000, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 2.5, | ||
| outputPrice: 10.0, | ||
| description: "Qwen3 235B Instruct model via Model-as-a-Service.", | ||
| }, | ||
| } as const satisfies Record<string, ModelInfo> | ||
|
|
||
| export const VERTEX_REGIONS = [ | ||
|
|
@@ -306,6 +360,7 @@ export const VERTEX_REGIONS = [ | |
| { value: "us-west2", label: "us-west2" }, | ||
| { value: "us-west3", label: "us-west3" }, | ||
| { value: "us-west4", label: "us-west4" }, | ||
| { value: "us-south1", label: "us-south1" }, | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nice attention to detail placing this alphabetically! The ordering is correct between us-west4 and northamerica-northeast1. 👍 |
||
| { value: "northamerica-northeast1", label: "northamerica-northeast1" }, | ||
| { value: "northamerica-northeast2", label: "northamerica-northeast2" }, | ||
| { value: "southamerica-east1", label: "southamerica-east1" }, | ||
|
|
||
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.
The "-maas" suffix pattern is interesting. Could we add a comment explaining that these are Model-as-a-Service offerings? This would help future maintainers understand the naming convention.