Skip to main content
Bring your own keys (BYOK) connects your workspace’s provider account to Deepline. Your provider bills calls that use this connection. Deepline compute or other usage charges can still apply. Managed access uses Deepline credentials and billing when the action supports this mode.

Connection contract

Each connection belongs to one workspace. Only workspace owners and admins can connect integrations. The provider’s current connection form defines the required fields and supported authentication method. See Provider setup. For supported credential-form providers, POST /api/v2/integrations/connect accepts provider and credentials. A representative Icypeas request body is:
The endpoint also retains the api_key compatibility input for applicable single-key providers. OAuth and specialized integrations use their own connection procedures. This payload does not connect every OAuth provider.

Managed and BYOK eligibility

Each action defines its supported billing modes and price. A connected provider does not imply that every action supports both modes. Inspect the live tool contract and the provider rate cards for the operation you use. Provider environment variables in an operator’s server configuration are not a hosted customer connection method. Setting a provider key in your local shell does not send it through the hosted CLI. Store workspace credentials using the connection flow, not in Play source or tool input. For setup, see Connect an integration. For the tradeoffs, see BYOK governance and economics.