Delegate the messy middle
ClawCall dials, navigates phone menus, waits through queues, speaks with the person who answers, and follows your task boundaries.
A finished phone call for your product
Give your app a phone call—not a voice stack.
Send ClawCall a destination and a clear task. It handles the phone tree, hold time, conversation, and authorized voicemail, then returns the network outcome and transcript evidence your application needs. Use REST from a trusted backend or hosted OAuth MCP from a compatible AI agent.
You provideDestination · task · boundaries
ClawCall handlesIVR · hold · conversation
Your app receivesOutcome · transcript evidence
Add phone work without rebuilding telephony
ClawCall gives your product a finished calling capability while leaving authorization, application state, and the final user decision under your control.
Keep authority in your product
Your trusted system confirms the destination, goal, known facts, fallbacks, and decisions the caller may or may not make.
Keep continuity outside the call
Your application stores its request correlation, ClawCall call identifier, latest state, transcript retrieval, and any follow-up decision.
Know what happened on the line
Use the network outcome to understand the connection and the transcript evidence actually captured to decide whether the real-world task succeeded.
Choose the connection that fits your runtime
Both paths reach the same ClawCall calling capability. The difference is who owns the authorization and orchestration.
Your backend owns the workflow
Use the REST API when your server can protect a ClawCall API key, bind each call to a user or approved workflow, and persist the result in your application.
Open the API reference →The agent gets bounded ClawCall tools
Use https://api.clawcall.dev/mcp when the host supports remote Streamable HTTP MCP and OAuth. The host receives revocable tokens—not a ClawCall API key.
Keep secrets out of prompts and browsers
Do not place a ClawCall API key in client JavaScript, a consumer prompt, a URL, or a public repository. Use a trusted backend or the hosted OAuth flow.
Retries stay inside the user’s authority
A callback, retry, or small call set can support one objective, but it must preserve the authorized goal, destinations, and decision limits.
ClawCall runs the call; your app keeps continuity
A clear division of responsibility makes a phone call easier to recover, explain, and act on inside a larger product workflow.
Persist the approved briefing
Keep the principal, destination, objective, known facts, alternatives, fallback behavior, and any decision that must return to the user.
Persist correlation and latest state
Store your own request or job ID beside the ClawCall call identifier so a worker restart does not orphan the external action.
Read the captured transcript
Record whether transcript retrieval succeeded and which captured evidence supports the conclusion your product shows to the user.
Treat recording access as temporary
Recording links expire. Keep the durable call reference and retrieval state your product needs; use the transcript for longer-lived task review.
Return evidence your product can use
ClawCall separates what happened on the phone network from what happened in the task, so your app does not mistake a connected line for a completed goal.
Model exactly ten terminal outcomes
answered · no_answer · busy · rejected · invalid_number · unreachable · network_error · cancelled · system_error · failed
Judge success from the transcript
The transcript shows what was asked, answered, agreed, refused, or left unresolved. Do not treat answered as proof that the user’s goal succeeded.
Keep mailbox behavior in context
Voicemail is not a network outcome. ClawCall can leave a concise message when the user’s instructions authorize it, and the transcript records what happened.
Return choices to the user
If the call surfaces a new price, alternative, verification request, or commitment outside the briefing, pause instead of inferring consent. When the user joins, post-join recording and transcription follow the account’s “Record bridged conversations” setting, so captured evidence may end at the bridge.
Best fit for the current ClawCall API
Use ClawCall for focused, user-directed US phone work
- Language and destination: English-language calls to US +1 numbers.
- On-call work: IVR navigation, hold, conversation, instructed voicemail, live join, and transcript-backed results.
- Access: REST from a trusted application or 11 bounded tools through OAuth-protected hosted MCP for compatible AI hosts.
- Inbound: Unlimited Reserve adds a private reserved caller-ID number; Reserve Plus adds AI inbound answering on an active reserved number.
- Pricing: the free trial includes 30 calls and 30 minutes, whichever lasts later, with no credit card; paid plans are $4.99, $8.99, and $14.99 per month.
- Limits: not for robocalls, predictive dialing, or bulk/high-volume automated outreach or sales campaigns; no current HIPAA, PCI, or SOC 2 attestation.
Start with the path that matches your product
ClawCall is ready when your application or agent needs a real phone call completed. Choose the next step for your runtime.
Build from the current REST contract
Use the API docs for current authentication, request fields, call state, outcomes, transcripts, recordings, and errors.
Open API docs →Connect through hosted MCP
Review host support, OAuth permissions, and the 11 bounded ClawCall tools before connecting your AI agent.
Connect an AI agent →See ClawCall complete a real call
Start with a US +1 number you control and a bounded task, then review the outcome and transcript when the call ends.
Try a ClawCall →Confirm fit before production
Review pricing, inbound eligibility, current product limits, and security posture for the workload you plan to ship.
ClawCall API questions
- What does ClawCall handle for my application?
- Your application provides an English-language US +1 destination, a user-directed task, known facts, and decision boundaries. ClawCall handles dialing, IVR navigation, hold time, the live conversation, and a concise voicemail when the instructions authorize one. Your application receives call state, a network outcome, and transcript evidence.
- Should my product use REST or hosted MCP?
- Use REST when a trusted backend owns the credential and application workflow. Use ClawCall’s OAuth-protected hosted MCP path when a compatible AI host supports remote Streamable HTTP MCP and OAuth. The hosted path keeps a ClawCall API key out of the AI host and exposes 11 bounded tools.
- What state should my application keep?
- Keep your user or workflow identity, the authorized destination and task boundaries, request correlation, the ClawCall call identifier, the latest observed call state, and what transcript evidence was captured. Recording links are temporary access rather than durable application state.
- Which terminal network outcomes should my application model?
- The closed set is answered, no_answer, busy, rejected, invalid_number, unreachable, network_error, cancelled, system_error, failed. Voicemail is not a network outcome. Reaching a mailbox or leaving an instructed message belongs in agent behavior and transcript context, while the network result remains one of the ten values above.
- Can one user-directed workflow place more than one call?
- Yes. A bounded objective can include a callback, a retry, or a small comparison set when the user-authorized goal and decision limits remain clear. ClawCall is not for robocalls, predictive dialing, or bulk/high-volume automated outreach or sales campaigns.
Verified product details
ClawCall behavior, connection paths, plan boundaries, and security limits are grounded in the current first-party product pages below.
- ClawCall API and hosted MCP documentation — authorization paths, call evidence, recordings, and inbound boundaries; checked 2026-09-03.
- ClawCall for AI agents — hosted endpoint, OAuth model, 11 tools, and host compatibility; checked 2026-09-03.
- ClawCall pricing — trial, Unlimited, Reserve, Reserve Plus, language, and destination scope; checked 2026-09-03.
- ClawCall security and data handling — current security and attestation boundaries; checked 2026-09-03.
- US Federal Trade Commission: Telemarketing Sales Rule guide — bulk telemarketing programs as a separate regulated workload; checked 2026-09-03.
The FTC source is informational, not legal advice. ClawCall does not claim a reliability, latency, completion-rate, adoption, or ranking benchmark on this page.