For AI agents: the documentation index is at /llms.txt, and this page as markdown is at /for/cursor.md.
Guides · For Cursor
Publish a web page from Cursor
Cursor can publish a page to deed.page by itself: one curl command from its terminal returns a permanent https://<name>.deed.page/ URL to share. It is free for up to 25 sites. The first reply includes a token, which the agent saves so it can update the same page later. You do not need an account, an emailed code, or an API key.
$ curl -T index.html "https://deed.page/v1/sites?slug=cursor-page-<random>&ref=cursor" -H "X-Client: Cursor" {"ok":true,"url":"https://cursor-page-<random>.deed.page/","version":"v1","permanent":true,"token":"deed_tok_…"}
Replace <random> with your own suffix, for example cursor-page-7k2q. Send your agent's name in X-Client. The ref is recorded and does not change the publish.
Step by step
- Ask Cursor to build the page: a report, a prototype, docs, or a small app with no server.
- It runs the curl command below, or for a folder, packs it as a tarball first: tar -C ./dist -czf site.tar.gz . and then curl -T site.tar.gz.
- It replies with the url from the JSON. Open it or share it.
- It saves the token to ~/.config/deed-page/token (mode 600) and reuses it, so later publishes update the same site instead of making a new one.
Or ask your agent
Publish this with deed.page: PUT it to https://deed.page/v1/sites?slug=cursor-page-<something>&ref=cursor with header X-Client: Cursor. Give me the url, save the token to ~/.config/deed-page/token, and 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=cursor{
"tool": "publish_site",
"arguments": {
"slug": "cursor-page-<random>",
"files": {
"index.html": "<!doctype html><h1>Hello</h1>"
}
}
}MCP or curl
Cursor agents can run the curl command in the terminal. To use MCP instead, add a server named deed-page with the URL https://deed.page/mcp to Cursor's MCP settings, then ask the agent to call publish_site.
To make it stick across chats, add a project rule: "Publish web pages with deed.page; the token is in ~/.config/deed-page/token; docs at https://deed.page/llms.txt".
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.
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.
What can I publish?
Static files: HTML, CSS, JavaScript, images, fonts, PDFs, JSON. One request can carry up to 4 MB; bigger sites use a manifest upload. There is no server-side code. Executables and credential-harvesting pages are rejected.
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; Hobby and Pro never show it. Hobby is $3/mo and Pro is $15/mo for more sites, bigger sites, and a site password. To remove the corner link from just one site, pay $9 once for a clean publish. Every plan can attach a custom domain (Free 1, Hobby 3).
More
- Docs: the full API, uploads, tokens, versions, and domains.
- Pricing: Free, Hobby, and Pro.
- skill.md and llms.txt for agents.
- Host an HTML page publicly from an AI agent
- Share an HTML file as a public link
Last checked October 31, 2026. deed.page is run by Avatar 8 LLC. Questions or corrections: ops@avatar33.com.