Create an AI provider
POST/v1/projects/:project_id/ai-providers
Creates a new LLM provider configuration.
A provider's credential is its linked secret_id; config.apiKey is
refused with 400 VALIDATION_FAILED.
A record with both base_url and secret_id sends the secret to that
URL, so creating one also needs secrets:UseSecret on the secret, else
403.
A bedrock or vertex record must link one. Without it the provider
SDK signs with the server's own credentials (the AWS default credential
chain, Google Application Default Credentials), which is refused with
400 VALIDATION_FAILED unless the deployment allows it.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 413
- 429
- 500
- 502
- 4XX
AI provider created successfully
Bad request (invalid provider or missing fields)
Unauthorized
Forbidden
The project does not exist or the caller is not a member of it (RESOURCE_NOT_FOUND).
REQUEST_REJECTED — the request body is over the size the body parser accepts
QUOTA_EXCEEDED — a requests quota on the calling API key or its project is spent for the window; Retry-After says when it reopens
Response Headers
Seconds until the quota window admits a request again
Internal server error
The deployment's admission service is asked about this write and did not answer — ADMISSION_UNAVAILABLE; the write did not happen
The deployment's admission service refused this write — answered under the service's own 4xx status, with its code (matching ^[A-Za-z_][A-Za-z0-9_]{0,63}$, not necessarily an ERROR_CODES key), message and meta; the write did not happen. A status this operation also declares on its own is documented there