Is ClawCall a direct alternative to AgentPhone?

They overlap but are different shapes. ClawCall is a finished outbound AI calling product that ships with a skill for Claude Code, Cursor, ClawHub, and OpenClaw — you call the hosted REST API at api.clawcall.dev and get a transcript and recording back. AgentPhone is YC-backed infrastructure that gives every AI agent its own US or Canadian phone number and routes inbound voice and SMS to one webhook. If you want an agent that places calls today, ClawCall is closer. If you want each of your agents to own a phone number for inbound traffic, AgentPhone is closer. Switching between them is mostly rewriting your handler — there is no shared portable agent format.

Which one supports inbound calls?

AgentPhone is built around inbound: voice and SMS to your agent's number are transcribed in real time and pushed to your webhook as text, and your text replies are converted back to speech. ClawCall is outbound-first — POST /call dials any US number for you — and offers inbound on the Unlimited Reserve Plus tier at $14.99/mo, which adds an AI inbound assistant on your reserved private number. For multi-tenant inbound at scale, AgentPhone's per-agent-number model is the more natural fit; for one consumer or developer who wants a single inbound number alongside outbound, Reserve Plus is enough.

Does either guarantee the AI will disclose itself or avoid voicemail?

ClawCall enforces it as a product rule: the agent always discloses it is an AI when asked, can leave voicemail when instructed, and never makes unsolicited sales or robocalls. That is a non-negotiable platform-level behavior, not a prompt suggestion. AgentPhone is infrastructure — your agent's prompt controls its behavior, so disclosure and voicemail policy are your responsibility. That is appropriate for a number-provisioning layer, but it means consumer-facing builders on AgentPhone need to encode those behaviors themselves and own the regulatory and brand risk that comes with them.

Which one should I pick if I just want my AI to call the dentist?

ClawCall. The use case it is explicitly built for is consumer chores in the US: doctor and dentist appointments, restaurant reservations, disputing medical and utility bills, canceling subscriptions, airline rebookings, DMV, insurance, and eliminating hold time. The no-card trial of 30 calls and 30 minutes, whichever lasts later lets you confirm it works before committing to $4.99/mo. AgentPhone is built for teams shipping agents that need their own phone identity for inbound calls and SMS, not for the one-off consumer outbound task.

Comparison

ClawCall vs AgentPhone

ClawCall is an AI phone-calling product that dials any US number, navigates phone trees, waits on hold, talks to whoever answers, and returns a transcript and recording — reachable through a web app, SMS/iMessage, and a REST API at api.clawcall.dev. AgentPhone is a Y Combinator-backed developer API that provisions US and Canadian phone numbers for AI agents and routes inbound voice and SMS to a single webhook, transcribing voice to text and converting your agent's text replies back to speech. If you are building a multi-tenant agent platform where each agent needs its own persistent phone identity for inbound calls and SMS, AgentPhone is the more direct fit. If you are an AI coding agent (or a builder of one) that needs to place real outbound phone calls — book a doctor, dispute a bill, sit on hold with the airline — and prefer a drop-in skill over wiring up a webhook, ClawCall ships that today with a SKILL.md for Claude Code, Cursor, ClawHub, and OpenClaw. ClawCall also bundles the voice stack (Telnyx + Deepgram Voice Agent + ElevenLabs), enforces an AI-honesty rule, can leave voicemail when instructed, and charges flat $4.99–$14.99 per month with a no-card free trial of 30 calls and 30 minutes, whichever lasts later instead of per-minute billing. The two products solve different shapes of the "AI on the phone" problem; pick by whether you want infrastructure to assemble or a finished calling agent to invoke.

Feature comparison

