anomalyco / anomalyco/models.dev

Add amazon.nova-premier-v1:0 to amazon-bedrock provider

Open Beginner friendly
#2,015 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.9k
Forks
1.7k
Avg merge
3h 21m
Merged PRs (30d)
873

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
aws
Domain
ai-infra-agents
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.