Not built
Playground
An in-browser place to try an agent - prompt, voice, tool call, webhook event - without deploying anything. It does not exist yet. Here is what it would need, and what already covers parts of it.
Why it is not here yet
A playground that does anything real needs an agent to talk to, and an agent belongs to an account. That leaves three options, and none of them is free:
- Ask for your API key. Technically simple and the wrong thing to ask. A key pasted into a third-party page is a key you have to rotate.
- Run a shared demo agent. Then this site is paying for every visitor's conversation and moderating what they say to it. That is a product, not a documentation page.
- Sign in. Which makes bitpull.io an application with accounts - a different thing from what this domain is for.
The version that is worth building is the third, and it belongs in the product rather than here. A demo you can talk to today already exists on bitpull.ai.
What already covers part of it
The pieces of a playground that do not need an account are built, and they are the pieces people actually reach for:
Widget generator
AvailableAssemble the embed snippet with a live preview of the widget chrome, attribute by attribute.
Webhook tester
AvailableA live inbox URL, plus a sample delivery you can fire at yourself to see the rendering.
Prompt reviewer
AvailableStatic review of a prompt against the failures that show up in real transcripts.
Voice latency test
AvailableNetwork, WebRTC and microphone measurements against the budget a spoken turn has.
What is genuinely missing
| Would be | Needs |
|---|---|
| Talk to your agent from this page | Your credential, or an account here. Both are the wrong trade. |
| Try a prompt change against real questions | A model call, and therefore a key. The dashboard's prompt test panel does this properly. |
| Fire a tool call and see the arguments | A live session. The declaration itself can be written and reviewed without one. |
| Replay a webhook event into your endpoint | Nothing, actually - the tester already sends a sample delivery. |
| Interactive API explorer | A published OpenAPI document. There is none, and generating one from guesses would be worse than the curl on the API page. |
It will be because one of those trade-offs stopped being a trade-off, and the changelog will say which. Until then this page is a plan, clearly labelled as one.