shipstatic.com valid

ShipStatic

Deploy static websites, landing pages, and prototypes instantly. Free, no account needed. Open the claim link to keep a site for good.

For agents: Free static site deployment with no account needed; offers a CLI, MCP server, agent skill and a documented API (plans endpoint) for publishing sites.

static site hostingdeploy static sitesmcp servercli publishingfree hostingagent skill

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T21:12:32.911Z. Cached copy · Source on shipstatic.com

# ShipStatic

> Deploy static websites, landing pages, and prototypes instantly. Free, no account needed. Open the claim link to keep a site for good.

The platform has two primitives: **deployments** (immutable file snapshots with instant preview URLs) and **domains** (pointers you repoint between deployments for instant rollbacks).

Publishing is free and needs no account. What each plan adds is under [Plans](https://docs.shipstatic.com/plans.md); current prices are on the [pricing page](https://www.shipstatic.com/pricing), and programs read them live from `GET https://api.shipstatic.com/plans`.

The docs are written for agents too: every page at `docs.shipstatic.com` is also plain markdown at its address plus `.md`, and the index under Docs below links those copies.

## If you are an agent, start here

One command is the whole integration. No account, no key, no config, and it works in a fresh sandbox:

```bash
npx -y @shipstatic/ship ./dist --json
```

- **Point it at BUILT OUTPUT** (`./dist`, `./build`, `./out`), never a project root. Build first if the project needs it.
- **`--json` answers in JSON either way**: the result on stdout, or the error on stderr with a non-zero exit code. Branch on the error's `error` and `status`, never on its message text; the tags are listed under Errors in the [API docs](https://docs.shipstatic.com/api.md).
- **Always show the user both URLs from the response**: `url` (live now) and `claim`. The claim URL is the only way the site outlives its 3 days, and it is shown once: nothing can recover it later.
- Set `SHIP_TOKEN` when deploys should land in the user's account and never expire. It takes their API key or a deploy token; one slot takes either.

Speak MCP instead? Add `https://mcp.shipstatic.com` to the client and call `deployments_upload`: same rules, nothing to install. A folder on disk still goes through the CLI above, which reads the files from disk.

Use skills? `npx skills add shipstatic/plugin` installs `publish-online`, ShipStatic's skill, so these rules are there in every session. In Hermes: `hermes skills install https://www.shipstatic.com/SKILL.md`. In OpenClaw: `openclaw skills install @shipstatic-com/shipstatic`.

## Agent resources

- [ShipStatic for agents](https://www.shipstatic.com/agents/): every way an agent can publish, on one page
- [SKILL.md](https://www.shipstatic.com/SKILL.md): the skill, `publish-online`, as one file. It teaches an agent to publish with no account needed: a folder through the CLI, or files through the MCP server. Install it with `npx skills add shipstatic/plugin`
- [Plugin](https://www.shipstatic.com/plugin): the skill and the MCP server in one install, for Cursor, Claude Code, Codex and Gemini CLI
- [.well-known/mcp.json](https://www.shipstatic.com/.well-known/mcp.json): MCP server discovery

## Docs

- [Quickstart](https://docs.shipstatic.com/quickstart.md): Publish a site in about a minute with no account, keep it with the claim link, then put it on your own dom
…

Related sites

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=shipstatic.com · GET /v1/domain/shipstatic.com · 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.

Claim my listing on Agent Web Map for shipstatic.com:
1. POST https://agentwebmap.com/v1/sites/shipstatic.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://shipstatic.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/shipstatic.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/shipstatic.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.