Console API
BYOK Setup
Create and manage custom provider keys (BYOK)
POST
Create and manage custom provider keys (BYOK - Bring Your Own Key) for AWS Bedrock, Google Vertex AI, Azure, and other LLM providers. This allows you to use your own credentials instead of Edgee’s shared keys.
Request Body
string
required
The provider type. Supported values:
anthropic, openai, google_vertex_ai, google_gemini, mistral, deepseek, xai, zai, nvidia_nim, fireworks, scaleway, bedrock, bedrock-mantle, azure, alibaba_cloud, github_copilot, custom_openai_compatible, baseten, cerebras_cloud, deepinfra, groq, inceptron, ionos, meta, minimax, nebius_token_factory, nscale, ovhcloud, poolside, tensorx, together_ai, umans_aistring
required
The credentials for the provider. Format depends on the provider type:
- Standard providers (anthropic, openai, mistral, deepseek, xai, zai, nvidia_nim, google_gemini, fireworks, scaleway, github_copilot, baseten, cerebras_cloud, deepinfra, groq, inceptron, ionos, meta, minimax, nebius_token_factory, nscale, ovhcloud, poolside, tensorx, together_ai, umans_ai): API key as string
- Bedrock: JSON string with region-keyed credentials
- Azure: JSON string with endpoint and api_key
- Alibaba Cloud: JSON string with workspace_id, api_key, and optional region (defaults to
eu-central-1) - Google Vertex AI: Service account JSON string
- Custom OpenAI-compatible: JSON string with base_url and optional api_key
string
required
A descriptive name for this provider key (e.g., “Production Vertex AI Key”). Max 100 characters.
array
Array of Edgee API key IDs to assign this provider key to. Omit or leave empty to create an organization-level provider key that applies to all API keys.
array
Array of squad IDs to assign this provider key to. Every member of a listed squad uses these credentials.
boolean
Update only. Set to
false to disable the provider key without deleting it.Response
string
Unique identifier for the provider key
string
The provider type (e.g., “google_vertex_ai”)
string
The name of the provider key
string
ISO 8601 timestamp of when the provider key was created
string
User ID of who created the provider key
Examples
Tips
- Organization-level keys: Leave
api_key_idsempty to apply the provider key to your entire organization - API-key-specific assignments: Specify API key IDs to restrict the provider key to specific API keys only
- Security: Never commit provider credentials to version control. Use environment variables or secure credential management systems
- Multi-region Bedrock: For AWS Bedrock, you can specify different credentials for different regions. Use
"global"as the key for a default region.
Credential Formats
Google Vertex AI
Provide the entire service account JSON as a string:AWS Bedrock
Provide region-keyed credentials:Azure
Provide endpoint and API key:Alibaba Cloud
Provide your Model Studio Workspace ID, API key, and (optionally) region. The gateway resolves these intohttps://{workspace_id}.{region}.maas.aliyuncs.com/compatible-mode/v1. region defaults to eu-central-1 (Germany/Frankfurt) if omitted. Supported regions: eu-central-1 (Germany/Frankfurt), cn-beijing (China/Beijing), ap-southeast-1 (Singapore), ap-northeast-1 (Japan/Tokyo), cn-hongkong (China/Hong Kong).