Cloudflare now lets AI agents deploy Workers without creating an account first. One API call spins up a temporary account, deploys the Worker, and hands back a live URL — no email, no dashboard, no OAuth flow.
Here’s how the lifecycle works:
- Deploy — the agent hits a single endpoint and gets back a working URL plus a claim token
- 60-minute window — the temporary deployment stays live for one hour, during which the agent (or user) can verify it, redeploy changes, and iterate
- Claim or expire — a real Cloudflare user can claim the deployment into their own account using the token; unclaimed deployments disappear after the window closes
The practical use case is vibe-coding agents and LLM-driven dev tools that need to ship something runnable during a conversation. An agent building a small API or webhook handler can deploy it, test it against real traffic, and let the user decide whether to keep it — all without forcing an account-creation detour mid-flow.
The Cloudflare docs frame this as “claim deployments,” and the mechanic is straightforward: the claim token is a one-time-use credential that transfers ownership. Once claimed, the Worker behaves like any other Workers deployment — billing, custom domains, KV bindings, the full stack.
One Hacker News commenter compared it to Claude’s Artifacts but with a timeout. That’s directionally right, but the difference matters: this runs on Cloudflare’s edge network with a real URL, not in a sandboxed preview pane. The deployed Worker handles actual HTTP requests.
NOTE
Temporary deployments run on Cloudflare’s free tier limits. If your agent needs KV, Durable Objects, or other paid primitives, the user will need to claim the deployment into a paid account before those bindings work.
Available now through the Workers API. The 60-minute TTL and single-endpoint deploy make this the lowest-friction path from “agent wrote code” to “code is live on the internet.”