Reference implementation, in one prompt.
The Sprites archive ships with a working end-to-end example — a single Lovable build that spins up a public fly.io Sprite, drops an HTML asset in, boots a long-running service, and warm-polls the URL. Every mega-prompt in the index expands on this exact shape.
Vol. 01 · No. 01 · Live · GitHubsprite-sandbox-fun — the working reference build.
A TanStack Start app that calls api.sprites.dev/v1 from a single createServerFn, creates a public Sprite, writes into /root/www, runs a python http.server service on port 8080, and warm-polls the URL before handing it back. All four primitives from the archive, wired end-to-end.
Spin up a public micro-VM
POST /sprites with url_settings.auth: public. Idempotent create; 409 = already exists is fine. Public URL returns in the response body.
Push assets into /root/www
PUT /sprites/{name}/fs/write?path=/root/www/index.html with an octet-stream body. Parents auto-created. Never target /home/sprite — the service will fail to start.
Wake-on-request server
PUT /sprites/{name}/services/{svc} with http_port set, then POST /start. Warm-poll the public URL ~12× before returning so the first user never hits a cold-boot 502.
Run a shell command
POST /sprites/{name}/exec?cmd=bash&cmd=-lc&cmd=<script> with only Authorization set. Response stream ends with 0x03 + exit code. Do not add an Accept header — Sprites returns 406.
More showcases land here as builders ship them.
Pick any entry from the index, paste its mega-prompt into Lovable with your SPRITES_TOKEN set, and your build will join the showcase.