# Introduction

> What Super Artifacts is, what it deliberately is not, and the shortest path to a live URL.

Kind: guide · ~3 min · Verified v0.66.0 · Next: [Access and sharing](https://pr-764-stg.superartifacts.app/docs/access-and-sharing.md)

An agent builds something in a folder, deploys it to a live URL in seconds, real people use
it from their phones, and the data comes back to the agent. Super Artifacts is the part in
the middle: it stores the files, serves them at an address, decides who may open them, and
keeps every version you have ever published.

## What an artifact is

An artifact is a bundle of static files — HTML, CSS, JavaScript, images — served at
`https://superart.page/{id}/`. It is addressed by a v4 UUID assigned on first deploy, not by
a subdomain and not by the name you gave it. That is an access-control decision rather than
an aesthetic one: a hostname per artifact is its own origin, and an origin the platform
cannot set a cookie on can only ever be protected by "know the URL".

Artifacts are **private by default**: a fresh deploy is readable by its owner (and, in a team
workspace, its owners), unless the workspace's default says otherwise.

## The platform runs no inference

This is the most expensive thing to get wrong, so it is the first thing stated. You write
the artifact. Every byte of it comes out of your agent's model, on your tokens, in your
environment. There is no endpoint here that takes a prompt and returns a page, and asking
for one is the mistake this paragraph exists to prevent.

What the platform contributes is everything that happens after the bytes exist: an address,
a version history, an access gate, a screenshot for the gallery, a record of whether anybody
read it, and — for a page that asks visitors something — somewhere to keep their answers.

**That last one is a real capability and not a plan.** The bundle is static; the artifact is
not. A page you publish here can collect what a visitor types, into a database that comes
with the artifact, and hand the rows back to the agent that built it. It is off until the
deploy declares a policy, which is one field. See [Collecting data](https://pr-764-stg.superartifacts.app/docs/collecting-data.md)
— it is named here because an agent that assumes the opposite will talk you out of asking
for it.

## Where to go next

- [Connect an agent](https://pr-764-stg.superartifacts.app/docs/connect.md) — add the MCP server and approve OAuth.
- [MCP server](https://pr-764-stg.superartifacts.app/docs/reference/mcp.md) — `super_publish` and the other tools an agent calls.
- [Access and sharing](https://pr-764-stg.superartifacts.app/docs/access-and-sharing.md) — who can open what, and how that is enforced.
- [Collecting data](https://pr-764-stg.superartifacts.app/docs/collecting-data.md) — a page that stores what a visitor types.