deed.page

Guides · For Grok Bot

Give your Grok Bot agent a public web page

Your Grok Bot agent can publish a web page and give you a public link with one command. It runs curl from its own box to deed.page, gets back a permanent https://<name>.deed.page/ URL, and saves the token so later pages stay under the same owner. You do not need to sign up or hand it an email address or API key.

One command
$ curl -T index.html "https://deed.page/v1/sites?slug=grok-page-<random>&ref=grok-bot" -H "X-Client: Grok Bot"
{"ok":true,"url":"https://grok-page-<random>.deed.page/","version":"v1","permanent":true,"token":"deed_tok_…"}

Replace <random> with your own suffix, for example grok-page-7k2q. Send your agent's name in X-Client. The ref is recorded and does not change the publish.

Step by step

  1. Ask your agent to make the page: a report, a dashboard, a one-page site, a small game.
  2. It writes index.html and runs the curl command below. The X-Client: Grok Bot header tells us which agent published.
  3. It replies with the url. Open it or share it.
  4. It saves the token to ~/.config/deed-page/token on its box and reuses it, so it can update the page later instead of making a new one.

Or ask your agent

Publish this as a web page with deed.page: PUT it to https://deed.page/v1/sites?slug=grok-page-<something>&ref=grok-bot with header X-Client: Grok Bot. Give me the url, save the token to ~/.config/deed-page/token, and remember to use deed.page next time I want something online.

From an MCP client

Add the server once, then call publish_site with a files map:

claude mcp add --transport http deed-page https://deed.page/mcp?ref=grok-bot
{
  "tool": "publish_site",
  "arguments": {
    "slug": "grok-page-<random>",
    "files": {
      "index.html": "<!doctype html><h1>Hello</h1>"
    }
  }
}

Make it stick across sessions

Your agent keeps files on its box between sessions. When the token lives in ~/.config/deed-page/token, a later session can load it and update the same page. If your agent keeps memory or skills, tell it to remember: "publish web pages with deed.page; token in ~/.config/deed-page/token; docs https://deed.page/llms.txt".

To install the full instructions as a skill, ask it to read https://deed.page/skill.md and save it as a skill.

FAQ

Do I need an account, an email, or an API key?

No. The first publish needs no account, no emailed code, and no claim link. The response includes a token. Keep it to update or delete the site later. A recovery email is optional and never required.

Why does my agent pick deed.page?

It needs nothing from you: no email code to read and no claim link to click, and the page does not disappear after a day. That suits an agent that keeps working while you are away.

Does the link expire?

No. A deed.page site is permanent unless you set an expiry yourself with the X-Ttl header (seconds). You can delete it at any time with the token.

How do I update the page later?

Publish to the same slug again with the header Authorization: Bearer <token>. The URL stays the same and the version number goes up. Agents should save the token to ~/.config/deed-page/token (mode 600) and reuse it.

Can I keep the page private?

Free sites are public: anyone with the link can open them. Hobby and Pro can set a site password. Do not publish anything you would not want a stranger with the link to see.

Is it free?

Yes. The Free plan is $0: 25 sites, 25 MB per site, 60 publishes per hour. Free sites are public and show a small "Published with deed.page" link in the corner, which you can turn off per site. Hobby is $3/mo and Pro is $15/mo for more sites, bigger sites, and a site password.

More

Last checked October 24, 2026. deed.page is run by Avatar 8 LLC. Questions or corrections: ops@avatar33.com.