Feature	ClawCall	AgentPhone
Primary shape	Finished AI calling product + drop-in agent skill	Developer API for phone-number infrastructure
Core promise	Your agent makes a real outbound call and returns transcript + recording	Your agent gets a phone number; inbound voice and SMS arrive at one webhook
Pricing model	Flat monthly: $4.99 / $8.99 / $14.99; 30 calls and 30 minutes, whichever lasts later, no card	Unspecified (pricing page not in research)
Number geography	US only (+1 NANP)	US and Canada at launch; more countries planned
Inbound vs outbound	Outbound by default; inbound on Unlimited Reserve Plus tier ($14.99/mo)	Inbound voice and SMS via webhook; outbound posture unspecified
Integration surface	REST API + agent skill for Claude Code, Cursor, ClawHub, OpenClaw	REST API, MCP server, NPM package
SMS	SMS/iMessage user-facing interface; no outbound SMS via public API	Inbound SMS handled in the same webhook as voice
Voice stack	Telnyx + Deepgram Voice Agent + ElevenLabs, managed	AgentPhone handles TTS; inbound voice sent to your webhook as text
AI-honesty rule	Always discloses it is an AI when asked; can leave voicemail when instructed	Unspecified (your agent's prompt controls behavior)
Auth model	Tri-auth: Clerk session, API key, anonymous IP with auto-issued proto-key	Unspecified
Open source / community	Docs under CC BY 4.0; agent skill open	Public GitHub org and Discord community; license unspecified
Backing	Independent	Y Combinator-backed

Choose ClawCall if…

You want an AI coding agent (Claude Code, Cursor, ClawHub, OpenClaw) to place real outbound phone calls today via a drop-in skill — not wire up a webhook.
You need an end-to-end outbound calling product (dial, IVR navigation, hold, transcript, recording) rather than phone-number infrastructure you compose yourself.
You prefer flat monthly pricing ($4.99–$14.99) with a no-card trial of 30 calls and 30 minutes, whichever lasts later over per-minute telecom-style billing.
You care about an enforced AI-honesty rule and instruction-controlled voicemail / no-robocall posture for consumer-facing calls.
You want SMS and iMessage as a user-facing channel into the same agent, not just as a developer webhook event.
Your use cases are consumer chores in the US: appointments, reservations, bill disputes, cancellations, airline rebooking, DMV, hold-time elimination.

Try ClawCall free →

Choose AgentPhone if…

You are building a multi-tenant agent platform where each agent needs a persistent, dedicated phone number for inbound calls and SMS — AgentPhone is purpose-built for that identity layer.
You need Canadian numbers in addition to US numbers at launch; ClawCall is US-only today.
You want a single unified webhook event shape for both inbound voice and SMS so your agent code stays uniform across channels.
You value Y Combinator backing, a public GitHub org, and a Discord community for an early-stage infrastructure vendor.

Visit AgentPhone →

Product shape: finished calling agent vs phone-number infrastructure

The clearest way to separate these two is to ask what arrives in your inbox the day after you sign up. With ClawCall, what arrives is a working agent: you POST to /call with a US number and an instruction, get a call_id back immediately, poll GET /call/:id until lifecycle=finalized, and read the transcript and recording. The voice stack — Telnyx for telephony, Deepgram Voice Agent for realtime turn-taking, ElevenLabs for speech — is already glued together and managed. The agent skill installs into Claude Code, Cursor, ClawHub, or OpenClaw, so a coding agent can place a call in the same session it writes code. With AgentPhone, what arrives is a phone number and a webhook contract: inbound voice is transcribed in real time and pushed to your webhook as text, your agent replies with text, and AgentPhone runs the text-to-speech layer using the same event shape for both voice and messaging. You still own the agent's brain, its prompt, its tools, and its memory. That is the right shape if you are shipping a platform where every tenant agent needs its own persistent number; it is more work than you want if your goal is simply to have an AI call the dentist.

Pricing posture: flat consumer-style plans vs developer API

ClawCall publishes three flat monthly plans — Unlimited at $4.99/mo (unlimited calls from a shared outbound number pool), Unlimited Reserve at $8.99/mo (adds one private reserved inbound number), and Unlimited Reserve Plus at $14.99/mo (adds an AI inbound assistant on that reserved number) — plus a free trial of 30 calls and 30 minutes, whichever lasts later that does not ask for a credit card. There is no per-minute meter, no annual contract, and legacy minute-pack purchases were retired. The implicit bet is that a consumer or solo developer wants to know the bill in advance and not babysit a usage dial. AgentPhone's public site emphasizes that it is built for teams shipping agents and provisions numbers instantly through the API, but pricing is not on the pages our research crawled, so we list it as Unspecified rather than guess. Developers evaluating AgentPhone should expect a per-number, per-minute, or per-message model in line with telecom-style infrastructure vendors and should confirm rates on AgentPhone's pricing page directly. If predictable flat pricing matters more than elasticity, ClawCall's posture is friendlier.

Integration: agent skill vs unified webhook

Both products want to live inside an AI agent's tool belt, but they hand you different primitives. ClawCall ships an agent skill — a SKILL.md plus tools — that drops into Claude Code, Cursor, ClawHub, and OpenClaw, so the agent learns to call the hosted REST API at api.clawcall.dev without bespoke wiring. The tri-auth flow means an anonymous POST /call auto-issues a proto-key returned in the response that survives sign-up via linking, so the agent can start calling before any account exists. AgentPhone exposes a REST API, an MCP server, and an NPM package, and routes both inbound voice and inbound SMS into one webhook event shape — so an agent's handler code looks the same whether the user texted or called. That uniformity is genuinely useful when you are building a product where every agent is a long-lived entity with its own number. ClawCall does not ship an MCP server today; AgentPhone's research surface does not describe a packaged Claude Code or Cursor skill. Pick by which primitive matches your agent's runtime, and remember that an outbound call from AgentPhone is not a documented entry point in the materials we crawled.

Geography, channels, and the AI-honesty rule

AgentPhone provisions US and Canadian phone numbers instantly through the API and tells customers more countries are coming soon. ClawCall is US-only today (+1 NANP), English only, and capped at roughly three concurrent calls per account by default — the bridge tool that hands a live call back to the user consumes two of those numbers. On channels, AgentPhone treats inbound voice and inbound SMS as siblings in one webhook; ClawCall offers SMS and iMessage as a user-facing interface into the agent but does not expose outbound SMS through its public API. The hard ClawCall differentiator that does not appear in AgentPhone's marketing is behavioral: ClawCall always discloses it is an AI when asked, can leave voicemail when instructed, and never makes unsolicited sales or robocalls. For a consumer-facing calling agent, that posture is a brand and compliance asset; for an infrastructure vendor it is correctly out of scope, because the agent's prompt and behavior are the customer's responsibility, not the platform's.

Frequently asked

Is ClawCall a direct alternative to AgentPhone?: They overlap but are different shapes. ClawCall is a finished outbound AI calling product that ships with a skill for Claude Code, Cursor, ClawHub, and OpenClaw — you call the hosted REST API at api.clawcall.dev and get a transcript and recording back. AgentPhone is YC-backed infrastructure that gives every AI agent its own US or Canadian phone number and routes inbound voice and SMS to one webhook. If you want an agent that places calls today, ClawCall is closer. If you want each of your agents to own a phone number for inbound traffic, AgentPhone is closer. Switching between them is mostly rewriting your handler — there is no shared portable agent format.
How does pricing compare?: ClawCall publishes flat monthly plans: Unlimited at $4.99/mo, Unlimited Reserve at $8.99/mo, and Unlimited Reserve Plus at $14.99/mo, with a free trial of 30 calls and 30 minutes, whichever lasts later that does not require a credit card. Legacy minute-pack purchases are discontinued. AgentPhone's pricing was not on the pages our research crawled, so we list it as Unspecified rather than guess; check AgentPhone's pricing page directly. Developers should expect AgentPhone to lean toward a telecom-style usage meter given its infrastructure positioning, and ClawCall to lean toward predictable flat consumer-style pricing — a meaningful gap once you cross a few hours of monthly call time.
Which one supports inbound calls?: AgentPhone is built around inbound: voice and SMS to your agent's number are transcribed in real time and pushed to your webhook as text, and your text replies are converted back to speech. ClawCall is outbound-first — POST /call dials any US number for you — and offers inbound on the Unlimited Reserve Plus tier at $14.99/mo, which adds an AI inbound assistant on your reserved private number. For multi-tenant inbound at scale, AgentPhone's per-agent-number model is the more natural fit; for one consumer or developer who wants a single inbound number alongside outbound, Reserve Plus is enough.
Can I use either inside an AI coding agent like Claude Code or Cursor?: ClawCall ships a drop-in agent skill that installs directly into Claude Code, Cursor, ClawHub, and OpenClaw. Once installed, the agent can POST /call with a US number and instruction and poll GET /call/:id until lifecycle=finalized. The first anonymous call auto-issues a proto-key returned in the response that survives sign-up via linking, so the agent can start working before an account exists. AgentPhone exposes a REST API, an MCP server, and an NPM package — usable from coding agents, but our research did not surface a packaged Claude Code or Cursor skill, so wiring is on you.
Does either guarantee the AI will disclose itself or avoid voicemail?: ClawCall enforces it as a product rule: the agent always discloses it is an AI when asked, can leave voicemail when instructed, and never makes unsolicited sales or robocalls. That is a non-negotiable platform-level behavior, not a prompt suggestion. AgentPhone is infrastructure — your agent's prompt controls its behavior, so disclosure and voicemail policy are your responsibility. That is appropriate for a number-provisioning layer, but it means consumer-facing builders on AgentPhone need to encode those behaviors themselves and own the regulatory and brand risk that comes with them.
Which one should I pick if I just want my AI to call the dentist?: ClawCall. The use case it is explicitly built for is consumer chores in the US: doctor and dentist appointments, restaurant reservations, disputing medical and utility bills, canceling subscriptions, airline rebookings, DMV, insurance, and eliminating hold time. The no-card trial of 30 calls and 30 minutes, whichever lasts later lets you confirm it works before committing to $4.99/mo. AgentPhone is built for teams shipping agents that need their own phone identity for inbound calls and SMS, not for the one-off consumer outbound task.

Other comparisons: ClawCall vs Bland AI · ClawCall vs Vapi · ClawCall vs Goodcall · ClawCall vs ClawTalk · ClawCall vs ClawdTalk · ClawCall vs PollyReach · ClawCall vs CallBuddy · ClawCall vs Chirp AI · ClawCall vs CallFluent AI · ClawCall vs Jarvis.cx · ClawCall vs Retell AI · ClawCall vs Synthflow · ClawCall vs ClawCall vs Vocode · ClawCall vs Air.ai · ClawCall vs Regal · ClawCall vs Rosie · ClawCall vs Numa · ClawCall vs Replicant · ClawCall vs Apple Hold For Me (Hold Assist) · ClawCall vs HoldForMe.ai