Provider Integrations

Provider integrations allow you to connect your own API keys from external AI services directly to SipPulse AI. Instead of using platform credits, you can use your own accounts with providers like OpenAI, Anthropic, Google, and others.

Benefits of Using Your Own Keys

• Cost Control: Pay directly to the provider with your own pricing tier
• Higher Limits: Access your provider's rate limits instead of shared platform limits
• Direct Billing: Manage costs through your existing provider accounts
• Exclusive Models: Some models may only be available through your own credentials due to their pricing complexity

Page Overview

The Integrations page is divided into two sections:

• Add: Shows providers that are available but not yet configured. Click on any provider tag to add your API key.
• Integrations: Shows your currently configured integrations as cards, displaying the masked API key and applicable models.

Adding a Provider Credential

To add a new provider integration:

1. Navigate to Integrations in the sidebar menu
2. In the Add section, click on the provider you want to configure
3. In the modal that opens, paste your API key in the input field
4. Review the Applicable models that will be unlocked with this integration
5. Click Save

TIP

After adding a credential, requests to those models will use your API key and be billed directly by the provider. Your usage will appear in the dashboard with a cost of R$0.00 since billing is handled by the provider. In some cases, certain models may only become available after adding your credentials.

API Key Validation

When you save a new credential, SipPulse AI validates the API key with the provider to ensure it's valid. If the key is invalid or has insufficient permissions, you'll see an error message and the credential won't be saved.

Replacing a Credential

To replace an existing API key:

1. Navigate to Integrations
2. Find the provider card in the Integrations section
3. Click the edit button (pencil icon) on the card
4. In the modal, you'll see:
   • Current key: Your existing masked API key
   • New API Key: Input field for the replacement key
   • Applicable models: All models that use this provider
5. Enter the new API key in the New API Key field
6. Click Replace

The new key will be validated before saving. Your previous key will be replaced and can no longer be used.

Removing a Credential

To remove a provider integration:

1. Click the edit button (pencil icon) on the provider card
2. Click the Remove button (red, on the left side)
3. Confirm the removal

After removal, requests to that provider's models will use your organization's credits instead of your own API key.

Viewing Applicable Models

Each integration shows which models will use your API key:

• On the card: You'll see the first few applicable models with a "+N" indicator if there are more
• In the modal: The full list of applicable models is displayed, including both LLM models and TTS models (shown with different icons)

This helps you understand exactly which features and models will use your own credits.

Security

Your API keys are protected with enterprise-grade security:

• Encryption: All API keys are encrypted using AES-256-CBC before storage
• Secure Storage: Keys are stored securely and never exposed after saving
• Request-Only Access: Keys are only decrypted at the moment of API requests
• Masked Display: After saving, only a hint (first 4 and last 4 characters) is shown
• No Logging: API keys are never logged or stored in plain text

WARNING

Keep your API keys confidential. If you believe a key has been compromised, remove it from SipPulse AI immediately and regenerate it from the provider's console.

Access Permissions

Only users with Admin or Owner roles can manage provider integrations. This ensures that API credentials are controlled by authorized team members and prevents unauthorized access to billing-sensitive configurations.

Regular team members can use the models enabled by these integrations, but cannot view or modify the credentials themselves.

Integrations vs API Keys

It's important to understand the difference between Provider Integrations and API Keys:

Feature	Provider Integrations	API Keys
Purpose	Connect external AI providers (OpenAI, Anthropic, etc.)	Access SipPulse AI's API
Who manages	Admin/Owner only	All users
Billing	Direct to provider	SipPulse AI credits
Location	Integrations page	API Keys page
Use case	Use your own provider accounts	Integrate SipPulse AI into your apps

FAQ

Can I use both my own keys and platform credits?

When you add a provider credential, calls to that provider's models will use your key. For providers without credentials configured, the platform will use your organization's credits.

How does billing work with my own keys?

When using your own API keys, you are billed directly by the provider (OpenAI, Anthropic, etc.) according to their pricing. SipPulse AI does not charge additional fees for using your own credentials.

What happens if my API key expires or is invalid?

If your API key becomes invalid, requests to that provider will fail. You'll need to update the credential with a valid key. The platform will show an error message indicating the authentication failure.

Can I have multiple keys for the same provider?

Currently, only one credential per provider is supported per organization. If you need to switch keys, edit the existing integration and replace the key.

Where can I get API keys for each provider?

Each provider has their own console for managing API keys:

• OpenAI: OpenAI Platform
• Anthropic: Anthropic Console
• Google AI Studio: Google AI Studio
• Eleven Labs: Eleven Labs