Why AI Agents Need Instant Static Hosting

You're working with a coding agent. It generates a beautiful reveal.js presentation, or a dashboard with Chart.js, or an architecture diagram in Mermaid. Now what? You've got an HTML file sitting in your local filesystem. To show it to someone you have to either push it to a repo and deploy it somewhere, spin up a quick server and ngrok it, or just screenshot it and lose all the interactivity.

here.now makes that entire problem disappear. Your AI agent generates the content, calls the here.now API, and hands you back a public URL. Done. No account, no deploy pipeline, no config files. The whole thing takes seconds. If you're running agents that produce shareable output (and you should be, it's half the point), this tool is a proper time saver.

How here.now's Publishing API Works

Three API calls. That's it.

1. POST /api/v1/publish with a manifest of your files (paths, sizes, content types, SHA-256 hashes). You get back presigned upload URLs.
2. PUT each file to its presigned URL. Parallel uploads work.
3. POST /api/v1/publish/:slug/finalize to go live.

Your site is immediately available at <slug>.here.now, served from Cloudflare's edge network globally.

For agents, there's an even easier path. Install the skill:

npx skills add heredotnow/skill --skill here-now -g

Once installed, a Claude Code or codex or cursor session can call it natively. The agent generates HTML, invokes the skill, and replies with the live URL. No human touches a deploy button.

What You Can Host on here.now

Anything static. HTML, CSS, JS, images, PDFs, videos. The sweet spot for AI agent workflows:

Presentations that your agent builds in reveal.js. You describe what you want, the agent generates the slides, publishes them, and you share a link instead of a PowerPoint attachment.

Architecture diagrams rendered as interactive Mermaid or D2 pages. Share a live diagram instead of a screenshot that's already out of date by the time you paste it.

Dashboards and visualisations with D3 or Chart.js. Your agent pulls data, generates a dashboard, and hosts it for your team to see. No Grafana instance, no Streamlit server.

Prototypes built as small web apps. Agent scaffolds a React or vanilla JS app, deploys it, and your stakeholder clicks a link instead of cloning a repo.

Remotion videos rendered to MP4 and hosted for instant playback.

Reports as formatted HTML or hosted PDFs. Better than email attachments in every way.

here.now Free Tier Limits and Pricing

	Anonymous (no account)	Authenticated (free)
File size	250 MB	5 GB
Rate limit	5 publishes/hour	60/hour
Expiry	24 hours	Permanent
Storage	n/a	10 GB

Anonymous publishing is properly zero-friction. Your agent publishes, gets a URL, and the site lives for 24 hours. If you want to keep it, claim it with the token returned at publish time and create a free account.

No credit card. No "free trial that expires." Just free.

Advanced Features: Proxy Routes, SPA Support, and Payment Gating

Proxy routes are the feature that caught my eye. You can store API keys server-side as named variables and define a proxy manifest (.herenow/proxy.json) that lets your hosted site make authenticated upstream API calls without exposing secrets in the client. So your agent can build a dashboard that calls a protected API, and the keys never touch the browser. Rate limited at 100 requests per hour per IP.

Password protection for gating access. Useful when an agent generates something you want to share with a specific group but not the entire internet.

SPA routing for single-page apps. If your agent generates a React or Vue app, here.now can handle the client-side routing properly instead of returning 404s for deep links.

Stablecoin payment gating via Tempo (the payments blockchain from Stripe and Paradigm). You can require visitors to pay before viewing content. This is an early signal of what "agent monetisation" might look like: an agent creates content, hosts it, and charges for access, all without human intervention. Wild, and probably premature, but interesting to see it built into the platform already.

When to Use here.now (and When Not To)

Use it for: anything an agent generates that needs to be shared via URL. Presentations, diagrams, prototypes, reports, visualisations, one-off tools, demos.

Don't use it for: server-side applications (it's static only), anything that needs a database, anything that needs server-side rendering at request time, long-term production hosting (use Vercel, Netlify, or Cloudflare Pages for that).

The mental model is: here.now is for agent output, not for your product. It's the difference between hosting a document and hosting a service.

Getting Started with here.now

If you're running Claude Code (or any terminal-based AI coding agent):

npx skills add heredotnow/skill --skill here-now -g

Then just tell your agent to publish something. "Generate a reveal.js presentation about X and publish it to here.now." It'll figure out the rest.

If you want to hit the API directly, the docs are clean and the three-step flow is straightforward. No SDK needed, just HTTP calls. Pair it with an agent swarm and you've got agents that can build, deploy, and share their work without a human touching a button.