Vapi crosses 1,000,000,000 calls handled* Series B closes at $50M led by Peak XV* Valuation marks ~$500M* Amazon Ring picks Vapi over 40 rivals* 1M+ developers on platform* Sub-500ms median latency* YC W21 alum* San Francisco HQ* Vapi crosses 1,000,000,000 calls handled* Series B closes at $50M led by Peak XV* Valuation marks ~$500M* Amazon Ring picks Vapi over 40 rivals* 1M+ developers on platform* Sub-500ms median latency* YC W21 alum* San Francisco HQ*
Vapi logo
Vapi, photographed in a server rack somewhere, refusing to blink.
YesPress // Company File // 2026

Vapi.

The voice AI developer platform behind a billion calls - and the awkward silence between every one of them.

Voice AI Developer Platform San Francisco YC W21 Series B
Share this profile Twitter / X LinkedIn Facebook Instagram

Somewhere in San Francisco, a phone rings. A voice answers in 380 milliseconds. It is not a person. The caller does not notice. That uneventful exchange is Vapi's entire business model.

Pick up the phone today and there is a non-trivial chance the voice you hear is glued together by a four-year-old company you have probably never read about. Vapi has crossed a billion calls. Its agents handle scheduling for hospitals, support for fintechs, drive-thru orders, and the kind of debt-collection calls that used to be done by people with weary scripts. The product is largely invisible. That is the point.

For a company whose technology is loud by definition, Vapi has been impressively quiet about itself. So we are going to do the talking.

The Problem

Voice was supposed to be solved.

It was not. Speech-to-text got cheap. Large language models got fluent. Text-to-speech got eerie. And yet, every developer who tried to bolt these pieces together discovered the same thing: in voice, the silence is the product. A 900ms pause feels like the bot is broken. A 200ms pause feels like a person who is thinking. Between those two numbers lies an enormous amount of plumbing nobody wanted to write.

Telephony added a second layer of misery. SIP trunks. Carrier rules. Echo. Barge-in. Interruption handling. The polite fiction that any of this would Just Work if you wired up a few APIs. It did not.

In voice AI, the silence is the product. Vapi optimizes the gap between words like an audio engineer mixing a record. - YesPress, on what nobody else is bragging about
The Founders' Bet

A failed AI therapist that became a billion-call API.

Jordan Dearsley and Nikhil Gupta met at the University of Waterloo, where they shipped a YC-backed calendar app together that, charmingly enough, made money. In mid-2023, Dearsley wanted a therapist he could talk to on his daily walks. So he built one. He chained models, fought latency, and ended up with something that worked over a regular phone call.

The therapy product did not take off. Therapy is a hard business. The infrastructure under the therapy product, however, was something else entirely: a working real-time voice stack that other developers immediately wanted to borrow. Vapi pivoted into the picks-and-shovels business and never looked back. It launched publicly on Product Hunt in March 2024.

There is something almost suspicious about how clean the origin story is. A side project. A failed product. A discovered platform. It would feel apocryphal if the call counter were not at ten figures.

The therapy didn't take off. The infrastructure did. - The Vapi origin story, condensed
The Product

An API for the dial tone.

Strip Vapi to its core and it is a single, slightly outrageous proposition: give a developer one API and a credit card, and they will have a phone-answering agent on the internet in roughly the time it takes to make a cup of coffee. Underneath that promise sits a careful orchestration layer that swaps between speech-to-text engines, large language models, and text-to-speech voices on the fly, all while keeping median response under half a second.

Around it: telephony integrations, SDKs in the usual flavours, a CLI that engineers actually use, automated testing suites for voice agents (a category that barely existed two years ago), and the compliance accoutrements - SOC 2, HIPAA, PCI - that enterprises need before they will even take the meeting. Self-hosted speech models for the regulated paranoid. A/B testing for prompts and voices. Real-time transcripts and analytics.

What you can build with Vapi

The Proof

Receipts, kindly arranged.

