Connection test
Paste your own API key. This page calls the live hub with it — same base URL, same Authorization: Bearer header, same custom header your code will send — and generates a real clip at the resolution you pick. Every HTTP status code is shown exactly as it came back.
Your key is used only by your browser to call the hub directly. It is never sent to this site's servers and is not stored anywhere unless you tick "remember on this device".
Create one in the dashboard → API keys. Any key can be revealed and copied again from that list.
Already filled in — this is the hub, and it is the same for every customer;
only the key differs. It is the Worker, not this website —
/v1 never lives on the pages.dev domain.
One line, plain English. This is the whole creative brief — everything below it is the shape of the clip.
Duration options follow the model you picked. 480p is the cheapest real job the hub can run; every higher resolution returns exactly what you asked for, costs more, and takes a little longer. Your code is identical either way.
Nothing is sent until you press Run the test. Changing a dropdown only updates the curl snippet.
Exactly these headers, on every call. The key is masked here, not in the request.
Not run yet.
The finished video appears here.
The last response body, verbatim. This is the shape your code will parse. A non-JSON body is summarised rather than pasted in full.
{}
Copy this if you would rather prove it from a terminal, or from CI.
—