Add amazon.nova-premier-v1:0 to amazon-bedrock provider
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- aws
- Domain
- ai-infra-agents
Research direction
Start with providers/amazon-bedrock/models/amazon.nova-pro-v1:0.toml and compare it with the AWS Bedrock model-card and pricing links in the issue. Add the missing amazon.nova-premier-v1:0 metadata entry, including verified pricing, limits, modalities, and capabilities; done means the amazon-bedrock provider exposes the model with the specified values.
Written by the indexing model from the issue text.
Description
Summary
amazon.nova-premier-v1:0 is missing from providers/amazon-bedrock/models/, even though the other Nova generation-1 models (nova-lite, nova-micro, nova-pro) are present there.
The Kilo provider already has a nova-premier entry, but the amazon-bedrock provider is the one consumed by downstream tooling (e.g. langchain-aws runs a daily refresh from models.dev and uses the amazon-bedrock provider).
Spec (from AWS Bedrock docs)
- Model ID:
amazon.nova-premier-v1:0 - Geo inference ID:
us.amazon.nova-premier-v1:0 - Release date: 2025-10-31
- Knowledge cutoff: 2024-10
- Context window: 1,000,000 tokens
- Max output tokens: 25,000
- Reasoning: supported
- Input modalities: text, image, video
- Output modalities: text
- Tool use: yes
- Prompt caching: yes
Suggested file
providers/amazon-bedrock/models/amazon.nova-premier-v1:0.toml — modeled after amazon.nova-pro-v1:0.toml:
name = "Nova Premier"
family = "nova-premier"
release_date = "2025-10-31"
last_updated = "2025-10-31"
attachment = true
reasoning = true
temperature = true
knowledge = "2024-10"
tool_call = true
open_weights = false
[cost]
# Please verify against https://aws.amazon.com/bedrock/pricing/
input = 2.50
output = 12.50
cache_read = 0.625
[limit]
context = 1_000_000
output = 25_000
[modalities]
input = ["text", "image", "video"]
output = ["text"]
Impact
Tools that derive LLM model metadata from the amazon-bedrock provider will not emit a ModelProfile for nova-premier. For example, langchain-aws runs a daily automated refresh from models.dev — without an entry here, downstream consumers fall back to conservative hardcoded token limits rather than the model's actual 1M-token context window.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 18m
- Merged PRs (30d)
- 856
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anomalyco/models.dev
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/models.dev#7494 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
anomalyco/models.dev#7459 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
anomalyco/models.dev#6639 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
anomalyco/models.dev#5691 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
anomalyco/models.dev#5630 ·
All issues in anomalyco/models.dev
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100