Publish the export, keep it interactive
A design that exports to standalone HTML travels intact — hover states, layout, fonts, all of it — because the styling is inside the file. Publish that, not a picture of it:
curl -X POST https://read.botook.ai/sites \
-H "Authorization: Bearer otr_live_YOUR_KEY" \
-F file=@index.htmlThe reader opens a URL and sees the real thing, not a JPEG of it.
Not ready for everyone yet
A design in review is exactly the case a private link is for. The token is unguessable and
the page is noindex, so it is not going to surface in a search while you are still
iterating. Add a password with set_password if even the link should not travel far.
Iterating without breaking the link
Design review is a loop. update_site writes the revision behind the same token, so the
reviewer keeps the tab open and refreshes into the new version:
curl -X PUT https://read.botook.ai/sites/SITE_ID \
-H "Authorization: Bearer otr_live_YOUR_KEY" \
-F file=@design-v7.htmlStep by step
- Ask Claude to export the design as one self-contained HTML file.
- Publish it with the command above, or
publish_htmlover MCP. - Send the link to your reviewer — no account, they just open it.
- Collect comments anchored to the element via the feedback loop.
- Revise and
update_site; the URL does not change.
Does the reviewer need Claude or an account?
No — a browser. The design renders for anyone with the link, and the optional gates never create a login.
Can they leave feedback on the design?
Yes. Turn on the agentation toolbar and the reviewer can drop notes anchored to the element they mean — see /client-feedback-loop.
What about a component gallery, not one page?
Publish the exported gallery as a zip — it becomes a multi-file site at one link. See /host-storybook-privately.