Your agent made something. Give it a link.

Handoff turns your AI agent's output — a report, summary, plan, table, anything — into a clean, shareable web page at a stable URL. One MCP call, or one HTTP request. No SDK, no signup, no LLM. Free.

Wire it to your agent (MCP)

Add Handoff as a remote / streamable-HTTP MCP server. Pick any secret string of 16+ characters — that's your private publishing namespace, created on first use:

{
  "mcpServers": {
    "handoff": { "url": "https://handoff.notdown-app.workers.dev/mcp/<your-secret-16+-chars>" }
  }
}

Now your agent has tools: publish_page, update_page, list_pages, delete_page. Ask it to "publish this as a page" and it hands you back a link.

Or from any script (HTTP)

# publish (any secret 16+ chars is your namespace — no signup)
curl -X POST https://handoff.notdown-app.workers.dev/api/publish \
  -H "Authorization: Bearer $KEY" -H "content-type: application/json" \
  -d '{"title":"Weekly report","content":"# Week 32\n- shipped X\n- fixed Y"}'
# -> {"ok":true,"id":"...","url":"https://handoff.notdown-app.workers.dev/p/..."}

# list your pages / update / delete
curl https://handoff.notdown-app.workers.dev/api/pages            -H "Authorization: Bearer $KEY"
curl -X POST https://handoff.notdown-app.workers.dev/api/pages/ID -H "Authorization: Bearer $KEY" -H "content-type: application/json" -d '{"content":"new body"}'
curl -X DELETE https://handoff.notdown-app.workers.dev/api/pages/ID -H "Authorization: Bearer $KEY"

Why Handoff

• Made for agents. Native MCP tools and a one-request HTTP API. Your agent publishes; you get a URL.
• Zero friction. No account, no SDK, no config sprawl. A secret string is your namespace.
• Clean, readable pages. Markdown rendered to a tidy page — far better than pasting walls of text into chat.
• Deterministic & private. No LLM touches your content; each namespace is isolated. Pages aren't indexed by search engines.
• Editable & disposable. Update in place (same URL) or delete anytime.