Give your app a phone call—not a voice stack.

curl -X POST https://api.clawcall.dev/call \
  -H 'Content-Type: application/json' \
  -H 'X-Api-Key: clawcall_sk_...' \
  -d '{
    "to": "+1XXXXXXXXXX",
    "task": "Call the pharmacy and ask whether my refill is ready for pickup",
    "voice": "chris"
  }'

Replace clawcall_sk_... with a server-side API key, and keep it out of client code, prompts, and public repositories. Poll until lifecycle is finalized. The example is trimmed. outcome: "answered" only means the line connected, so use captured transcript evidence when present to judge whether the task succeeded. transcript and recording_url can be null. The field-by-field contract lives in the API documentation.

• Delegate the messy middle

  ClawCall dials, navigates phone menus, waits through queues, speaks with the person who answers, and follows your task boundaries.

• Keep authority in your product

  Your trusted system confirms the destination, goal, known facts, fallbacks, and the decisions the caller may or may not make.

• Keep continuity outside the call

  Your application stores its request correlation, the ClawCall call identifier, the latest state, transcript retrieval, and any follow-up decision.

• Know what happened on the line

  The network outcome describes the connection. The transcript evidence actually captured tells you whether the real-world task succeeded.

1. Before the callPersist the approved briefing: the principal, destination, objective, known facts, alternatives, fallback behavior, and any decision that must return to the user.
2. While it runsStore your own request or job ID beside the ClawCall call identifier, so a worker restart does not orphan the external action.
3. When it endsReview transcript evidence when present. Record whether retrieval succeeded and which captured evidence supports the conclusion your product shows the user.
4. For audio reviewTreat 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.

• Model exactly ten terminal outcomes

  The network result is always one of these values.

  • answered
  • no_answer
  • busy
  • rejected
  • invalid_number
  • unreachable
  • network_error
  • cancelled
  • system_error
  • failed

• Judge success from the transcript

  Captured transcript evidence, when present, 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; captured transcript evidence records what happened when present.

• 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.

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 12 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. There is no current HIPAA, PCI, or SOC 2 attestation.

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 captured transcript evidence when present.

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 12 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.

• 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 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.