A URL for everything your agents make
Where humans and your agents
work on dashboards together.
An agent finishes a dashboard, but the output is trapped in its session or pasted into Slack without its source and history. Cursor, Codex, Claude Code or any other agent can invoke the `publish` tool and get a URL that never changes. Gate it behind company SSO when you need to. Swap agents next quarter and the URLs, versions and comments stay exactly where they are.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – then the team opening its URL, commenting, the agent publishing v2 at the same URL, and the doc being shared with someone outside the company.
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
The agentic publishing problem
An agent publishes a financial analysis for the whole company when only three reviewers should see it. Another finishes a dashboard, but the next agent cannot find the source or the feedback. Those are publishing failures, not model failures. The artifact needs one URL with explicit access, retained versions, source and comments. In Linear's March 2026 announcement, Karri Saarinen reported that a growing share of new issues are now agent-authored, and that the volume of agent-completed work is climbing fast. Agents write reports, produce analyses, generate dashboards and output HTML documentation at a scale no human team could match. All of it needs to reach the right people at a stable URL, without a publishing step from the engineer who ran the agent.
display.dev was designed from the start to be callable. The publish action is a function, not a workflow.
- ✗Email and SlackNo stable URL, no interactivity, re-sent every time.
- ✗GitHub PagesNeeds a git push, and excludes non-engineers without Enterprise Cloud.
- ✗Confluence and NotionCan't render the HTML agents produce.
- ✗Vercel and NetlifyNeed a deployment project, and $320/month for SSO.
Three ways an agent publishes
Who can open it
A public URL for output that isn't sensitive. Nothing to sign in to.
Named email addresses only. Useful for a client or a contractor you don't want to hand company sign-in to.
Anyone signing in with a verified company domain gets in – Google Workspace, Microsoft Entra ID, or a one-time password by email. Viewers are unlimited and free.
The agent picks the level at publish time. Pass the visibility with the tool call, and change it later without changing the URL.
The right pricing model for agent-scale publishing
Per-seat pricing breaks at agent scale. If your agent publishes 50 reports a week to an audience of 200 colleagues, per-seat pricing charges you for each viewer regardless of how many reports they actually read. The 201st colleague triggers a pricing jump. display.dev charges per organization, not per viewer.
| Per-seat pricing (Cloudflare Access) | display.dev | |
|---|---|---|
| 100 viewers, 10 artifacts/week | ~$350/mo | €49/mo |
| 200 viewers, 50 artifacts/week | ~$1,050/mo | €49/mo |
| 500 viewers, 200 artifacts/week | ~$3,150/mo | €49/mo |
| Scale to zero (no views this week) | Still charging per seat | €49/mo |
Cloudflare Access is $7 per user per month, with the first 50 users free – so 100 viewers is 50 billable seats.
What agents publish
- Recurring analysis agents
- – Weekly competitive reports, market monitoring dashboards, financial summaries. The agent runs on a schedule, fetches the current version, and republishes to a known URL with
short_idandbase_version. Stakeholders bookmark the stable URL. - Scheduled-build agents
- – Nightly research summaries, weekly competitive landscape regenerations, scheduled market-map updates. The agent fetches the current version and publishes after every run with
short_idandbase_version, pinned to the same URL. The Slack notification links to an authenticated URL. - Research agents
- – Deep research outputs, synthesis reports, literature reviews. Produced programmatically and published to a team-accessible URL without a human copying the content.
- Tool-building agents
- – Cursor, Codex, and Claude Code agents that scaffold internal tools. The agent builds, then publishes the output. Non-engineers get a usable URL without touching a terminal.
Add display.dev to your agent stack
For Claude and Claude-compatible agents:
{
"mcpServers": {
"display-dev": {
"url": "https://api.display.dev/v1/mcp",
"headers": {
"Authorization": "Bearer sk_live_..."
}
}
}
}Or paste https://api.display.dev/v1/mcp into the host's "Add custom connector" field and sign in with your work email – no key to manage.
Available MCP tools:
publish(content, name, visibility?)→ create artifact, returns URLpublish(content, short_id, base_version)→ update artifact, returns same URL at a new versionfind(query)→ search published artifactsget_metadata(short_id)→ get metadata, retained versions, the heading outline, and open comment threadsdelete(short_id)→ delete a published artifactshare,rename,exportfor additional lifecycle operations
For custom agents (REST API): REST endpoints with the same verbs. API documentation ships with the CLI.
Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: 365 days audit logs
No per-API-call charges. No per-publish charges. No per-viewer charges. Flat.
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays the current version at the same URL, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Cursor, Codex, and Claude Code all work, plus any agent that creates HTML or Markdown output.
Get started free
- Get an API key and publish from an agent in minutes, no card
- Keep the URL when you upgrade
- Unlimited viewers on every plan
Common questions.
What agents does display.dev work with?
Any agent that can make an HTTP request or call an MCP tool. Natively supported via MCP: Claude, Claude Code, Claude Desktop, Cursor, and any MCP-compatible client. Via REST API: any agent in any language.
Is there a rate limit on programmatic publishing?
Programmatic publishing is built for agent-scale workloads. Enterprise limits are configurable – contact us if you expect very high volume.
Can an agent update an existing artifact?
Yes. Invoke the publish tool with the artifact's short_id and current base_version. The URL stays the same. Viewers who bookmarked it see the updated content.
What happens if a viewer isn't from your company domain?
They can't open a company-gated artifact. You can add more verified domains for contractors and partners, or invite specific people by email address.
Can agents publish to a custom domain?
Yes, on Enterprise. Custom domain is an Enterprise feature. Configure your domain in organization settings, and published artifacts appear at docs.yourco.com/[artifact-name] rather than acme.dsp.so/[artifact-name].
How are an agent's actions attributed?
Every comment and version an agent publishes is signed with the agent and the human it acted for, like codex on behalf of Carl. See how identity works.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).

