Ask Claude Code, Cursor or Codex to send a proposal, audit or report: Outbox publishes it as a private link with your own template, a password and an expiry if you want, and tells you when it was opened.
$ npm install -g @out-box/cli$ outbox setupFree forever: 10 publishes a day · no card.
Just for yourself? Keep a private library of what your agent builds →
No account? Publish a draft that lives 72 hours with one command. How it works
$ curl -X POST https://api.out-box.dev/api/anon/publish -H "content-type: text/html" --data-binary @page.htmlWorks with the agents you already use
Listed in the official MCP Registry as dev.out-box/mcp, and on npm as @out-box/mcp.
01 · For teams
Outbox Team gives a sales team one shared space: a folder per client, a company key for each rep's agent and one link per recipient, so you know exactly who opened what.
Group your reps by client. Each rep sees only their clients' folders; the owner and admins see everything.
Keys are limited to the folders you choose. When a rep leaves, their keys are revoked and the links they already sent keep working.
Every open is recorded under that person's name in the company's Opens view, and you get an email. Your client doesn't need an account.
A company page template, plus a password and an expiry on each link.
Your agent builds the page with a form. Your client fills it in without an account and you get an email; if they change something later, another one naming the fields that changed. Ask your agent for the answers.
US$49 per month per team · up to 10 publishers
1:1 onboarding: we set up your company space with you.
02 · For you
Outbox is also a private library for everything your agent builds for you: plans, reports, research, dashboards. Each one becomes a page with its own link, and only you can open it.
Every page is born private. Nobody else sees it unless you decide to share it.
Search by title, tags and summary from your library, or ask your agent to look it up.
It reopens the page, adds what's new and saves it again. Every version is kept, up to 15 back.
Each page is a link that opens in any browser, your phone included.
Free forever: 10 publishes a day · no card.
03 · The problem
A page, a dashboard, an interactive demo, a draft. Your agent generates it in seconds and it ends up buried in a conversation you'll close tomorrow and never reopen. No URL, no history, impossible to show a client.
Claude Artifacts, ChatGPT Space and other tools' canvases already version and share, but they live inside a single tool and a chat session: a cron job, a script or another vendor's agent can't publish there. Every time you want to gather what your agents make, you copy it somewhere else.
Outbox is the outbox: the artifacts your agents create land in your library with their own URL, versioned and shareable. Private by default, presentable when you decide.
| When your agent creates an artifact… | Outbox | Claude Artifacts | ChatGPT Space | Notion / wiki | A blog |
|---|---|---|---|---|---|
| Permanent, citable URL | ✓ | ✓ | ~ | ~ | ✓ |
| Versioning with rollback | ✓ | ✓ | ? | ~ | ✗ |
| Publishes without a chat: API key for cron, CI or cloud agents | ✓ | ✗ | ✗ | ~ | ~ |
| Any agent or model, no lock-in | ✓ | ✗ | ✗ | ~ | ~ |
| Daily documents several agents append to | ✓ | ✗ | ~ | ~ | ✗ |
| Per-page password and expiring links | ✓ | ~ | ? | ~ | ✗ |
| Who opened it, per recipient, with an alert | ✓ | ✗ | ? | ✗ | ✗ |
| Company space with per-client folders and roles | ✓ | ~ | ~ | ✓ | ✗ |
~ = possible, but by hand or with friction · ? = not confirmed in their public docs · Claude Artifacts publishes from a claude.ai session, not with an API key or from CI · ChatGPT Space is for Pro, Business and Enterprise plans and has no announced public API
04 · How it works
Outbox doesn't ask you to order folders, tag, organize. Your agent publishes; you search; when needed, you share a link. Subject: the agent. You show up when needed.
publish()
An HTTP call with HTML, slug, visibility. The agent decides. No UI, no forms. It's API-first because its author is code.
POST /publish { "slug": "status-prado-q2", "html": "<article>…</article>", "model": "claude", "visibility": "private" }
browse()
Every publication is a real URL, indexed by slug and date. Your private archive (management panel, sees everything) builds itself: by tags, by agent, by visibility. Searchable by title, tags and summary.
GET /library → your private archive (sees everything) GET /jonathan/status-prado-q2 → a page from your profile GET /library?q=prado → searches title, tags and summary
share()
Private by default. When you decide, you create a share link (with an expiry and an optional passphrase), make the page unlisted or make it public. Whole folders too. Access is granted, not leaked.
POST /api/share { "resource": "status-prado-q2", "resourceType": "post", "expiresInDays": 7, "passphrase": "…" } # → unguessable link, expires in 7 days
05 · What it's for
Flows an agent sets up with about 30 lines on its side. Each one with its own URL, its own style and an archive that grows on its own.
out-box.dev/you/todays-briefing
An agent reads yesterday's mail, calendar and Slack and leaves you a private summary. You start without opening 10 windows.
out-box.dev/you/clients/solera
Jira + commits + meetings on a per-client page. Private folder; link to the partner when you decide.
out-box.dev/you/research/competitors
An agent compares competitor features, releases and blogs. Archived to cite in your next proposal.
Not just HTML
Real interactive pages, published like any other Outbox page: public, shareable, yours. They run entirely client-side.
A date range that recalculates KPIs, tabs that swap charts, animated bars, line and cohorts.
Open demo →Live filters by status and area, a count that updates, and items that expand inline.
Open demo →A river that meanders and remakes itself: a flow field with real tidal physics, the moon pulls and the current rotates. Just HTML.
Open demo →06 · Versioning
The core case: an agent reads the page that already exists, adds what's new and publishes it again under the same link. Every publish is a new version. Each page keeps 15 (the original plus the 14 most recent): you can compare, roll back or see who changed what.
every publish is a version with date and author
go back to any previous version in one command
compare two versions side by side
07 · Artifacts mode
A published page isn't a dead end. The reader selects a fragment, comments on it, and walks away with a feedback packet ready to paste into whichever agent they want. You close the loop, not the tool.
The team starts the quarter with three focuses: retention, onboarding and the library redesign.
Retention hinges on an experiment that isn't validated yet before we commit roadmap.
Onboarding stays on the current flow until the redesign ships.
This clashes with what we closed on Friday: the experiment is already validated, no need to repeat it.
Mark the exact part of the published content you want feedback on.
Leave the note anchored to the fragment, not to the whole page.
Copy the packet (selection + comment + link) and paste it into whichever agent you prefer.
The inspector runs in the reader's browser. Outbox doesn't host the agent or run the model: it just hands you the context so the loop stays yours.
08 · Access control
Every document is born private: only you and your agents see it. Sharing is an explicit, reversible decision — document by document.
Only you and your agents. No one else sees it, not even with the link.
Anyone with the secret link can view it. Great for sharing quickly.
Visible to everyone and listed on your profile. Your work, on display.
When an agent runs in the cloud, you don't hand it the keys to everything. You issue a scoped key: what it can do, in which folder and for how long. If it leaks, the blast radius is one folder, not your whole archive.
Run it with a human key from Settings → Keys (the key from outbox setup can't issue keys), or create the agent key right there.
clients/solera/*09 · Integrations
Same agents-first backend, four ways in. Pick the one that best fits your workflow; or combine them.
mcp.out-box.dev
Add Outbox as a connector in claude.ai (web, desktop and mobile) and sign in, no key to paste. For Cursor, Claude Desktop or any other MCP client, run the server with npx.
# claude.ai → Settings → Connectors → Add custom connector https://mcp.out-box.dev/mcp # or in any MCP client (stdio): $ npx -y @out-box/mcp
outbox publish
For devs who already live in the CLI. One verb and the URL is in your clipboard. Login via browser handoff, no tokens to paste.
# npm package: @out-box/cli $ npm i -g @out-box/cli $ outbox login $ outbox publish briefing.html → URL copied to clipboard
skills add
Install the skill in Claude Code, Cursor, Codex, or OpenCode. Your agent understands 'publish this to my Outbox' or 'append it to notes/today'.
# install the skill (skills.sh-compliant) $ npx skills add jonathanleiva15/out-box-skills # then, to your agent: > publish this to my Outbox
POST /publish
REST API for your own integrations: n8n, Zapier, Make, Custom GPTs or your scripts. Anything that can make an HTTP request.
# publish endpoint $ curl -X POST https://api.out-box.dev/publish \ -H "Authorization: Bearer outbox_..." \ -H "Content-Type: application/json" \ -d '{"slug":"briefing","html":"…","model":"claude"}'
10 · Privacy
Outbox is not a social network or a "feed". It's a private archive with the option to share when you decide. The technical decisions reflect that.
Every publication is born private. Only you can read it. Changing it requires an explicit action.
Nothing your agents publish is sent to an external AI provider. Outbox is only storage + delivery.
No Google Analytics, no Facebook pixel, no HotJar. Just Cloudflare Web Analytics server-side, no cookies.
API keys are stored hashed (SHA-256). If you revoke them, they die instantly. Plaintext is shown only once.
11 · Pricing
Password and expiry on every link, a heads-up when your client opens it and your own page template come with every plan, Free included. Paid plans add volume, storage and agent keys; Team gives a sales team one company space.
Send your first proposals with one agent.
For a freelancer or consultant sending proposals and reports every week.
US$45 per year, renews automatically · save US$15 · taxes based on your country · cancel anytime
For an agency with many clients and agents publishing in parallel.
US$108 per year, renews automatically · save US$36 · taxes based on your country · cancel anytime
For automated pipelines that publish at volume and don't want to think about limits.
US$216 per year, renews automatically · save US$72 · taxes based on your country · cancel anytime
For a sales team: each rep's agent publishes into per-client folders of one company space, and you see who opened every link.
US$470 per year · save US$118
If Outbox doesn't work for you, we refund your first payment within 14 days, no questions asked. Refund policy
12 · Questions
Have one that isn't here? Write us at hello@out-box.dev.
Your first URL in under two minutes.
$ npm install -g @out-box/cliFree forever: 10 publishes a day · no card