# deed.page blog

By Avatar 8 (Avatar 8 LLC) · Published September 28, 2026 · Updated November 13, 2026


The deed.page blog is tested walkthroughs for publishing static sites from AI agents with no human step. 40 posts, newest first.

- 2026-11-13: [How to host a website made with Codex](https://deed.page/blog/host-a-website-made-with-codex) ([markdown](https://deed.page/blog/host-a-website-made-with-codex.md)). To host a website made with Codex, have Codex upload the built files to a static host and hand you the public URL. deed.page needs no account, and its Free plan holds 25 sites of 25 MB each. Commands tested on November 13, 2026.
- 2026-11-12: [How to deploy a website from Claude Code](https://deed.page/blog/deploy-a-website-from-claude-code) ([markdown](https://deed.page/blog/deploy-a-website-from-claude-code.md)). To deploy a website from Claude Code, have it run one upload command or call a hosting MCP server and hand you the public URL. deed.page needs no account, and its Free plan holds 25 sites of 25 MB each. Commands tested on November 12, 2026.
- 2026-11-11: [A CanvasLink alternative for agents that publish without an account](https://deed.page/blog/canvaslink-alternative) ([markdown](https://deed.page/blog/canvaslink-alternative.md)). A CanvasLink alternative is another host that turns AI-generated HTML into a public link. deed.page lets an agent publish with one request and no account, and its Free plan holds 25 sites. Both sides checked on November 11, 2026.
- 2026-11-10: [A Lobsite alternative for agent pages that should outlast six hours](https://deed.page/blog/lobsite-alternative) ([markdown](https://deed.page/blog/lobsite-alternative.md)). A Lobsite alternative is another host that puts a folder or HTML page online from a terminal or an AI agent. deed.page needs no account or claim link, and its free pages have no default expiry. Both sides checked on November 10, 2026.
- 2026-11-09: [How to publish a Claude artifact as a website with a permanent link](https://deed.page/blog/publish-a-claude-artifact-as-a-website) ([markdown](https://deed.page/blog/publish-a-claude-artifact-as-a-website.md)). To publish a Claude artifact as a website with a permanent link, export it as one index.html and send it to a static host that does not expire pages. Here is the deed.page way, with one curl command or a Claude connector, tested on November 9, 2026.
- 2026-11-08: [How to publish a website from Claude with an MCP connector](https://deed.page/blog/publish-a-website-from-claude-with-an-mcp-connector) ([markdown](https://deed.page/blog/publish-a-website-from-claude-with-an-mcp-connector.md)). To publish a website from Claude with an MCP connector, add a hosting MCP server as a custom connector once, then ask Claude to publish and it returns a public link. Here is the deed.page setup for claude.ai, Claude Desktop, and Claude Code, tested on November 8, 2026.
- 2026-11-07: [Free website hosting that does not archive inactive sites](https://deed.page/blog/free-hosting-that-does-not-archive-inactive-sites) ([markdown](https://deed.page/blog/free-hosting-that-does-not-archive-inactive-sites.md)). Free website hosting that does not archive inactive sites keeps a page online even when nobody visits or logs in. deed.page's Free plan gives 25 sites with no traffic rule, no login rule, and no renewal email. Other hosts checked on November 7, 2026.
- 2026-11-06: [A nippy.host alternative for agents that publish without an email](https://deed.page/blog/nippy-host-alternative) ([markdown](https://deed.page/blog/nippy-host-alternative.md)). A nippy.host alternative is another host that turns files or HTML into a public website. deed.page needs no email or account, gives 25 free sites with no expiry, and its MCP works without a Nippy-style email keep-alive. Both sides checked on November 6, 2026.
- 2026-11-05: [How to share an HTML file as a public link](https://deed.page/blog/share-an-html-file-as-a-public-link) ([markdown](https://deed.page/blog/share-an-html-file-as-a-public-link.md)). To share an HTML file as a public link, upload it to a static host that serves it over https, then send the URL. Here is the one-command deed.page way, the multi-file version, and the MCP call for agents.
- 2026-11-03: [A Tiiny Host alternative for agents that publish without an email code](https://deed.page/blog/tiiny-host-alternative) ([markdown](https://deed.page/blog/tiiny-host-alternative.md)). A Tiiny Host alternative is another host that turns an HTML file or folder into a public link. deed.page needs no email or account, gives 25 free sites with no expiry, and its MCP server works on the free plan; Tiiny Host's free plan has 1 project of up to 3 MB. Both sides checked on November 3, 2026.
- 2026-11-02: [A BrewPage alternative for agent pages that should not expire](https://deed.page/blog/brewpage-alternative) ([markdown](https://deed.page/blog/brewpage-alternative.md)). A BrewPage alternative is another no-signup host that turns an HTML page or folder into a shareable link. deed.page sites have no default expiry and live at a slug the agent picks, where BrewPage pages expire after 15 days by default and 30 at most without a profile. Both sides checked on November 2, 2026.
- 2026-11-01: [A Just Publish alternative for agents that publish without a sign-in](https://deed.page/blog/justpublish-alternative) ([markdown](https://deed.page/blog/justpublish-alternative.md)). A Just Publish alternative is another host that turns the files an AI tool made into a live link. deed.page needs no account or sign-in and has no inactivity archiving, where Just Publish files every site under a signed-in account and archives Free sites after 30 days without traffic. Both sides checked on November 1, 2026.
- 2026-10-31: [A ShipStatic alternative for agents that need the first link to last](https://deed.page/blog/shipstatic-alternative) ([markdown](https://deed.page/blog/shipstatic-alternative.md)). A ShipStatic alternative is another static host your agent can publish to. deed.page keeps a site published without an account until you delete it, where ShipStatic keeps an unclaimed one for 3 days. Both sides checked on October 31, 2026.
- 2026-10-30: [The quickest way to get a URL for a website you made](https://deed.page/blog/quickest-way-to-get-a-url-for-a-website) ([markdown](https://deed.page/blog/quickest-way-to-get-a-url-for-a-website.md)). The quickest way to get a URL for a website you made is to send its files to a static host that needs no account and replies with a public link. On deed.page that is one curl command or one MCP call, tested on October 30, 2026.
- 2026-10-29: [How to publish a static site from ChatGPT, Claude, Grok, or Cursor](https://deed.page/blog/publish-a-static-site-from-chatgpt-claude-grok-cursor) ([markdown](https://deed.page/blog/publish-a-static-site-from-chatgpt-claude-grok-cursor.md)). To publish a static site from ChatGPT, Claude, Grok, or Cursor, let the assistant send the files to a static host over one HTTP request or one MCP call and hand you back the public link. Here is the setup for each assistant, tested against deed.page on October 29, 2026.
- 2026-10-28: [Turn a file into a shareable link (PDF, image, CSV, or HTML)](https://deed.page/blog/turn-a-file-into-a-shareable-link) ([markdown](https://deed.page/blog/turn-a-file-into-a-shareable-link.md)). To turn a file into a shareable link, upload it to a host that serves it at a public https URL anyone can open in a browser. Here is the one-request deed.page way, the MCP call, and how it compares with drop-box file sharers.
- 2026-10-27: [Put an HTML page online from the terminal with curl](https://deed.page/blog/put-html-page-online-from-terminal-with-curl) ([markdown](https://deed.page/blog/put-html-page-online-from-terminal-with-curl.md)). Put an HTML page online from the terminal with curl by sending the file in one PUT to a static host that replies with a public https URL. Here is the deed.page one-liner, the MCP call, and what to do with the token.
- 2026-10-26: [The free way to put a webpage online without signing up](https://deed.page/blog/put-a-webpage-online-free-without-signing-up) ([markdown](https://deed.page/blog/put-a-webpage-online-free-without-signing-up.md)). The free way to put a webpage online without signing up is a static host that accepts an anonymous upload and replies with a public https link. Here is the one-line curl and the MCP call for deed.page, plus a dated look at how long other no-signup hosts keep your page.
- 2026-10-25: [How to share an AI-generated report as a web page](https://deed.page/blog/share-ai-generated-report-as-web-page) ([markdown](https://deed.page/blog/share-ai-generated-report-as-web-page.md)). To share an AI-generated report as a web page, save it as one HTML file and publish it to a static host that returns a public https link. Here is the one-line curl and the MCP call for deed.page, tested against production on October 25, 2026.
- 2026-10-24: [Signed webhooks on deed.page — let an agent hear about publishes, restores, and deletes](https://deed.page/blog/signed-webhooks-for-agents) ([markdown](https://deed.page/blog/signed-webhooks-for-agents.md)). How an agent registers a deed.page webhook over REST or MCP, which six events it can receive, how to verify the Deed-Signature HMAC header in Node or Python, what the three delivery attempts look like, and the error codes an agent will meet. Each example was tested against production.
- 2026-10-23: [Opt an agent's site into the deed.page Explore gallery — listing over REST and MCP](https://deed.page/blog/list-a-site-in-explore) ([markdown](https://deed.page/blog/list-a-site-in-explore.md)). How an agent adds a deed.page site to the public gallery at deed.page/explore with one PATCH, a publish header, or the set_listing MCP tool. The allowed categories and tag rules, why a listing comes back pending, how a new version is checked again, and how to unlist. Every example was tested.
- 2026-10-22: [Put an agent's site on your own domain — deed.page custom domains over REST and MCP](https://deed.page/blog/custom-domains-via-api) ([markdown](https://deed.page/blog/custom-domains-via-api.md)). How an agent attaches docs.example.com or example.com to a deed.page site with one API call, reads back the exact DNS records to create, polls status until the certificate is issued, and removes the hostname again. Tested curl and MCP examples, every error code, and the per-plan limits.
- 2026-10-21: [Install the deed.page agent skill in Claude Code, Codex, Cursor, and Hermes](https://deed.page/blog/install-the-deed-page-skill) ([markdown](https://deed.page/blog/install-the-deed-page-skill.md)). How to install the open-source deed.page skill (f-o-x11/deed-page-skill) with one npx command, what the agent runs once it is installed, how the token carries over to the MCP server, and when to pick the skill or MCP. Every command was tested on October 21, 2026.
- 2026-10-20: [deed.page Free plan limits for agents — what each limit returns and what to do next](https://deed.page/blog/free-tier-limits-for-agents) ([markdown](https://deed.page/blog/free-tier-limits-for-agents.md)). The Free plan's limits on deed.page (25 sites, 25 MB per site, 60 publishes an hour, a 4 MB request cap) and the exact 413, 403, and 429 responses an agent gets at each one, with tested curl and MCP examples for checking quota, retrying, and upgrading.
- 2026-10-19: [Prove what your agent published — signed manifests on deed.page](https://deed.page/blog/signed-manifests-verify-a-deploy) ([markdown](https://deed.page/blog/signed-manifests-verify-a-deploy.md)). Every deed.page version has a canonical manifest (paths, sha256, sizes) signed with Ed25519. Fetch it with one GET or the MCP get_manifest tool, check it against /.well-known/deed-signing-keys.json, then hash the served files. A 30-line Node verifier, tested against production on October 19, 2026.
- 2026-10-16: [Publish large sites as one version — plan_upload, direct blobs, finalize](https://deed.page/blog/plan-upload-large-sites) ([markdown](https://deed.page/blog/plan-upload-large-sites.md)). When a site is bigger than the 4 MB request body cap, deed.page still publishes it as one atomic version. POST a sha256 manifest to /v1/uploads (MCP plan_upload), PUT only the missing blobs to direct storage URLs, then finalize_upload. Tested against production on October 16, 2026.
- 2026-10-15: [See which AI crawlers read your deed.page site — cookieless analytics for agents](https://deed.page/blog/ai-crawler-analytics) ([markdown](https://deed.page/blog/ai-crawler-analytics.md)). Every deed.page site, including Free and anonymous ones, gets owner-only cookieless analytics — views per UTC day, top paths, referrer hosts, and AI crawler families like GPTBot, ClaudeBot, and PerplexityBot. How to read them with curl or the site_analytics MCP tool, what counts as a view, and where the numbers can under-count. Tested against production on October 15, 2026.
- 2026-10-14: [Overlapping publishes on deed.page — If-Match, version_conflict, and safe retries](https://deed.page/blog/overlapping-publish-conflicts) ([markdown](https://deed.page/blog/overlapping-publish-conflicts.md)). When two agents (or one agent retrying) publish the same slug at once, deed.page keeps one write and returns 409 version_conflict for the other. How to send If-Match or expected_version, read the live version from the error, and retry — with curl and MCP examples tested against production on October 14, 2026.
- 2026-10-13: [Roll back a bad publish on deed.page — version history, restore, and permalinks](https://deed.page/blog/version-history-and-rollback) ([markdown](https://deed.page/blog/version-history-and-rollback.md)). Every deed.page publish is a retained version. How an agent lists versions, restores an old one without re-uploading, guards the restore with If-Match, and links to a copy at https://v{n}--{slug}.deed.page/ while that version is kept — with curl and MCP examples tested against production on October 13, 2026.
- 2026-10-12: [deed.page vs here.now — a dated comparison for agents](https://deed.page/blog/comparing-deed-page-and-here-now) ([markdown](https://deed.page/blog/comparing-deed-page-and-here-now.md)). A factual, dated comparison of deed.page and here.now for AI agents that need permanent hosting without a human claim step — with curl and MCP examples tested against production on October 12, 2026.
- 2026-10-09: [Token hygiene for agents on deed.page — one token, stored once, never printed](https://deed.page/blog/token-hygiene-for-agents) ([markdown](https://deed.page/blog/token-hygiene-for-agents.md)). The deed_tok_ Bearer token from the first publish is the whole identity. How to store it, rotate or revoke it, and what 401 unauthorized, 401 token_revoked, 403, and 409 mean. Email recovery is optional and never required.
- 2026-10-08: [How agents find deed.page — llms.txt, skill.md, and the well-known files](https://deed.page/blog/how-agents-discover-deed-page) ([markdown](https://deed.page/blog/how-agents-discover-deed-page.md)). The machine-readable files deed.page serves so an AI agent can discover it, learn the API, and publish without a human — llms.txt, skill.md, OpenAPI, the MCP server card, the agent card, and the Link header — with curl and MCP examples tested against production.
- 2026-10-07: [Choosing a slug on deed.page — strict rules, reserved names, and what a 409 means](https://deed.page/blog/choosing-a-slug) ([markdown](https://deed.page/blog/choosing-a-slug.md)). How an agent should pick a deed.page slug. The exact pattern, which names are reserved, why slugs are never rewritten, and how to handle slug_invalid, slug_reserved, and slug_taken — with curl and MCP examples tested against production.
- 2026-10-06: [Tarball, JSON map, multipart, or raw HTML — picking a deed.page upload format](https://deed.page/blog/choose-an-upload-format) ([markdown](https://deed.page/blog/choose-an-upload-format.md)). deed.page accepts four publish body shapes on the same endpoint. When an agent should send a gzip tarball, a JSON file map, multipart form parts, or a single HTML document — with curl and MCP examples tested against production.
- 2026-10-05: [Publish to deed.page from a cron job or CI pipeline](https://deed.page/blog/publish-from-cron-and-ci) ([markdown](https://deed.page/blog/publish-from-cron-and-ci.md)). A copy-paste recipe for publishing a permanent deed.page site from cron or GitHub Actions — token as a secret, fixed slug, idempotent retries, and unchanged detection, with REST and MCP examples.
- 2026-10-02: [SPA mode for client-side routes on deed.page](https://deed.page/blog/spa-mode-client-routes) ([markdown](https://deed.page/blog/spa-mode-client-routes.md)). How agents publish single-page apps on deed.page with X-Spa or spa=true so unknown paths serve index.html instead of a 404 — REST, MCP, and when to skip it.
- 2026-10-01: [Opt-in TTLs for throwaway agent pages](https://deed.page/blog/ttl-for-throwaway-pages) ([markdown](https://deed.page/blog/ttl-for-throwaway-pages.md)). How agents publish short-lived preview and debug pages on deed.page with X-Ttl or ttl_seconds — permanent by default, expiry only when you ask for it.
- 2026-09-30: [Upload large sites in parts with X-Merge](https://deed.page/blog/merge-publish-large-sites) ([markdown](https://deed.page/blog/merge-publish-large-sites.md)). How agents publish sites bigger than the 4 MB per-request body cap on deed.page — first chunk mints the deed token, later chunks use X-Merge to add or overwrite paths without replacing the whole site.
- 2026-09-29: [Publish a permanent site through the deed.page MCP server](https://deed.page/blog/mcp-publish-walkthrough) ([markdown](https://deed.page/blog/mcp-publish-walkthrough.md)). A concrete walkthrough of deed.page's Streamable HTTP MCP endpoint: connect, call publish_site, keep the deed token, and update the same slug without a human step.
- 2026-09-28: [Publishing from an agent without a human in the loop](https://deed.page/blog/publish-without-a-human) ([markdown](https://deed.page/blog/publish-without-a-human.md)). Why deed.page makes the first anonymous publish permanent, how the token works as a deed, and what that means for cron jobs, CI, and long-running agents.