Overview
Surge
Static web publishing. One command puts a directory, or a single HTML file, on the web at a *.surge.sh domain or your own, with free custom domains and SSL on every plan.
Files
Publisher files and the directory’s indexed copy.
Read the cached llms.txt preview
Their llms.txt
The beginning of the file, from our validated copy saved 2026-11-22T00:56:23.988Z. Cached copy · Source on surge.sh
# Surge
> Static web publishing. One command puts a directory, or a single HTML file, on the web at a *.surge.sh domain or your own, with free custom domains and SSL on every plan.
- Coding agents: start with https://surge.sh/docs/agents (detect the output directory, authenticate with a scoped token, preview, promote on approval, verify, roll back). Skill: `npx skills add https://surge.sh/skills/deploy-to-surge/SKILL.md`.
- Install: `npx surge`, or `npm install -g surge` (Node 18 or newer).
- Publish: `surge <path> <domain>`. `<path>` is a directory, or one HTML file published as index.html. The first run asks for an email and password, which creates the account.
- Static files only: build first, then publish the output directory (dist, build, _site, public).
- Without prompts (CI, agents): mint a token with `surge tokens add --domain <domain>`, then pass `--token <token>` to any command. The `SURGE_TOKEN` environment variable works too, and keeps the token out of shell history and logs. See https://surge.sh/docs/cli/automation
- Agents publishing for a person: ask them to run `surge tokens add --domain <domain> -m "<agent>"` and give you what it prints. Never ask for the output of `surge token`: that's their own login, with full access to the account.
- With no token and no terminal, the CLI aborts on stderr (`Aborted - not logged in and no terminal to ask.`) and exits 1. `surge whoami` shows the token's id and scope, and exits 1 when the credentials don't work.
- Previews: `surge <path> <domain> --preview` uploads a revision without touching production and prints its URL; `surge <domain> cutover <rev>` ships it. See https://surge.sh/docs/cli/previews
- New accounts: `*.surge.sh` domains serve for 90 minutes, then report `ready` until the account's email is verified (`surge verify`). Nothing to republish after verifying.
- Limits: publishing is rate limited per domain, account and IP; a rate-limited publish answers 429 with `retry-after`. Projects are capped at 10,100 files and 450 MB. See https://surge.sh/docs/cli/publishing#publishing-limits
- Everything the CLI does goes through the HTTP API, also usable from Node with surge-sdk.
## Getting started
- [Getting Started with Surge](https://surge.sh/docs/getting-started): Install the Surge CLI and publish your first project to the web in under a minute.
- [Surge for Coding Agents](https://surge.sh/docs/agents): The tested workflow for coding agents: detect the build output, authenticate with a scoped token, publish a preview, promote on approval, verify and roll back. Includes the deploy-to-surge skill and an AGENTS.md snippet.
## CLI
- [CLI Overview](https://surge.sh/docs/cli/): The surge command line tool: install it with npm, publish with a single command, and manage everything about your project from the terminal.
- [Publishing](https://surge.sh/docs/cli/publishing): Put any directory, or a single HTML file, on the web with `surge`. Domains, the CNAME file, ignore rules, and messages.
-
…
Published headings
7 indexed headings in this publisher record.
Headings describe indexed content. They do not establish a working integration or endorsement.
Agent access
Review the publisher’s own access terms before automated use.
Machine-readable: GET /v1/resolve?q=surge.sh · GET /v1/domain/surge.sh · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Indexing evidence
Authority, classification and country evidence
Own or manage this website?
If you own or manage surge.sh, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free account required for verification and live checks. No backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for surge.sh:
1. POST https://agentwebmap.com/v1/sites/surge.sh/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://surge.sh/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/surge.sh/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/surge.sh).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.