Comparison
Sentway and Claude artifacts
Claude artifacts are one of the fastest ways to go from a description to a working page, and Claude can publish an artifact and give you a link to share. Sentway is for what comes after sharing: deciding on the server who may open the page, capturing what visitors submit, keeping a record of their activity, publishing several pages as one site, and selling access when the content is paid.
What Claude artifacts are good at
- Making a page or an app in seconds from a plain description
- Iterating on it live while you are still talking to Claude
- Previewing the result without leaving the chat
- Publishing an artifact and handing out a share link
Nothing below is a criticism of that. Sentway is shaped around a different job, and the table sets out where the two differ.
The difference in one line
An artifact is a page Claude makes and can publish for you to share. A Sentway page is a published site with an access rule enforced on the server, a stored record of every response, and a way for your AI to read that record back.
The two are complementary rather than competing. Claude writes the page, Sentway serves it. Sentway has no editor and no generation of its own, so nothing about how Claude wrote the page is changed on the way through.
When you need the second half
Once a link is out in the world, new questions appear. Who is allowed to open it. Did the client actually read it. What did they type into the form, and where is that stored. Which of the three people you sent it to came back a second time. Can I charge for the part behind the introduction.
Those are the questions Sentway exists to answer. Your AI connects over MCP, publishes the page, sets the access rule, and later reads the visitor record back into the same conversation.
Access, responses and paid entry
Sentway checks the gate before any content leaves the server, so gated content is never hidden in the browser. The rule can be public, email capture, verified email, an allowlist or a password.
Forms in the page are captured natively with no endpoint to configure, and Paid Access can put a price on a page or a section, taking payment through your own connected Stripe account and granting the buyer access once the payment succeeds.
- get_site_accessFree plan
- get_submissionsFree plan
- get_paid_accessFree plan
What your AI can read back
Once the page is live, the tools below are what your AI calls to tell you what happened. The plan each one needs is read from the live tool catalogue.
- get_analyticsFree plan
- get_submissionsFree plan
- list_visitorsPro: Visitor timelines
- get_visitor_activityPro: Visitor timelines
Using both together
Build in the artifact until you like it, then ask Claude to publish it to Sentway when the page needs an access rule, stored responses or a price on it. Because Sentway accepts HTML, JSX, Markdown, SVG and Mermaid, the source usually moves across untouched.
Revisions work the same way. Claude saves a new version and publishes it, the address stays the same, and the visitor record carries on across versions.
Side by side
| Capability | Sentway | Claude artifacts |
|---|---|---|
| Where the page lives | Its own subdomain of sentway.page, served to anyone you allow | In the conversation, or as a published artifact link |
| Who wrote the page | Your AI. Sentway does not generate or restyle content | Claude, in the conversation |
| Access control | Public, email capture, verified email, allowlist or password, checked on the server | Sharing controls provided by Claude |
| Form responses | Captured natively, stored per site and read back over MCP | Handled by whatever the artifact code does with them |
| Visitor record | Visits, active time, answers and completed tasks | Not what an artifact is shaped around |
| Charging for access | Paid Access with your own connected Stripe account and entitlements | Whatever the artifact code implements |
| Multiple pages | Several pages published together as one site | One artifact at a time |
| Publishing model | Atomic snapshots, so visitors never see a half-published site | Live edits in the conversation |
Which one to reach for
Use Claude artifacts when
- You are still exploring an idea and nobody else needs to see it yet.
- A published artifact link is all the page needs, with no access rule, stored responses or price.
- You want to iterate in seconds without publishing anything.
Use Sentway when
- You are sending the page to a client, a buyer, a candidate or a list.
- Who can open it matters, and hiding content in the browser is not good enough.
- You want the answers, the visits and the finished tasks back in the conversation.
- You want to charge for access, or publish more than one page as a single site.
Questions people ask
- Does Sentway change how my page looks?
- No. Sentway serves what your AI wrote and adds only the SDK script that captures form submissions and activity. There is no template applied to your content and no restyling.
- Claude can already publish an artifact, so why publish to Sentway?
- For what happens around the page. Sentway decides on the server who may open it, stores form responses and visitor activity for your AI to read back, publishes several pages as one site, and can charge for access through your own Stripe account.
- Can I keep editing in Claude after publishing?
- Yes. Ask Claude to save the updated page and publish again. The address stays the same and the new snapshot replaces the old one for every visitor at once.
- Do I need to copy and paste the code across?
- No. With the MCP connection in place your AI publishes directly. Paste and upload also work if you would rather move it by hand.
Read next
- Connect your AI over MCP
- Publish HTML with Sentway
- How to collect responses from a Claude Artifact form
- How to sell a Claude Artifact or AI built mini tool
If the job in front of you is a page that goes out to somebody and comes back with an answer, connect your AI to Sentway and ask it to publish one.