What is Antiphony?
The lexicon, the call-and-response model, and what the infrastructure does. Read more →
Antiphony
An AT Protocol lexicon and MIT-licensed infrastructure for audio call-and-response — audio posts, replies, portable records, and transcription behind one HTTP API. Vox Pop is one app built on it.
What’s here
Section titled “What’s here”The lexicons
dev.antiphony.* — the AT Protocol records every Antiphony app shares. The contract you build against. Browse →
Architecture
How the service is wired and where the backend swaps out. Read more →
Self-host it
Run the open core yourself — Workers and Postgres, or any backend behind the same ports. Quick start →
Build your own app
Consume the public API from your own surface — apps/reference is the worked example. Get started →
API reference
Every /api/v1/* endpoint, generated from the Zod schemas. Browse →
Where the line is
Section titled “Where the line is”Antiphony is infrastructure and a protocol, not a finished app. It gives you audio posts, replies, and transcription behind one API — and a set of dev.antiphony.* AT Protocol lexicons that define those records portably. It deliberately does not give you identity: accounts, profiles, and sign-in stay with the app that calls it, which asserts who is acting on each request. The product experience, and the higher-level features a given app layers on (telephony, hosted distribution, teams, billing), belong to whatever you build on top.
Vox Pop is one such app. Anything Antiphony stores — an audio prompt and the replies it draws — is a dev.antiphony.audio.post; how an app presents that, who it lets reply, and what it charges for are app decisions, not protocol ones.