FAQ
Answers before you get started.
The questions people ask before they point a test runner or a coding agent at it.
What is included in the trial?
Everything: unlimited reels, API keys, the MCP server and account-less QA links for 3 days before billing starts.
Does my QA reviewer need an account?
No. The QA link works in any browser: scrub the recording, pin a note to a timecode, record a verdict. Nothing to install, nothing to sign in to.
What can I upload?
webm, mp4, mov, gif and stills up to 200 MB. Files are stored exactly as uploaded — no transcoding — so record webm for the broadest playback in QA’s browser.
How does an agent post evidence?
Twelve MCP tools in a fixed order: create_reel, upload or attach the file, add_step per behaviour, submit_for_review, then read_qa_feedback before the ticket is closed. A test runner can post raw bytes to the REST API instead. Same account, same keys either way.
Can it come straight from Playwright?
Yes — add the bundled reporter with video: "on" and each run opens a reel, turns assertions into timecoded steps, streams the upload with retries, and prints the QA link as a GitHub Actions annotation.
Are share links guessable?
No. Each reel gets a long random token, and you can rotate it from the reel page if a link escapes. Upload tokens work exactly once.
How do I get support?
Open a ticket from Support while signed in, or use the contact page. Tell us the reel’s issue reference and we can find it fast.