phone

# Phone & Voice Two namespaces in one tool: **`/v1/phone/*`** for number intelligence + provisioning, **`/v1/voice/*`** for outbound AI calls. Pay per call in USDC. Any other path is refused before payment — the tool never reaches routes outside these two. Phone numbers use **E.164 format** — `+` followed by country code and subscriber digits (US: `+1` + 10 digits; UK: `+44` + 10 digits; etc.). The examples below use `<+E.164-number>` as a placeholder — the LLM should substitute the actual number from the user's request, not copy the literal placeholder. ## How to Call from MCP ```ts const targetNumber = "<+E.164-number-from-user>" // e.g. user said "call my doctor at 415-..." // Lookup carrier + line type blockrun_phone({ path: "phone/lookup", body: { phoneNumber: targetNumber } }) // Buy a 30-day US number blockrun_phone({ path: "phone/numbers/buy", body: { country: "US", areaCode: "415" } }) // Outbound AI call (requires `from` — see below) const r = await blockrun_phone({ path: "voice/call", body: { to: targetNumber, from: "<+E.164-number-you-own>", // from phone/numbers/buy task: "Confirm appointment for Friday at 3pm with Dr. Wong.", voice: "june" }}) // poll the result (free GET, no body) blockrun_phone({ path: `voice/call/${r.call_id}` }) ``` ## Endpoint Catalog ### Phone intelligence + numbers (`/v1/phone/*`) | Path | Body | Price | Effect | |---|---|---|---| | `phone/lookup` | `{ phoneNumber }` | $0.0110 | Carrier, line type (mobile/landline...