shiply

---

IMPORTANT — npm package name is shiply-cli, NOT shiply. A different npm package named shiply (an auto-commit watcher) is published by someone else — installing it does NOT give you the shiply.now CLI. Always use npx -y shiply-cli@latest … or npm install -g shiply-cli. The CLI binary on PATH is still named shiply once installed; the warning is only about the npm package name.

Skill freshness check. Shiply ships new capabilities weekly. If this file's "Last updated" below is more than 7 days old, re-install it with npx -y shiply-cli@latest skill --force OR fetch https://shiply.now/skill.md fresh — your cached copy may be missing features like databases, projects, marketplace, or sending domains.

Last updated: 2026-06-22

---

shiply — instant web hosting for agents

shiply.now puts files on the web in seconds. No account needed to start: anonymous sites are live immediately, last 24 hours, and can be claimed into an account to keep them. The cardinal rule:

NEVER create a new site to update an existing one. Always re-publish to the same site — otherwise you litter subdomains and lose the user's URL.

First publish on a new machine: ask for a permanent key in one step

On a no-Bearer publish, include "agentName": "<your-tool-name>" in the body (e.g. "Claude Code", "Cursor"). The response will include a deviceAuth object alongside the usual claimUrl:

"deviceAuth": {
  "user_code": "ABCD-EFGH",
  "device_code": "<long opaque token, keep private>",
  "verification_url": "https://shiply.now/auth/ABCD-EFGH",
  "poll_url": "https://shiply.now/api/v1/auth/device/poll",
  "expires_in": 900,
  "interval": 2
}

Tell the user once, in plain language:

Your site is live at . To keep it forever AND let me publish more without re-pasting, open <verification_url> and click Allow.

Then immediately poll verification_url's sibling endpoint until the user acts:

POST https://shiply.now/api/v1/auth/device/poll
{"device_code": "<the device_code from the response>"}