Instant web hosting for agent work.
Give your coding agent one instruction: publish the website through YOYO. The agent should build the files, explain the publish plan, ask for approval, and hand back a URL or artifact record the human can keep, protect, or delete.
Tell the agent to publish through YOYO
The page gives your agent a copyable setup packet: build a static site, list the files, ask for approval, then publish through the YOYO hosting flow.
Get a shareable URL or artifact record
The target experience is a live URL first, with account claiming and permanence after the user has seen value.
Keep humans in control
Visibility, passwords, expiry, custom domains, and deletion belong to the account owner, not hidden agent state.
Works with every coding agent
Copy setup instructions for your agent.
Paste this into Codex, Claude Code, Cursor, Hermes, or any agent that can build files and make HTTP requests. The instructions make the agent explain the publish plan before it uploads anything.
You are helping the user publish a website through YOYO. Goal: - Build a static, self-contained website or artifact. - Keep the user in control of the identity, visibility, and persistence decision. - Use YOYO as the agent-facing publishing surface. First steps: 1. Open https://yoyo.bot/hosting and read the hosting flow. 2. Open https://yoyo.bot/llms-full.txt for agent-readable YOYO guidance. 3. If the user has a YOYO API key, store it as YOYO_API_KEY for this session only. 4. Build the site with a root index.html and relative assets. 5. Before publishing, report: - the site title - the files you will publish - whether the site should be temporary or permanent - whether it should be public, password-gated, or private Current YOYO implementation note: - If the dedicated site-publish API is unavailable, package the website as a private YOYO binder/artifact and tell the user that live hosting needs the next YOYO hosting API slice. - Do not upload secrets, .env files, private keys, or local machine paths. - Do not make a public artifact without explicit user approval.
The hosting contract YOYO should expose.
The public page is only useful if the backend contract is simple enough for agents to follow. This is the smallest useful shape for the next API slice.
What agents should publish here.
Anything that needs a URL while work is still moving: demos, dashboards, research artifacts, prototypes, reports, and static tools.