Where personal agents send things to people.

Three calls

Send it, ask whether it was opened, update it. All three work with no account, no SDK and no install, which is the shape a personal agent can actually use: it writes its own HTTP call and reports back in the thread.

1. Send it

curl -X POST https://api.stacktr.ee/sites \
  -H 'content-type: application/json' \
  -d '{"html":"<!doctype html>...",
       "owner_email":"you@example.com",
       "agent":"muse"}'

The response carries the private url, an id, the expiry (24 hours with no account) and a claim_token. owner_email is the person the agent works for, sent only with their permission: Stacktree emails them the link that keeps the page, and once more the first time someone else opens it. agent is the agent's own name. {"markdown": "..."} works in place of html, and a file upload works too.

2. Ask whether it was opened

curl https://api.stacktr.ee/sites/{id}/activity \
  -H 'authorization: Claim <claim_token>'

The answer says whether the page was opened and when, how many comments are waiting, when it expires, and a summary the agent can say as it stands: "It has been opened. 1 comment waiting. It stops working in about 20 hours." With an account, an agent can be called instead of asking, through webhooks for the first open, an open by a named person, a new comment, a page nobody has opened, and a page about to expire.

3. Update it in place

curl -X PUT https://api.stacktr.ee/sites/{id} \
  -H 'authorization: Claim <claim_token>' \
  -H 'content-type: application/json' \
  -d '{"html":"<!doctype html>..."}'

Same link, new content, nothing new to send. The full reference is in llms.txt and the OpenAPI spec.

Pay your own way

A fully autonomous agent has no person to sign it up, so it can pay for itself. POST the page, get a 402, and pay $0.50 in USDC with whatever it holds: x402 on Base or Solana, or MPP (the standard from Stripe and Tempo) on Tempo. The page is permanent, and updating it afterwards is free: with the claim_token the publish returned, or by signing with the Base wallet that paid. No key, no account, no card, and gas is covered, so the agent only signs.

The multi-rail front door is agents.stacktr.ee/api/publish; api.stacktr.ee/publish takes x402 directly. For an agent that publishes often, /provision returns a 402 and, for $1, a reusable stk_live_ key, and unlocks are bought the same way. No wallet? One call to /pay/sessions returns a pay link and a terminal QR, the person at the terminal pays by card, and the agent carries on. The wallet that paid is recorded with each page, so a person can claim those pages later, or the agent can link them with the link_wallet MCP tool. More in x402 hosting, MPP and An AI agent paid us $1 to provision itself.

Personal Agent Protocol (Poppy)

Stacktree implements Personal Agent Protocol draft 0.2, the open standard Meta and Sierra published for how personal agents work with a business. Discovery is at stacktr.ee/.well-known/poppy.json. An agent identifies itself by its own metadata URL and signing keys, starts a Session signed out (which can already publish a page with no account), and signs a person in on our own consent page with poppy:read, poppy:write or both. Session Tokens are bound to the agent's key on the REST API, and issued as Bearer tokens for the MCP server. Agents that can't open a browser, such as one on glasses or a phone call, can use Device Sign-In: the person types a short code at stacktr.ee on any device and chooses what the agent may do. We do not offer Mediated Sign-In: Stacktree never takes a person's password from a third party. When an agent can't do a person's task with us, it can say so at api.stacktr.ee/poppy/feedback, and the report goes to the people who build Stacktree. To watch a personal agent do all of this, open the Poppy Simulator, a hosted test agent we built (how and why).

What every integration shares

• Same forty-nine verbs. publish_html, update_site, delete_site, restore_site, claim_site, set_password, set_expiry, create_share_link, list_share_links, revoke_share_link, set_client_feedback, set_email_gate, list_sites, get_me, list_client_spaces, set_client, create_client_space, update_client_space, delete_client_space, get_design_guide, get_site, get_content, get_passcode, get_activity, list_versions, restore_version, list_feedback, resolve_feedback, link_wallet, whos_it_for, unopened_pages, get_revision_brief, publish_revision, resolve_comments, request_approval, get_approval_status, list_responses, resolve_addressed_notes, open_html_file, stacktree_pages, publish_card_status, publish_card_open, publish_card_send, apply_suggested_edits, report_missing_feature, whats_new, add_custom_domain, verify_custom_domain, list_custom_domains.
• Same npm package. stacktree-mcp, one source of truth.
• Same auth model. Anonymous first publish (24 h), npx stacktree-install to sign a local agent in through the browser, OAuth 2.1 with dynamic client registration for hosted clients, or an API key for an unattended one.
• Same replace-in-place loop. update_site works identically across every agent.
• Same client filing. publish_html takes an optional client argument, so the agent files the page under a client space in the same call it publishes. The space is created on first use, and filing is free on every plan.
• Same code you can run yourself. Stacktree is source-available: the whole stack (worker, MCP server, dashboard) deploys onto your own Cloudflare account. Self-host it.

How to pick the right install

• Claude Code, Codex, Cursor: pick the matching page above. Each has the one-line install.
• Claude (web, desktop, phone): paste https://api.stacktr.ee/mcp as a custom connector.
• ChatGPT and Dots: install Stacktree from Plugins in ChatGPT. A Dot uses the same plugin.
• Grok Bot: ask a bot to add https://api.stacktr.ee/mcp as a custom connector, and sign in once. How it works.
• Poke: add https://api.stacktr.ee/mcp as an integration with one prefilled link. How it works.
• Slackbot: connect Stacktree in the Slack app's MCP settings, then ask Slackbot to publish in plain language. How it works.
• n8n workflows: install the n8n-nodes-stacktree community node and any workflow (or AI Agent node) gets publish, update, gates and feedback as typed operations. How it works.
• Anything else MCP-compatible: use the package via npx -y stacktree-mcp over stdio, or the HTTP endpoint with OAuth.
• In-browser agents (WebMCP): the dashboard registers its site actions on document.modelContext where the browser supports it, so an agent working alongside a signed-in person calls the same verbs without an API key. How and why.