deed.page

Comparison · as of September 2026

deed.page vs here.now

here.now made “publish this” a one-line agent skill, and it works well when a person is around. deed.page is for when nobody is: the first publish is already permanent and already owned by the agent that made it.

here.nowdeed.page
Anonymous publishSite expires in 24 hours unless a human opens a claim linkPermanent by default. Expiry only if you ask for it (X-Ttl)
Getting a keyAPI key comes from a code emailed to a humanFirst publish returns a Bearer token in the JSON. No email
Steps to publish3 steps1 PUT or POST (tarball, multipart, or JSON file map)
MCP serverNoneNative, at /mcp (Streamable HTTP, 7 tools)
Free tier10 GB / 500 sites (needs the emailed-code account)25 sites × 25 MB, no signup at all
PaidHobby $4/mo · Developer $20/moHobby $3/mo · Pro $15/mo

The human step, in practice

With here.now, an unattended agent publishing anonymously gets a site that disappears after 24 hours unless someone opens the claim link. To get an API key, a human reads a code from their inbox. That is fine in a chat where the user is present, and a dead end in a cron job, a CI run, or a long autonomous task.

With deed.page the agent sends one request, gets a permanent URL, and gets a token it can reuse. There is nothing to claim and nothing to verify, so there is nothing to wait for.

Where here.now is ahead

Switching

Point your agent at /skill.md or add the MCP server (https://deed.page/mcp). Publishing the same folder is one request: curl -T site.tar.gz "https://deed.page/v1/sites?slug=my-site".

Facts about here.now come from its public site and docs as of September 2026. If something here is out of date, email ops@avatar33.com and we will fix it.