Guides
Guides for what happens after your AI builds the page
Each guide starts with the problem and the honest options, including the ones that are not us, then shows how Sentway handles it.
Every guide
- How to Add Email Capture to a Claude ArtifactAdd an email gate to a standalone version of your Claude artifact. Learn the publish order, verification options, plan limits and how to find captured visitors.
- How to See Who Viewed Your Claude ArtifactLearn what Claude artifact sharing tells you, how to track a new Sentway URL, and when verified email can identify visitors. Includes setup steps and privacy limits.
- How to Share a Claude Artifact Without a Claude AccountWhen Claude artifacts require sign-in, the legacy publishing exception, and how to share a standalone AI-built page through Sentway so visitors need no Claude account.
- How to Password Protect a Claude ArtifactClaude's sharing controls do not set a password on an artifact. Publish a standalone copy on Sentway behind a site-wide password gate, then test and share safely.
- How to collect responses from a Claude Artifact formClaude can build the form UI in seconds, but a production form needs somewhere for the responses to go. Here are the practical options, and how to publish the page through Sentway so submissions are captured natively.
- How to Sell a Claude Artifact or AI-Built ToolSell access to a standalone version of your Claude-built tool: host it on Sentway, charge through your own Stripe account and publish a paywall that buyers can trust.
- How to Share an Interactive HTML Report With a ClientSend an interactive HTML report as a browser link your client can open without downloads or broken charts. Learn how to package, publish, restrict and test it.
- How to Add a Paywall to an HTML Page Using StripeA Stripe button collects money but does not protect your HTML. Learn how server-side access control works and how to sell paid access with your own Stripe.
Reference documentation
These guides are the introduction. The step by step reference for each feature lives in the docs tree.