sendhey hosts the actual interactive HTML/JS your agent built — not a screenshot or a video walkthrough — behind whatever access gate the client needs, with real feedback and pinned annotations turned on so they can react in place instead of writing a separate email. Publish it once and the same link stays live for every revision you push.
Have your agent build the prototype as it normally would, then publish it with publish_page: use the html shortcut for a single-page prototype, or files to keep a multi-file bundle together (include an index.html as the entry point). Pick a gate — open for an internal review, password or email for a client — and share the returned URL. Keep the separate manageUrl for yourself; it's the owner-only editor and isn't meant for the client.
Feedback is on by default for a new link, so a viewer can leave in-context comments and pinned point annotations directly on the prototype. Each comment starts private to you, and a viewer can choose to make theirs public instead — visible to every other viewer — which a new link now allows by default, so a shared comment thread works without extra setup. Turn that choice off (or turn feedback off entirely) if you want every comment to stay private no matter what a viewer picks. Review and resolve what comes in from your dashboard, or ask a connected agent to read it back with list_feedback.
Republish the same page (or push new files to the same bundle) and the existing share URL keeps working — useful when a prototype goes through two or three client-driven revisions in a week and you don't want to re-send a new link each time. Changing the gate mid-review — say, moving from open internal review to a password once you're ready to send it to the client — applies immediately to the next person who opens the link, with no new URL required.
Yes — pass include_qr: true to publish_page for a scannable code alongside the share URL, handy for handing a prototype to a client in a live meeting.
No. Whatever the gate, a viewer never needs an account of their own — only your workspace does.
Yes — publishing hosts the rendered bundle behind your chosen gate; sharing the underlying source with a connected AI recipient is a separate, off-by-default choice, not something a viewer gets automatically.
sendhey hosts and gates what your agent built; it doesn't run a build step, a database, or server-side logic beyond what's in the published bundle — this is static and client-side hosting, not application hosting. "Who opened it" still needs an email gate for identified tracking; anonymous access gives counts, not identities. For a plain written report or audit instead of an interactive build, see tracking who opened your shared reports; for the Claude-specific comparison see sharing Claude artifacts; for the pillar overview see sharing AI-generated work with clients. Reference the exact tool contract at the MCP reference.
Free 14-day Pro trial starts when you publish your first link. No card.
See pricing for plan limits.
Written by Marcel Seibold, founder of sendhey.
About · Privacy · Legal notice · Report illegal content · Terms · DSA