Introduction

Voicebip gives your AI agents a real presence on the phone network. With one API you can provision a Nigerian phone number, a WhatsApp identity, and SMS capability, then point them at an agent that talks to callers, answers messages, and takes actions on your systems. It runs on NCC-licensed Nigerian carrier infrastructure built by Temlio Communications Limited — so you have numbers that are real +234 DIDs on Nigeria Telecom Provider.

If you’ve used a voice-AI platform before, Voicebip will feel familiar — with two differences that matter here: it’s Nigeria-first (local carrier numbers, Naira billing, English + Hausa/Yoruba/Igbo/Pidgin), and it’s multi-channel (voice, WhatsApp, and SMS behind one agent, not voice alone).

How it works

A call or message flows through the same shape every time: Voicebip handles the telephony and speech, your agent supplies the intelligence, and you get events back.

Caller / customer ──▶ Voicebip (carrier + STT/TTS) ──▶ your agent (AI)
│ answers, or calls a tool
◀── spoken reply / WhatsApp message ◀────────────┘
webhooks to your server (call.completed, message.received, …)

For voice, Voicebip answers the call, transcribes the caller (speech-to-text), runs your agent, and speaks the reply (text-to-speech) — managing barge-in, endpointing, and carrier failover for you. For WhatsApp and SMS it delivers inbound messages and sends your replies. Every meaningful moment is emitted as a signed webhook.

What you can build

Two ways to power your agent

Every agent runs one of two ways. Pick per agent — it’s a single field (ai_provider).

Hosted AIBring Your Own Model (BYOM)
Who runs the LLMVoicebip’s hosted modelYour endpoint
You provideA system_prompt (and optional tools + knowledge base)A webhook_url that returns replies
Best forFastest path to a working agent; tool-calling and RAG built inFull control over the model, prompt, and data residency
GuideAgents · Tool-callingBYOM

Both share the same telephony, transcription, recording, and webhook plumbing — the only difference is where the thinking happens.

Core concepts

A quick glossary before you dive in:

  • Agent — the AI persona that handles calls and messages. Owns a prompt, a voice, and (optionally) tools and a knowledge base. Hosted or BYOM. See Agents.
  • Number — a phone identity you provision: a Nigerian geographic DID (geo_did), a mobile virtual number, or an international DID. Bound to an agent, and enabled for voice / sms / whatsapp channels. See Phone Numbers.
  • Hosted AI vs BYOM — whether Voicebip runs the model (hosted) or relays each turn to your server (BYOM). See above.
  • Knowledge Base — your documents (PDF/DOCX/TXT/URL), chunked and embedded so a hosted agent can answer from them (RAG). See Knowledge Base.
  • Campaign — an outbound run over a list of recipients (voice, SMS, or WhatsApp), with pacing and retries handled for you. See Campaigns.
  • Webhook — an HTTPS endpoint we POST events to (call.completed, message.received, …), signed with HMAC-SHA256 so you can trust them. See Webhooks.

Get started

Base URL https://api.voicebip.com/v1 — all endpoints are versioned under /v1/. Auth Authorization: Bearer pk_xxx. Timestamps are ISO 8601 UTC and phone numbers are E.164 (+234…). Sandbox keys (pk_test_) route to synthetic call/message lifecycles with real signatures and zero billing.

Developer tools