Publish a deed.

PUT or POST your files to /v1/sites?slug=my-page-<random> (replace <random>; a tarball, one HTML file, multipart, or a JSON file map). Paths are stored exactly. The response has the live URL and, the first time, a token. Keep the token for updates. That is the whole flow. MCP clients can call publish_site on /mcp instead.

No. There is no signup, no emailed code, and no claim link. The first publish mints a Bearer token and returns it in the JSON. Email stays optional and is never required.

No. Sites are permanent unless you set X-Ttl (seconds) on the publish. After that time the slug stops serving and no longer counts toward the site cap. Delete any time with your token.

A deed is proof of ownership. Your token is the deed to your slug: whoever holds it can update or delete the site, and nobody else can.

Free: 25 sites up to 25 MB each. Hobby ($3/mo): 250 sites up to 100 MB. Pro ($15/mo): 2,500 sites up to 500 MB. A single request body is capped at 4 MB. Larger sites use POST /v1/uploads (manifest, direct blob upload, finalize) and still have to fit the plan cap.

Static files: HTML, CSS, JS, images, fonts, PDFs, JSON. No server-side code. index.html is served at the root; SPA mode serves index.html for unknown paths. Executables and credential-harvesting pages are rejected and not stored.

Only if you already attached a recovery email. That step is optional and never required to publish. We store the SHA-256 of the token and, when you attach one, the SHA-256 of the address, not the address itself. POST /v1/recovery returns the same message whether or not the address is on file, then a single-use link can mint a new token and invalidate the old one. A token with no recovery email has no self-serve recovery path. An operator who already knows the principal id can mint a replacement, which revokes every previous token. That route is not an MCP tool. The site stays up. If you still hold a leaked token, POST /v1/tokens/rotate or POST /v1/tokens/revoke. A revoked token returns 401 token_revoked, which is not 403 suspended.

Custom domains: yes, via API/MCP. POST /v1/sites/{slug}/domains with your token, or call add_domain. The response lists the DNS records to create (CNAME for a subdomain, A or ALIAS for an apex, plus any TXT verification). Check domain_status until it is active. Free includes 1, Hobby 3, Pro 20. https://{slug}.deed.page/ keeps working. https://deed.page/s/{slug}/ redirects there with 308 and does not serve the files.

Yes, for the owner. GET /v1/sites/{slug}/visits (or site_visits) returns human HTML page views, daily unique visitors, top pages, and referrer hosts. Free includes 7 days, Hobby 30, and Pro 90. The same page is at https://deed.page/analytics?slug= with the owner token. A visitor is a daily salted hash of the IP and user agent; the raw IP is not stored. GET /v1/sites/{slug}/analytics (or site_analytics) still returns the crawler rollup: views per UTC day, top paths, referrer hosts, and AI crawler families. That rollup is cookieless, does not store raw IPs or full user agents, and can under-count; the response includes an accuracy note.

On Hobby and Pro, yes. PUT /v1/sites/{slug}/access with {"password":"..."}, or the set_site_access MCP tool. Visitors get a short password page. A correct password sets a host-only, HttpOnly, Secure, SameSite=Lax cookie signed for that slug. Version permalinks and a custom domain of that site ask too. The password is stored as a scrypt hash. Free cannot set one. Pages on a protected site send noindex, and crawlers that only see the password page are not counted as views. Clearing the password is allowed on every plan.

Yes. POST /v1/webhooks with a public URL. Free can register 1, Hobby 5, Pro 20. Events: site.published, site.version_restored, site.deleted, site.taken_down, domain.active, and report.received for your own site. The HMAC secret is returned once. The Deed-Signature header is t=<unix>,v1=<hex hmac of timestamp.body>. Delivery tries 3 times (immediately, then after 0.5s and 2s) and then stops. Private and localhost targets are rejected. MCP: create_webhook, list_webhooks, delete_webhook.

Yes. Every publish stores that version's files. Free keeps the last 10 versions, Hobby 50, Pro unlimited. GET /v1/sites/{slug}/versions lists them. POST /v1/sites/{slug}/versions/vN/restore appends a new version with those files and does not re-upload. Send If-Match. A retained version stays at https://v{n}--{slug}.deed.page/ after the live site moves on. MCP: list_versions and restore_version.

Avatar 8 LLC. Contact ops@avatar33.com.