Provider setup directory

Choose the environment where your model runs, follow its setup guide, then pass the configured provider to an Agent. Each linked guide owns its dependency and credential instructions. For application-level comparisons, routing, and failure handling, use model patterns.

​

Direct provider APIs

Jev is a typed decision interface; do not assume every text-chat, vision, or judge example can substitute it unchanged. Use the Jev recipes.

​

Cloud deployments

A deployment name or inference profile is host configuration. Do not replace it mechanically with a model ID from a direct-provider example.

​

Local models and compatible gateways

Together, Groq, Fireworks, and OpenRouter are examples of gateway configurations covered by the compatible-provider guide. A compatible request shape alone does not establish tool, reasoning, vision, or streaming parity. Test the features your application uses.

​

Verify a new provider

1. Install only the provider dependency named in its guide.
2. Configure credentials and select a model available to that account/environment.
3. Run a small request through the first Agent program, changing the provider import and construction as the guide specifies.
4. Check terminal status and output, then test the actual tool/schema/streaming path your application needs.
5. Run your quality gate and update matching price entries.

The example-model record dates the text defaults used by these docs. Type checks establish SDK compatibility; model access and live endpoint behavior require a separate application check.

​

More patterns

Continue with model comparison and fallback, reasoning options, streaming, or the searchable integration directory.