◈OpenTree DashboardSign in

$ date -I # 2026-07-25

The homepage publishes. No account, no key, no install.

The shortest possible demonstration of a publish primitive is a text area and a button on the front page. It is also the one most sites cannot ship, because the security headers they are proud of forbid the script that would make it work.

Manage was the first half. Create is the second.

The dashboard already let a signed-in user manage sites. What was missing was the first step: producing one without having an account at all. Until that existed, the shortest path from landing on the site to holding a working link went through a sign-up form — a strange thing to put in front of a product whose pitch is "one call".

What the box does

Paste markup, press the button, get a link. Behind it is one request to the anonymous endpoint — no key, rate-limited by address, short-lived by default:

POST https://read.botook.ai/v1/publish
content-type: application/json

{ "content": "<html>…</html>" }

→ 201 { "url": "https://read.botook.ai/s/…", "expires_at": … }

Two doors to the same tool

A person uses the box. An agent driving the browser sees the same capability registered on the document and calls it directly. Both end at the same endpoint, so there is no demonstration-only code path that could quietly stop matching the real one.

The part that was actually hard

Making the script run under our own headers. Every viewer response carries a strict Content-Security-Policy — that is the product — and a page with an inline script is exactly what such a policy exists to stop. The resolution: keep the strict policy on hosted pages, where untrusted markup lives, and allow inline script only on our own first-party shell, where the markup is ours.

Which is why the check opens a browser

An assertion that the HTML contains a publish control proves nothing about whether the control works — the policy could block it and every string-matching test would stay green. So the check drives a real browser: paste, click, wait for the link, open it, confirm the body rendered, and watch the console throughout. That is the difference between "the button is on the page" and "the button publishes".

Twenty-four hours by default. With an API key the default is seven days, and either is changeable per link, including to never.

Is the anonymous endpoint rate-limited?

Yes, by address, on a fixed window. It is the one endpoint reachable with no credential at all, so it is the one that needs a limit.

Can I gate an anonymously published page?

Not without a key — the gates are settings on a site you own, and an anonymous publish has no owner. Publish with a key if the content needs a gate.

Does the paste box work in every browser?

The box is ordinary HTML and JavaScript, so yes. The agent-callable half depends on the browser exposing the tool interface, and degrades to nothing when it does not.

Keep reading