HTML artifacts
Host Claude artifacts as a live URL
The agent made HTML. Here’s the URL. Publish a Claude-style report, dashboard, or deck to https://{suffix}.novence.ai/ with MCP publish_html or npx novence deploy report.html. Same host as a full static site. No JSX kit, no sandbox that strips scripts.
How do I host a Claude artifact?
MCP: publish_html with the HTML string (read the file first). CLI: npx novence deploy report.html. REST: POST https://api.novence.ai/v1/publish-html. Poll until live. Then attach a domain or grow it into a site.
Sample documents
Open these, then publish the same files from examples/artifacts/ in the repo.
Dashboard
Terminal 7 night watch
Interactive berth map, live clock, range-filtered TEU chart, radio log. Unconstrained HTML and JS.
Report
Checkout 5xx postmortem
Board-ready write-up: sticky contents, blast-radius POPs, error-budget chart, print stylesheet.
Document editors vs hosting
ArtifactBin and similar tools are Google Docs for agent HTML: themes, comments, incremental edits. Novence is production static hosting — custom domain, Lighthouse checks, Novence Forms, unconstrained HTML/JS. Use an editor if you want a kit. Use Novence when the deliverable is a URL that can become a site.
FAQ
Is this the same as ArtifactBin?
No. ArtifactBin is a document editor (constrained JSX, themes, comments). Novence serves your HTML as-is at https://{suffix}.novence.ai/ — custom domains, forms, checks, and a later full-site deploy on the same project. Unconstrained JS stays allowed.
One file or a whole site?
publish_html (or npx novence deploy report.html) is the on-ramp for a single document. Extra CSS/JS/images still use the upload + deploy loop on the same project_id.
Can I keep iterating on the same URL?
Yes. Pass the same project_id to publish_html (or --project on the CLI). Each call replaces /index.html and deploys again.
Next
Multi-file sites: /for-agents. Agency rebuilds: /examples.