Create Hosted Provider

Configure a provider this deployment will serve hosted inference on.

provider is the any-llm implementation. name is what requests address it by (name:model), defaulting to provider; a name of its own lets two endpoints of one implementation coexist. api_key may be left out for a backend that needs none, or for an endpoint of its own (api_base), which is called with a placeholder key.

client_args is whatever the provider's SDK client needs beyond the key (Bedrock's region and IAM pair), the same shape an organization provider key takes. Values under credential-shaped names come back masked. restricted_to_organization_id keeps the provider to one organization; every other one is served as if it were not configured.

One hosted provider, known by its name, its implementation and the tail of its key.

No shape in this section carries key material: a stored credential is known by its last four characters and nothing else, client_args goes out with credential-shaped values masked, and api_base with the password in its userinfo and its query values masked.

name is what requests address and every route takes; provider is the any-llm implementation. source says where the provider is defined. A config provider comes from the hosted_providers: block, has no row and so no id or timestamps, and is changed by editing the configuration rather than through this API; its models are administered as a stored provider's are. shadows_config marks a stored provider that wins over a configuration entry of the same name, which serves again once the row is deleted. has_api_key is false for one stored without a key, and decryptable false for one whose key or extras no configured OTARI_SECRET_KEY reads, which serves nothing until re-entered.