AI Provider Integration Overview

Choose an AI provider, create a protected API credential, select a model, control spending and test Wemblo connectivity.

What this guide helps you do

Choose an AI provider, create a protected API credential, select a model, control spending and test Wemblo connectivity.

Who should use it

Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.

Before you begin

  • Use the correct workspace and minimum required role.
  • Use a business-controlled provider account where applicable.
  • Understand provider billing, usage and data settings.
  • Use fictional Pakistan test data.
  • Define human handover before enabling automatic replies or calls.

Main concepts and fields

Concept / FieldMeaning or Use
Provider AccountBusiness-controlled external account.
Project / WorkspaceProvider container for billing and keys.
API KeySecret credential.
ModelSelected AI model.
Provider BudgetExternal cost control.
Wemblo AI LimitPlan or add-on capacity.

Step-by-step instructions

  1. Compare provider availability, models, data terms and cost.
  2. Create a business provider account/project.
  3. Enable billing or credits if required.
  4. Create a restricted key.
  5. Enter it only in Wemblo.
  6. Select the model.
  7. Set provider and Wemblo usage controls.
  8. Test.
  9. Record rotation and revocation.

Test and verification

  1. Run one short factual test.
  2. Run one multilingual test.
  3. Review provider usage/billing.
  4. Confirm unauthorized users cannot see the key.

Common issues and solutions

IssueWhat to Check
UnauthorizedKey, project and provider account.
Model missingProvider/model access and Wemblo support.
Rate limitProvider limit and request volume.
Cost spikeModel, volume, retries and output length.

Security, privacy, consent, cost and provider notes

  • AI-provider charges and Wemblo AI-action usage are separate controls.
  • Do not expose provider keys or customer data in screenshots, tickets or client-side code.
  • Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
  • Do not promise perfect accuracy or guaranteed business outcomes.

Last reviewed: