Agent skill
recommendedTeaches Claude Code, Codex, Cursor and Gemini CLI to publish and hand you the link and claim link. About the skill.
$ npx skills add beacon-host/skill -gReports, dashboards, mini apps and whole static sites go live at <slug>.beacon.host with one command, one API call or one MCP tool call, no account needed. APIs and webhooks run at <slug>.worker.beacon.host with a free account.
Paste it into Claude Code, Codex, Cursor or any agent. Agents can also read beacon.host/skill.md directly.
Four ways in, one live URL out. Pick whichever your agent can use.
Teaches Claude Code, Codex, Cursor and Gemini CLI to publish and hand you the link and claim link. About the skill.
$ npx skills add beacon-host/skill -gA remote server with a publish_site tool, for agents that can't run commands. Setup for other clients.
$ claude mcp add --transport http beacon https://beacon.host/mcpPublishes a folder or a file. The beacon CLI (macOS/Linux, Windows) also builds and deploys sites and Workers.
$ curl -fsSL https://beacon.host/publish.py | python3 - ./distOne request for a small site, three calls for big ones. See the API docs and the OpenAPI spec.
$ curl -sS https://beacon.host/v1/publish -F file=@index.htmlMachine-readable docs: /llms.txt · /skill.md · /openapi.json · /.well-known/agent-skills/index.json
Anything that can run a command or send an HTTP request can publish. Your agent does the building; beacon.host turns it into a link anyone can open.
If it runs in a browser, it works here. A few things agents make most:
One file, one link that opens as a page, with an optional password. Share an HTML file as a link.
q3-review.beacon.host
index.html, app.js and data.json as one site. Updates keep the URL, and every version is kept for rollback.
sales-dash.beacon.host
Any static build: dist/, build/, out/. Add a 200.html and deep links load your app too.
pomodoro.beacon.host
Folders and .zip files, up to 10,000 files per version and 10 GB per site, with or without an account.
launch.beacon.host
PDFs and images, served with the content type you declare so they open in the browser. File upload API.
deck.beacon.host/pitch.pdf
Server-side JavaScript on Cloudflare Workers, with a free account. Workers and GitHub or Stripe webhook receivers.
hooks.worker.beacon.host
Free either way. An account (an emailed code, no password) lifts the limits and keeps sites up. Live values as JSON: /v1/limits.
| No account | Free account | |
|---|---|---|
| How long a site lasts | 24 hours, then a claim link keeps it | No expiry |
| Publishes per hour | 5 per IP address | 60 |
| Largest file | 250 MB | 5 GB |
| Per site | 10 GB, 10,000 files | 10 GB, 10,000 files |
| Password protection | Yes | Yes |
MCP publish_site, per call | 4 MB, up to 1,000 files | 10 MB, up to 1,000 files |
| Workers (APIs) | No | Yes, 3 MB bundle |
No. Your agent writes the page; beacon.host puts it online and hands back the link. There's no editor and no templates.
Probably not. A long-lived site with a build pipeline belongs on Netlify, Vercel or Cloudflare Pages. beacon.host is for the link your agent hands you mid-conversation.
Anyone you send the link to. Search engines are told not to index sites nobody has claimed yet, and you can add a password to any site, even without an account.
Yes. Add a 200.html (TanStack Start's _shell.html works too) and every path that isn't a file gets it, so deep links load your app. Missing assets still 404.
Hosting where the agent, not a person, creates the site: it publishes over a CLI, an HTTP API or an MCP tool with no dashboard or signup step, and gets a URL back to hand to you. beacon.host is built for that, and you can still drop files here yourself.
Anything you and your agent make that needs a link to share. Websites, documents, dashboards, little tools, school projects, portfolios, photo galleries, games, presentations, love letters. If it lives in a browser, it works here.
All of them. Claude, Cursor, Codex, Gemini, OpenClaw, and anything else that can talk to the internet. Copy the prompt from this page into your agent and you're ready. Step-by-step: publish from Claude Code or Codex.
It sends the files (index.html, app.js, data.json) in one request or one MCP tool call and gets back https://<name>.beacon.host. Running it again with the same name and claim token updates the dashboard and keeps the URL; earlier versions are kept and can be rolled back.
Nope. Drop a file here or ask your agent to publish. If you want to keep the site, sign in with your email within 24 hours; otherwise it disappears.
24 hours without an account. Sign in with an emailed code (no password) and they stay up until you delete them, or until an expiry you choose.
Yes, for free, even without an account. Add a username and password when you publish, or right after dropping a file here. Visitors get the browser's login prompt. How it works.
Yes. Without an account: 5 publishes an hour per IP address, 250 MB per file, links for 24 hours. With a free account: 60 publishes an hour, 5 GB per file, 10 GB per site, no expiry, and Workers for APIs. There are no paid plans.
Not yet. Every site lives at <name>.beacon.host and every Worker at <name>.worker.beacon.host.
Yes. If your agent builds something that needs to receive form posts, call other services with a secret key, or respond to visitors, we've got that too. Just ask your agent to make a "worker" and it'll live at a your-thing.worker.beacon.host link.
We'll charge for premium features at some point. For now, it's on us.
Yes. Every new thing you publish gets its own link. If you want to update something instead of creating a new one, just tell your agent.
Your files are stored on Cloudflare R2 and served over HTTPS from beacon.host. Identical files are stored once, so republishing is quick. Workers, the backend part, run on Cloudflare's edge network, close to whoever calls them.
Nothing illegal, no viruses, no scams or phishing, no spam, and nothing that hurts kids. Pretty much anything else is fair game.