§00 · Overview

Bring Converlane into your agent stack.

Four artefacts, one API key. Pick the surface that matches your tool — MCP for AI coding clients, Skills for any Claude session, OpenAPI for spec-driven frameworks, SDKs for plain code.

Every artefact below talks to the same /api/public/v1/* gateway with the same Authorization: Bearer vv_live_… key. Mint one at /api-keys, top up the wallet at /billing, and you are done with onboarding.

§01

MCP Server

Drop-in stdio server for Claude Code, Cursor, Codex, Cline. Four tools for the four public surfaces.

npx -y vaanivoice-mcp
§02

Claude Skill

Anthropic plugin Skill bundle. Activates when the user asks for voice / meetings / call data.

skills/vaanivoice/
§03

OpenAPI 3.1

Spec for LangChain, Cursor agent tools, Stainless, Speakeasy and any framework that consumes specs.

/openapi/v1/vaanivoice.yaml
§04

Language SDKs

Idiomatic clients for Node and Python — thin, typed, and faithful to the gateway shapes.

npm i vaanivoice · pip install vaanivoice

What you get, in one paragraph.

The MCP server exposes four tools — vaani_create_textvoice_session, vaani_create_voicebot_session, vaani_create_meeting_agent_room, vaani_create_plain_meeting_room— to any MCP-aware client. The Claude Skill teaches Claude itself when to reach for Converlane and how to call the gateway with the right body. The OpenAPI 3.1 spec is the canonical contract, served as a static asset with a generous cache header so LangChain/Cursor/agent frameworks can fetch it once and forget. The SDKs are the “just give me a function” option — same shapes, idiomatic types.

Pricing, briefly.

  • textvoice / voicebot — env-driven sell-rate per minute; matches your dashboard PAYG rate exactly.
  • meeting-agent (Vikash + LiveKit) — 8 paise / sec.
  • meeting (LiveKit only) — 1 paise / sec.

A 100-paise reservation floor is held at session-open and reconciled when the session closes. 402 insufficient_balance responses include a setup_url pointing to billing.