Explore Packet Atlas
Animated SVG traffic, environment switching, route and port inspectors, and fictional failure traces—all inside one HTML document.
Open the interactive architecture →DOCUMENTS THAT TRAVEL TOGETHER
One link.
Not one file.
Put the report, the README, the code, and the supporting images in one collection. Let people read it—and let your agent help maintain it.
Browse the examples →Connect your agentindex.html + README.md + docs/guide.md + example.py + data.json + images
FEATURED / THE HTML IS THE EXPERIENCE
From a diagram to a game, without a separate backend.
Play Queue Rescue
A Canvas-based incident game with three scenarios, a change budget, recovery gates, scoring, and a generated debrief.
Play the incident game →Both use self-contained HTML, CSS, and JavaScript. The simulations run locally; they do not control real services. Understand the HTML sandbox and copy the build-and-publish prompts →
Start with the thing you want to do.
Make documentation readable
Headings, tables, highlighted code, task lists, and diagrams. Link chapters in nested folders instead of writing one endless document.
Open the Markdown playground →Publish an HTML artifact
A custom layout or portable interaction deserves its own page. Keep the README and sample data beside the HTML.
Try the Claude-to-link workflow →Keep the code with the guide
Publish source files and machine-readable examples alongside the explanation. Use the explicit publishing recipe.
See the code-first recipe →Give your agent a destination
Connect through MCP, review sign-in permissions, and ask for a document that ends with a real stored link.
Connect and make a first link →Choose the right audience
Public discovery, unlisted links, private review, or a signed handoff. Those choices have different access boundaries.
Compare sharing modes →Invite specific readers
Allow verified reviewer addresses to open a private paste. Send the ordinary URL yourself; keep unrelated documents out.
Walk through private review →Keep the revision history
Make exact edits, inspect diffs, and restore deliberately. The example includes an actual saved version comparison.
See version history in action →Bring images and source files
Use native image uploads, explain their provenance, and give readers download or embedding options where available.
Open the image and export guide →Ask for the next useful thing
Find a decision, add a chapter, improve a section, or prepare a review. Use recipes that specify scope and verification.
Open the prompt cookbook →Try this after connecting.
Create a useful guide for a fictional app. Include a rich Markdown README, a portable HTML overview, and JSON examples. Save them in ONE new unlisted Marke.st paste with history on. Use no personal or company information. Read the files back and give me the real link, file count, and visibility.
No paid advertising claim. No invented customer story. Just a concrete publishing workflow.
Useful tools. Clear boundaries.
Public is different from unlisted
Public pastes are discoverable. Unlisted pastes open for anyone with the ordinary URL but are not publicly listed. Agent publication requests may need owner approval.
Private links have paste-level scope
A signed link can open the whole private paste, including its ZIP. Selecting an opening document does not limit access to that document.
HTML hosting is not a universal app runtime
Self-contained pages fit well. Build dependencies, backend services, external APIs, and Claude-specific features need separate consideration.
Capabilities vary by plan and client
The feature inventory separates connector operations from interface features. Check current plan limits and tools. Do not assume every client exposes every operation.