Skip to main content
The provider_params field lets you pass provider-specific parameters that aren’t part of Eden AI’s unified schema. This gives you access to advanced or niche options offered by individual providers without breaking the standard request format.

How It Works

Add a provider_params object to any Universal AI request. Its contents are forwarded to the provider alongside the standard input fields. On most subfeatures any parameter is forwarded as-is; video generation and the web subfeatures accept only the parameters on an allowlist (see Parameter Validation and Allowlisting).

Basic Example

Common Use Cases

Image Generation: Style and Quality

Control output style and quality for image generation:

Text to Speech: Voice Settings

Pass provider-specific voice parameters:

Parameter Validation and Allowlisting

For most subfeatures, Eden AI forwards provider_params directly to the provider without validation. Invalid parameters may cause provider errors. These subfeatures accept only the parameters on a per-provider allowlist, which each page lists under Provider Parameters: Any other parameter is rejected with a 400 Bad Request error naming the parameters that were refused. The check covers every provider the request can reach: with fallbacks, each parameter must be allowed for the provider in model and for every fallback provider, or the whole request is rejected.

Discovering Allowed Parameters

To read an allowlist from your code, query the subfeature detail endpoint:
The response includes a provider_params object mapping each provider to its accepted parameter paths. Abridged to three of the providers:
Each entry is a path in the provider’s own request format, lowercased, with nested keys joined by dots. Send the parameter as a nested object, in the casing the provider documents. videogenerationconfig.seed for Amazon means:
Likewise, Google’s aspectratio is sent as aspectRatio. The allowlist check ignores case, so a lowercased aspectratio passes it, but the provider then receives a key it does not recognize. An empty list means the provider accepts no provider_params, and null means the subfeature does not restrict them. To list every subfeature that restricts provider_params, call GET /v3/info?include=schemas (see List Expert Models) and keep the subfeatures whose provider_params is not null. You can also check the documentation_url field returned for each model in GET /v3/info to view the provider’s official documentation.

Important Notes

  • Available parameters vary by provider and feature. Refer to the provider’s own documentation for what each one does.
  • provider_params are sent to every provider the request reaches, including fallbacks. On subfeatures without an allowlist, a parameter one fallback provider does not support can make that attempt fail.

Next Steps

Bring Your Own Key

Use your own provider API keys for full control over costs and limits