Introducing AnyRouter Artifacts: publish a page, get a link

Coding agents write a lot of HTML now: a weekly report, a chart, a design note, a diagram of a request flow. Most of it ends up as a file on one laptop. To show it to someone, you had to find a host, set up a deploy and decide who could see it.

Artifacts, now in beta, removes those steps. You publish a file or a small folder to AnyRouter and get a stable URL at https://anyrouter.dev/a/<id>. Publish again and you get a new numbered version at the same URL. Every artifact is private until you change it.

Install the anyr CLI and sign in. The artifact command ships in the stable CLI.

curl -fsSL https://anyrouter.dev/setup.sh | bash
anyr login

Publish a page. The CLI prints the URL.

anyr artifact publish ./page.html --title "Sales board"

The page is private, so only you can open the link. When you want to share it, make it unlisted:

anyr artifact visibility <id> unlisted

The same publish works over HTTP with any AnyRouter API key:

curl -sS https://anyrouter.dev/api/v1/artifacts \
  -H "Authorization: Bearer $ANYROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d &#x27;{"title":"Hello","files":{"index.html":{"content":"<h1>Hi</h1>"}}}&#x27;

{
  "id": "k3Vx9TqLm2Ab7Zcd",
  "version": 1,
  "url": "https://anyrouter.dev/a/k3Vx9TqLm2Ab7Zcd",
  "visibility": "private"
}

One file, or a folder with its styles, scripts and images. The entry file's extension decides how the page looks to a viewer.

In a folder, index.html opens first. Files such as .js, .css, .json and .csv are never the entry, so a page plus its app.js still opens the page.

Let an agent publish its report. An agent that can run shell commands can publish with one call and read the URL from JSON. Ask it to build the page, then run:

anyr artifact publish report.html --json

Agents that talk to the AnyRouter MCP server can call the publish_artifact tool instead. It takes text files up to 1 MB and needs a management key with the write:artifacts scope.

Share a diagram. A .mmd file becomes a rendered Mermaid diagram. Paste the link in a pull request or a chat thread.

curl -sS https://anyrouter.dev/api/v1/artifacts \
  -H "Authorization: Bearer $ANYROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"title":"Flow","files":{"flow.mmd":{"content":"graph TD\n  A[Request] --> B{Key valid?}\n  B -->|yes| C[Route]\n  B -->|no| D[401]"}}}'

Keep one URL for a page that changes. Publish a folder, then send new versions to the same id. Each version gets a number and an optional label, so people who have the link always see the latest one.

anyr artifact publish ./report
anyr artifact publish ./report --id k3Vx9TqLm2Ab7Zcd --label "fix chart"

The CLI skips dotfiles, node_modules and .git when it uploads a folder.

Each artifact has one of three visibility settings:

• Your name is hidden by default. The page header reads "by an AnyRouter user" until you turn on --show-author. Your email address is never shown.
• A private id answers 404 to anyone but you, so nobody can probe for it.
• An account can make artifacts public 24 hours after sign-up, and up to 5 per day. Every artifact page has a Report button.
• You can see daily views and visitors for your own artifacts. AnyRouter stores no IP address or user identity for these counts.
• A page can fetch the files of its own version and nothing else. Requests to another artifact or another URL are blocked.
• Deleting an artifact stops its URL working for everyone else at once.

You can change visibility or show your name from the Artifacts page in the dashboard, or with anyr artifact visibility.

The limits are:

The CLI uploads up to 50 files and 20 MB in one publish. For larger folders, use the manifest upload in the API.

The Artifacts API docs cover the folder upload, version conflicts, every error code and the MCP tools. See what other people have published at anyrouter.dev/artifact, and manage your own in Dashboard, Artifacts.