Ask your own agent
Paste this into Claude Code, Codex, Cursor or any coding agent. It reads the skill file and does everything you just watched, with its own key.
Live on Cloudish · real keys · real credits · real containers
Given the prompt below and a Cloudish key, Claude Code built the system you’re looking at: a public app that takes prompts (this page), a sandbox of its own for each prompt, where Claude Code builds the app, and a key with capped credits for every app it ships. Cloudish runs all of it, the way it would run yours.
Build a system on Cloudish that turns a prompt into a live web app, built by Claude Code in a sandbox of its own. A public app takes the prompts. A private runner app’s image runs Claude Code, locked down by a managed policy and an egress allowlist, and every prompt gets a fresh replica of it, deleted afterwards. For each prompt, mint a child key, fund it with 0.5 credits and hand it to the sandbox to deploy with. The sandbox reaches Claude through a proxy on the public app, with a token that dies with the run, never the Anthropic key. Read https://cloudish.ai/skill.md first. Deploy to cloudish.ai.
That’s about all it takes. Give it to Claude Code with a Cloudish key and you get the bones of everything drawn below: the two apps, the sandboxes, the keys and the model proxy. The rest of this page is presentation.
Sheet 00 — System plan
This page, the sandboxes Claude Code works in, and the apps it ships are three Cloudish projects, and one key pays for all of them. Here they are as they stand right now, and the six moves every prompt sets off.
Type a prompt and the system takes it: Claude writes the app, and an agent ships it to Cloudish the way yours would. It mints its own key, funds it with real credits, builds a container in the cloud and puts it on public HTTPS. Every API call is shown, and every idea behind it drawn, as it happens.
Sheet 01 / 09
Live on HTTPS
Your turn
Paste this into Claude Code, Codex, Cursor or any coding agent. It reads the skill file and does everything you just watched, with its own key.
Demo apps get recycled. Download the exact source that was deployed and ship it under your own key, so it's yours for good.
No signup, no card. A key starts with 0.1 free credits, enough for a first deploy, and you can claim it later for a dashboard.
curl -X POST https://cloudish.ai/api/v1/keysSheet 00 — System plan, continued
The demo’s key pays for this page, the sandboxes and each app’s grant. Each app’s key pays for its own build and container, out of that grant, and can’t spend more. Claude’s model time is billed to an Anthropic account, not paid in credits.
| What | Paid by | Costs |
|---|
Fig. S-3 — Flight plan
Nine steps, all against Cloudish's production API, in about a minute. The agent follows the same skill.md any coding agent reads.
Fig. S-4 — The ideas
Fig. S-5 — Launch pads
Every demo app lands on one of a dozen recycled hostnames. When a pad is reused, the agent deletes the old app's key: its container, subdomain and image go with it, and its unspent credits flow back to the parent.
Specifications — The Cloudish model
One unauthenticated POST /api/v1/keys returns a key with 0.1 free credits. No browser, no card, no email.
Mint a key with a key and it's a child in the same account. Fund it by transfer, cap it with limits, delete it to get its balance back.
One credit is one dollar. Containers bill per second at their reserved size, builds for their seconds, and a key can never overspend.
Upload a tar.gz with a Dockerfile. BuildKit builds it on Cloudish's machines and pushes it to a private registry.
Long-running, any language, with an optional persistent volume. Idle apps scale to zero and wake on the next request.
Every app gets an HTTPS subdomain the moment its image exists. Swap in a memorable label, or point your own domains at it.