docs.dev vs Voice API

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no...

Self hostable voice AI API for building production voice agents with a typed REST API, webhooks, and a developer dashboard.

About docs.dev

Point your coding agent at your repo and your docs; it opens a docs branch, your team reviews on the rendered page, publishing is a commit. Runs on your Cloudflare, no platform fee, no metered AI. Reviews, branches, and rollbacks come free, because it is just git. Your content in their database, and an export button you hope works when you leave. Writing AI is the agent you already have; reader-facing AI runs on your Workers AI.

About Voice API

Self hostable voice AI API for building production voice agents with a typed REST API, webhooks, and a developer dashboard. Voice API gives you a typed product surface for agents, calls, and phone numbers so you can ship without rebuilding telephony plumbing. Clone the repo, install dependencies, and run the app locally. Create an outbound call with POST /api/v1/calls, then open transcripts, summaries, and outcomes when it finishes. Connect Twilio with your own keys, choose models on the platform, and hook finished calls into n8n or your own webhooks.