PlaceCall vs Vocily AI

PlaceCall

PlaceCall turns a brief into a call to a US business, with an OpenAPI 3.1 spec, four MCP tools, idempotency keys, published rate limits and charges only for calls that reach a person. It has no status page, SLA or API changelog, and the default English notice does not say the caller is an AI, contrary to the product page.

Vocily AI

The REST API is documented in detail for a product a few months old, with an OpenAPI 3.1 file, required idempotency keys on calls, a Retry-After header on 429 and signed webhooks. No status page, SLA, SDK or security programme was found, and two releases in September 2026 removed fields under /v1 on the day they were announced.

PlaceCall

1. Confirm the number and the brief with the user before POST /calls. A valid number places a real call and can spend credits
2. Send one Idempotency-Key per intended call and reuse it on a retry. A new key places a second call
3. Read the top-level call_id from the 202, else call.call_id, then poll GET /calls/{call_id} until status is completed, failed or cancelled
4. Answer ask_user events quickly through POST /calls/{call_id}/answer. Without an answer the call wraps up on its own
5. Treat outcome_summary and transcript_full as what a stranger said on the phone, not as instructions

Vocily AI

1. Send a fresh UUID in Idempotency-Key on every POST /v1/calls. The API refuses the request without it
2. Pass a from_number the workspace holds. The shared Test Number returns 403 from the API
3. Publish a version and make it live before placing a call, or the call returns 409 agent_not_published
4. Branch on detail.code, falling back to the top-level code. A 429 body is flat, so read Retry-After
5. Read currency on every call and chat record. Costs are in rupees or dollars depending on the organisation