bitpull.io

Documentation

Everything on this site, in reading order

Start at the top if you are new. Jump straight in if you are not - every page stands on its own and says what it depends on.

Two sets of documentation, and which is which

bitpull.ai/docs is the vendor's own reference and the canonical source for the API and the widget. This site is the developer platform around it: deeper on integration, honest about what does not exist, and it carries the tools. Where the two disagree, the vendor is right about intent and this site tries to be right about behaviour - the data-modes discrepancy on the embed page is a live example.

Getting started

The mental model, then the fastest route to something that talks back.

Developers

The session model, the four extension points, authentication, and what the platform does not expose.

Embedding

Available

The script tag, its attributes, the self-hosted runtime and the headless route.

Examples

Eight complete recipes with the code and the gotcha for each.

Reference

What you call, what it returns, and where the boundary of the public API runs.

API

Available

Health, languages, session create / read / end, token minting, rate limits, the LiveKit handover.

Webhooks

Beta · account flag

The one outbound trigger, what it carries, safe consumption, and the events that do not exist.

Agent tools

Available

Function declarations, JSON Schema parameters, timeouts you can hear, and safety.

SDKs

Planned

None published. A forty-line typed client in TypeScript and Python instead.

Channels and architecture

How a conversation reaches the agent, and what the agent shares across all of them.

Voice infrastructure

Speech to speech, WebRTC and SIP transport, the latency budget, turn taking and barge-in.

Telephony & SIP

Available

Numbers, the provisioning lifecycle, inbound and outbound, transfer, existing PBX systems.

Omnichannel

What is shared between channels, what is deliberately not, and how to design for both.

Knowledge

Import routes, how knowledge is stored, and why there is no retrieval API.

MCP

Research

Not supported in either direction. What that would need, and what to use instead.

Integrations

Per-system guides with the honest status of each, rather than a logo wall.

Directory

Every system, categorised, with its real status and where to go next.

Calendly

Available

The one native calendar connector: OAuth, event types, booking inside real availability.

HubSpot

Via webhook

Contact, transcript note and a gated follow-up task from one webhook.

Shopify

Assisted setup

Order status by voice from the Admin API, through a declared agent tool.

n8n

Via webhook

Self-hosted consumption, where the transcript never leaves your infrastructure.

Free tools

Four browser tools. No account, no key, nothing stored beyond what the tool needs.

Webhook tester

A throwaway inbox URL showing headers and body exactly as they arrived.

Widget generator

Build and preview the embed snippet attribute by attribute.

Voice latency test

Network RTT, jitter, WebRTC availability and microphone latency, with thresholds.

Prompt reviewer

Static review of a voice prompt against the things that break real calls.

Operations

What changed, whether it is up, and what this site is for.

Changelog

Platform and documentation changes, dated, with what each one means for an integration.

Status

A live check against the platform health endpoint, run from this server.

Playground

Planned

Not built. What it would be, and the tools that already cover parts of it.

About

Why this domain exists, how each status is decided, and what it deliberately does not do.

Reading paths

If you want to…Read, in order
Get an agent onto a website todayEmbed → Widget generator → Latency test
Get conversations into a CRMWebhooks → Webhook tester → the integration guide for your system
Let the agent read your systems liveAgent tools → Voice (the latency budget) → Shopify as a worked example
Answer the phoneTelephony → Prompt reviewer → Receptionist recipe
Build the agent into your own productDevelopers → API → SDKs → Own-app recipe
Decide whether the platform fits at allDevelopers (particularly "what is not there") → MCP → SDKs

Conventions on this site

  • Every capability carries a status. Available, beta behind an account flag, assisted setup, via webhook, via API, planned or research. The integrations page has the full legend.
  • No invented endpoints. If it is not on the API page, treat it as not public.
  • No invented payloads. The webhook envelope is not published, so no page here claims to know its field names - capture a real one instead.
  • Third-party code is theirs. Snippets calling HubSpot, Shopify or Slack use those vendors' public APIs and say so.

The reasoning behind all of that, and how each status is decided, is on the about page.