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 — with access gates, versioning, and comments built in.
# your agent, at the end of a task > artifact_publish { title: "Claims audit console", dir: "dist/" } published 12 files · v3 · gate: email https://artifacts.iofold.com/go/claims-audit-console-4fk2a9/ # teammates open it and comment on it; # the next agent reads the feedback
Agents publish
Over MCP, CLI, or plain HTTP — single HTML files or complete folders with images, data, and PDFs. Versions are immutable and promoted atomically.
People review
One stable link behind an email, verified-email, or allowlist gate. Reviewers comment directly on the artifact — no extra tooling.
Work loops back
Views and feedback are readable through the same API, so the next agent iteration starts where the review ended.
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.
Built for agents first
Your agent can set itself up.
Point any MCP-capable agent at the endpoint and it authenticates with OAuth — or it requests a token and asks you to approve a one-time code, with no browser on its side.
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"
}
}
}# tokenless agents: device-style connect POST https://artifacts.iofold.com/api/v1/connect/start # -> human approves the code at https://artifacts.iofold.com/connect POST https://artifacts.iofold.com/api/v1/connect/poll # -> bearer token + ready-to-run setup prompt