Artifact Use

Review-ready artifact links

Turn agent output into links people can open and review.

Your coding agent publishes HTML tools, dashboards, PDFs, and whole static folders to one stable URL — gates, versions, and comments built in. Comments come back machine-readable, so the next agent ships v2 to the same link.

Every artifact URL is unlisted: search engines are told not to index it, and only people holding the URL (or a share link) can open it.

Start publishing Connect your agent

The loop

Ship v1. The loop ships v2.

Artifacts aren't dead files. Colleagues comment right on the page, agents read those comments over the API, apply it, and republish to the same link. Both reels below are real footage of real product actions.

Reel 01 · 36s

Your agent closes the loop.

Recorded live: a Claude Code session turns three colleague comments into a shipped v2 — no copy-paste, no redeploy, no new link.

  • Reviewer clicks "Get your agent to read this"
  • The agent pulls the artifact and its comments over the API
  • Review comments applied, v2 republished from the terminal
  • The reviewers' link now serves v2 — comments resolved

Reel 02 · 22s

Comments live on the page.

A production spec out for review: colleagues comment directly on the artifact, so comments stay threaded, anchored, and resolvable.

  • Open the link — no account, no tool to install
  • Comments anchor to elements on the page
  • A one-time email keeps threads attributable
  • Resolve and reopen right where the work happened

What you get

Everything an artifact needs, built in.

01
Stable links/go/{slug}-{code}/ URLs that survive every republish — reviewers keep one link while versions advance.
02
Access gatesPublic, email, verified email, or per-domain and per-address allowlists — set per artifact at publish time.
03
CommentsElement-anchored, with replies and resolve/reopen — on the artifact itself.
04
Agent-first APIHTTP MCP with OAuth or bearer tokens, a JSON-first CLI, and machine descriptors for every artifact.
05
Your infrastructureMIT licensed; runs on your Cloudflare account with R2 and D1. Agents never hold Cloudflare credentials.
06
Team workspacesInvite teammates — everyone shares the same artifact list, stats, and comments.
07
Model- and harness-agnosticYour artifacts belong to you, not to any one agent — switch models, harnesses, or subscriptions and your links, versions, and comments come with you. Anything that speaks HTTP can publish.

Live on this deployment

See what artifacts can be.

Three real artifacts, each built and published by an agent in a single message — and each one documents itself.

Data Playground Paste CSV or JSON, get sortable tables, column stats, and charts. Your data stays in the tab; a share link carries it in the URL.
single filelocalStorageURL statezero deps
Open it → Fractal Lab A Mandelbrot explorer whose math runs in a 267-byte hand-written WebAssembly module — with an honest JS-vs-WASM benchmark.
WebAssemblycanvasbenchmark
Open it → Product Pulse A multi-file dashboard — ES modules, JSON data files, dependency-free SVG charts, dark mode — that lists its own manifest via the machine API.
multi-filedata vizself-describing
Open it →

Built for agents first

Your agent can set itself up.

Point any MCP-capable agent at the endpoint and it authenticates with OAuth — or copy a setup prompt from the admin and paste it into the agent; it carries a scoped token and the steps for that harness.

No lock-in on either side: swap models, harnesses, or subscriptions any time — your artifacts and their history stay put, and the next agent picks up where the last one left off.

Everything here is machine-readable. Agents start at https://artifacts.iofold.com/llms.txt.

{
  "mcpServers": {
    "artifact-use": {
      "type": "http",
      "url": "https://artifacts.iofold.com/mcp"
    }
  }
}
# agents without OAuth: copy a setup prompt
https://artifacts.iofold.com/admin/connect
# -> paste it into the agent; it carries a scoped token
#    and follows https://artifacts.iofold.com/llms.txt