Skip to main content
Poll the Room puts live polls on a presenter’s own slides. The presenter builds a deck, the audience joins on their phones with a six-digit code and never signs up, and the results show on the big screen as they come in. Everything a person can do in the editor, a script or an AI agent can do through one API. The same table of verbs is served three ways, and these pages are generated from it, so they cannot lag behind.

REST

Every verb under /api/v1, one bearer key, JSON in and out.

MCP

The same verbs as tools for Claude, Cursor, Codex and any MCP client.

For the model

llms.txt and llms-full.txt, the whole reference in one file an agent reads first.

​
What you can build

A deck from a PDF

Attach the presenter’s slides, put a poll on the right pages, look at the result.

Polls on slides

Seventeen widgets, floating on a slide or filling the screen, with the house defaults.

A room, driven from code

Start a room, walk the steps, close a poll and reveal, stop.

Results into a report

Every answer as JSON, and the same results as markdown, ready to paste.

​
How it fits together

A deck is a JSON document of steps: the join screen, slides with polls floating on them, and full-screen polls. A room is one live session of a deck. An API key belongs to a team and carries scopes, so a script can do exactly what the person who made the key allows. Three things to know before you start:
  1. The audience never signs up. An agent works on the presenter’s side only.
  2. A deck can be saved half-finished. Every read and write tells you whether it is ready to go on stage, and what stops it.
  3. Every write returns a revision. Send it back and a write lands only if nobody changed the deck since you read it, so an agent and a person can work on one deck without overwriting each other.

Quickstart

A key, one request, a deck in the editor. Five minutes.