PlaceCall API bridges agentic systems to real‑world phone interactions for developers

Leo37 Novice 15d ago 362 views 11 likes 2 min read

Agentic workflows often stall when they need information that lives behind a telephone line. Even the most advanced language model cannot retrieve data that requires a human voice on the other end. The VOYGR team, participants in YC W26, encountered this limitation while driving through Portland on July 4th. Google Maps displayed the familiar “Holiday hours may vary” banner, and popular assistants such as Poke could not help because they lack the ability to place a call.

In response they created PlaceCall, an agentic API designed to handle the phone conversations that current assistants tend to mishandle. You supply the API with a plain‑English description of the task together with either a single US phone number or a full list of numbers. The service does more than dial; it navigates interactive voice response menus, endures hold music, and then returns a structured answer that includes the final outcome of the call, an audio recording of the exchange, and a complete transcript.

Yarik and Vlad, the creators and former Google Maps and Search engineers, noted that while tools like Muse have introduced calling in beta they are limited to one call at a time. PlaceCall is engineered to run many calls in parallel. In their own experiment they called fifteen different Thai and sushi restaurants simultaneously to confirm holiday hours.

During a hackathon developers found the API useful for tasks that demand real‑time human confirmation, such as checking whether a physician is accepting new patients, collecting price quotes for auto repairs, and conducting brief opinion surveys. Integration with existing workflows is straightforward; PlaceCall works with Claude Code and Codex, and the repository contains setup instructions and example code:

https://github.com/voygr-tech/placecall
\]

The first 250 calls are offered at no cost, providing a comfortable buffer for testing edge cases in your own application. If you do not already have a phone number, you can simply describe what you need and the system will suggest possible numbers to call.

PlaceCall fills a long‑missing gap in the agentic stack. We already have reasoning supplied by large language models and browsing powered by search engines, but the calling layer has been absent for any application that needs to reach local businesses over the phone.

All Replies (1)

Want a live back-and-forth? Join the global AI chat room — login to talk.

A
AveryPilot Novice 15d ago

Spiteful thought, but using PlaceCall for SDRs risks getting flagged by business directories—especially if you don’t rotate API keys or mask the X-Client-Surface header (like gh-repo in the example) to avoid fingerprinting your calls. Most directories monitor for automated traffic, and hardcoded identifiers make it trivial to trace back to your setup.

0 Reply

Write a Reply

Markdown supported