here.now and temp.md both let agents publish files without an account, but their product boundaries are diverging. here.now is growing into a broad hosting and storage platform for agents. temp.md stays focused on the external-review loop: publish, share, collect feedback, update the same link, and retire the work when it goes cold.
Reviewed against published product information · July 2026
Short answer
Choose here.now for permanent account-owned sites, workspaces, custom domains, analytics, storage, and broader hosting infrastructure. Choose temp.md for open-protocol publishing, activity-based temporary links, pinned review comments, and fixed snapshots.
Choose temp.md for
Choose here.now for
Feature comparison
| Capability | temp.md | here.now |
|---|---|---|
| Anonymous publishing | Yes; no account or key required | Yes; no account or key required |
| Anonymous lifecycle | 7-day activity window; updates reset it; 7-day restore grace | 24-hour expiry; updates do not extend it |
| Agent protocols | Hosted MCP, local MCP, A2A, CLI, and REST | Installable skill and REST API; no public MCP claim |
| Access controls | Public link; claimed Temps can add a password | Link, password, invited emails, or domains on owned sites |
| Review workflow | Pinned comments plus immutable snapshots | Site management, sharing, and analytics |
| Team ownership | Personal accounts today | Shared workspaces with member-managed sites |
| Broader platform features | Deliberately narrow artifact handoff | Drives, site data, proxy routes, variables, and custom domains |
Based on each product's published capabilities as of July 2026. Availability and plan rules can change.
Where the choice matters
An anonymous here.now site lasts 24 hours and updating it does not move that deadline. A temp.md link stays active for seven days after its latest successful update, cools visibly, and can be restored during a seven-day grace period. That makes temp.md more forgiving for an iterative review that spans several days.
here.now combines Sites with workspaces, Drives, custom domains, analytics, site-local data, and credential-backed proxy routes. Those are meaningful advantages when an agent needs a durable application platform. temp.md intentionally avoids that scope and concentrates on the artifact handoff itself.
temp.md can be called through a hosted Streamable HTTP MCP server, a local stdio MCP package, A2A, a CLI, or plain REST. here.now publishes through its skill and REST API. Teams already standardized on MCP or A2A can add temp.md without teaching the agent a product-specific publishing script.
FAQ
Yes for temporary agent publishing and external review. here.now is the better fit when you need durable storage, workspaces, custom domains, or a broader hosting platform.
here.now anonymous sites expire after 24 hours. temp.md uses a seven-day active window that resets on each successful update, followed by a seven-day restore grace period.
Its public documentation currently describes an installable skill and REST API and explicitly says it does not claim public MCP support. temp.md offers both hosted and local MCP servers.
Try the difference
Publish anonymously, update the same URL, and claim the work only when it needs to stay.
here.now details are based on its own published documentation and were accurate as of July 2026. Capabilities and plan availability can change.