Numbers are doing more of the talking here than press releases. As of May 2026, Vapi reports more than one million developers on the platform, north of 2.7 million voice agents created, and over a billion calls handled. Enterprise revenue, by their own telling, grew tenfold in the year leading into the Series B. Amazon's Ring picked Vapi over forty competing platforms to power voice features in its devices, which is the kind of bake-off result that tends to settle arguments. Other names on the customer list: ServiceTitan, New York Life, Intuit, Kavak.

1B+
Calls handled
1M+
Developers
2.7M
Agents created
<500ms
Median latency

The cap table tracks the same trajectory. Peak XV led the $50M Series B in May 2026, with Microsoft's M12, Kleiner Perkins, Bessemer Venture Partners, and Y Combinator all writing checks. Total raised: about $72M. Reported post-money: around $500M. Not a unicorn yet. Halfway there, with the runway and the customer logos to argue it is plausible.

YesPress // Timeline

Vapi, from dorm room to dial tone.

2020 // Origin
Dearsley and Gupta begin building together after meeting at the University of Waterloo.
2021 // W21
Y Combinator W21 batch. Earlier product, same founders.
2023 // The walk
Dearsley builds an AI voice therapist for his daily walks. The therapy app stalls; the latency stack does not.
2024-03 // Launch
Vapi launches publicly on Product Hunt as a developer platform for voice AI.
2024 // Series A
$20M raised, led by Bessemer Venture Partners.
2026-05 // Series B
$50M led by Peak XV, with M12, Kleiner Perkins, Bessemer and YC. ~$500M valuation.
2026-05 // Ten figures
Platform crosses one billion AI voice calls handled.
YesPress // Growth In Round Numbers

Where the noise is coming from.

Calls
1,000M+
Agents
2.7M
Devs
1M+
Funding
$72M
Latency
<500ms
Visualizing five different things on the same axis is, strictly speaking, illegal. Consider it directional. The point is the gap between Vapi's ambition and its plumbing - and how small that gap has become.
The Mission

Make voice as boring as the dial tone.

Ask the founders what they are doing and the answer collapses to a sentence: make it trivial for any developer to build human-level voice experiences. The technical translation: turn a stack that takes a team of six months to build into an SDK that takes a single afternoon. The cultural translation: voice should not be a category, the same way "HTTP requests" is not a category. It should be a primitive.

A category dies the moment it stops being remarkable. Vapi wants voice AI to die that way. - A rough paraphrase of the Vapi worldview

Quiet ambition, that. The fashionable thing in AI right now is to call yourself an agent company and aim at the human. Vapi is aiming at the interface. There is a difference. One replaces workers; the other replaces forms.

Why It Matters Tomorrow

The boring future is the bullish one.

If Vapi is right, in a few years a noticeable share of phone calls in the developed world will be at least partly handled by software, and most of those will be running on a handful of orchestration platforms. The interesting question is which ones. Vapi is betting that developers, not procurement teams, will pick the winner. That is the bet behind everything: the API-first packaging, the public docs, the GitHub-forward branding, the SDKs, the CLI.

It is also the bet behind hiring a hundred-and-seventy-odd people and pricing the company at half a billion dollars on $8M of run-rate revenue. The market is not paying for what Vapi is. It is paying for what voice becomes if voice becomes ambient.

Skeptics have plenty of ammunition. Voice AI is a crowded category. Twilio is large. OpenAI ships voice. The platform shifts in conversational AI happen monthly. Margins are thin until you own the model layer, which Vapi does not, at least not yet. Self-hosted speech models, advertised on the marketing site, hint that they are thinking about that. There is a long road between a billion calls and a defensible business.

Still, here we are. Somewhere in San Francisco, a phone rings. A voice answers in 380 milliseconds. The caller, slightly later than usual, notices nothing. The infrastructure underneath the silence was once a side project for a man on a walk. Now it is the dial tone of a small but rapidly enlarging slice of the internet.

That is Vapi.