Skip to main content
Nexus BYOC is available only on Enterprise plans.
This page lists the Fireworks models that work with Pinecone Nexus Bring Your Own Cloud (BYOC) and the inference-proxy-models.toml fields a Fireworks catalog entry uses. For setup steps, see Use Fireworks AI models in Nexus BYOC.

Supported models

The following serverless models work with Nexus BYOC. For the full list, including models you can run on dedicated deployments, see the Fireworks model library. You can also use accounts/fireworks/models/gpt-oss-120b and accounts/fireworks/models/minimax-m3p1-flash the same way. Set each entryโ€™s context_window to the modelโ€™s own window, such as 131_072 for gpt-oss-120b. gpt-oss-120b is text-only, so also set no_vision = true. The catalog ID is the name you choose for an entry, and the examples here match it to the model name.

Endpoint and authentication

  • Endpoint: Set base_url to https://api.fireworks.ai/inference/v1, the Fireworks OpenAI-compatible endpoint.
  • API key: Store your Fireworks API key as the stack secret nexus-provider-keys.<ref>, and set the entryโ€™s api_key_ref to <ref>. Every Fireworks entry can share one reference. Pulumi stores the secret as a Kubernetes secret, and the inference proxy reads it at startup. If the key doesnโ€™t resolve, the proxy lists the model as unavailable.

Chat model fields

A Fireworks chat model is an [llm_models.<id>] entry with api_style = "openai". For current prices, see Fireworks pricing.

Embedding model fields

A Fireworks embedding model is an [embedding_models.<id>] entry with api_style = "openai".

Default profile fields

The [default] profile controls which catalog models your deployment serves.

Constraints

  • Chat model parameters: Every chat model must support the OpenAI tools and response_format parameters, because Nexus relies on both.
  • Default models: Each work areaโ€™s default comes from llm.phase_defaults, falling back to the tiers: Query from search or the standard tier, Curation from curate or the lite tier, and System from agent or the standard tier. The catalog reapplies these defaults on every settings pull, so the consoleโ€™s Default models card is read-only. To change a default, edit the catalog and run pulumi up.
  • Tier names in queries: A query treats a tier name, such as pro, as the Query default. Name models by catalog ID instead.
  • Embedding changes: A Pinecone indexโ€™s dimension is fixed when the index is created. If you change the default embedding model, keep every embedding model a context has used in the catalog, because existing contexts look up their embedding model by ID at query time.