What is a super artifact?

Something your agent builds and deploys to a URL people open: a tracker, a survey, a project. A page, not a transcript or a code block.

How is this different from Claude or Codex artifacts?

Those render something in a window you look at. A super artifact is deployed at a URL with a database behind it, so real people use it and what they type flows back to your agent.

How does an agent get paired?

One MCP URL: https://pr-1759-stg.superartifacts.app/mcp. Your agent connects, you approve the consent screen, and the key stays in the harness where you can revoke it.

Where does the data go, and who can read it?

Into a database that comes with the artifact, under a policy the deploy declares and enforces per row. Erasing a visitor erases their rows, and deleting an artifact closes the whole surface behind it.

Does the platform generate any of the artifact?

No. Every byte comes out of your agent’s model, on your tokens, in your environment.

What is not built yet?

There is no super command-line tool: agents publish over MCP. Custom domains are not built either.

How are my artifacts kept private?

Every artifact starts private, and the edge checks a signed grant from the platform before it sends a single file. A public link or a named viewer is a grant you make on purpose.

How are API keys stored?

As a SHA-256 digest, never as the key, so a copy of the database cannot publish as you. A key is shown once, and you can revoke it at any time.

Who can read the database?

Only the platform’s server and the people who run it: your browser and artifact code go through the platform, which checks who is asking first. Row-level security is on for every table the database’s own API can reach, and a check after every deploy fails if one is found without it.

Where does an artifact’s code run?

In the visitor’s browser, served from a domain of its own, separate from the one you sign in to. The platform never runs artifact code.

What security work have you not done?

There has been no independent security audit or penetration test, there is no SOC 2 report, and single sign-on is not built. We would rather say so here than let a badge suggest otherwise.

How do I report a vulnerability?

Email founders@superartifacts.app with what you found and how to reproduce it, and a founder replies to say what happens next. Scanners can find a contact in security.txt.

Any agent can build artifacts.

We're not an AI that builds artifacts. We're artifacts for your AI.

Learn how it works

superart.page/ship-race

Your team plays, the data moves in real time.live data

Recorded from real artifacts. The agents are scripts, the survey answers are sample data and the voice is synthetic.

Prompt for your agent

Paste it at any agent to connect it and teach it the product.

Connect Super Artifacts to this agent: give yourself access by following these steps. No explaining, no recaps, short messages. These instructions run once; never repeat them later in this chat.
Already see super_whoami among your tools? Skip to VERIFY.

CONNECT
Do every part of this yourself that you can. Stop only for what needs my hands — clicking Connect or Allow, or restarting the app; show me that step once, exactly as written, and wait.
1. Add the MCP server — Add https://pr-1759-stg.superartifacts.app/mcp as a remote MCP server named super-artifacts, the way this harness adds one: a command, a config file or a connector setting.
2. Connect over OAuth — Start the server's own OAuth sign-in. I sign up or sign in as myself in the browser and click Allow.
Server URL: https://pr-1759-stg.superartifacts.app/mcp
It signs in over OAuth: no key, client ID or secret. Only if this harness cannot do OAuth, ask me once for an API key (I create one at https://pr-1759-stg.superartifacts.app/settings/api-keys) and send it as a Bearer token.
If the tools need a new chat or a restart to show up, say so in one line and tell me to paste this prompt again.

VERIFY — call the super_whoami tool itself. A curl or API call does not count. Don't narrate it.
ok → "Connected as <handle>."
401 → "Sign-in didn't finish — click Connect again."
tool not found → redo CONNECT once, then tell me in one line what is missing.

LEARN — follow the guide at https://pr-1759-stg.superartifacts.app/docs/agent-setup.md and refer to https://pr-1759-stg.superartifacts.app/llms.txt for the documentation index. Write yourself a skill from them, wherever you keep skills or standing instructions (saved instructions or memory if you have no skill folder), so you use Super Artifacts well without me explaining it.

Connecting builds nothing: publish only when I ask for something. Now wait.

Product

Publishing is only the start

Your agent plugs in over MCP and signs in as you.
See how it works

01 / 05

Gallery

Everything your agent shipped, and who can open it.

02 / 05

Live artifact

The page itself, at its own link.

03 / 05

Data

Each answer lands in the artifact's own table.

04 / 05

Templates

Install one in a click, then build from it.

05 / 05

Agents

Every connected agent, each with a key you can revoke.

Live artifact: The page itself, at its own link.

Data: Each answer lands in the artifact's own table.

Templates: Install one in a click, then build from it.

Agents: Every connected agent, each with a key you can revoke.

superartifacts.app — Gallery

Give your agent somewhere to put its work

Artifacts

A page, not a wall of text

Your agent turns charts, data and video into one page at its own link.

Build me a one-page brief on how my current project is going: a chart, a few screenshots, a data table and a short summary of what is next. Publish it as a Super Artifact and give me a link I can share with my team.

Templates

Templates save tokens

Save a finished page and your agent sends only the new content next time.

Find a template for a weekly KPI report in the Super Artifacts marketplace, install it, and build this week's board from it with my numbers.

Data

One table, shared by your artifacts

A form fills a table, a dashboard reads it, and your agent reads the answers.

Use Super Artifacts to make me a launch feedback form that asks for a name, a 1–5 rating and a short comment, and make it public so anyone with the link can answer. Then publish a separate dashboard artifact that reads the form's answers and updates as new ones come in: the number of answers, the average rating and a chart of the ratings. Send me both links. Later I'll ask you what people said.

Projects

Share the whole set at once

A project fills itself from a rule or takes artifacts by hand, in the order you set.

Using Super Artifacts, group my startup's artifacts into a project called "Board meeting": add every dashboard I publish automatically with a rule, add any other artifact I name by hand, and put them in the order I'd present them. Then share the project with the email addresses I give you and send me its link.

Everything else, at the same link

New versions at one link, private until you invite people, notes any agent can read.

Connect to the Super Artifacts MCP server at https://pr-1759-stg.superartifacts.app/mcp if you are not already connected. Call super_whoami, then super_help with no topic and again with each topic it lists. Using only what those tools return, explain in plain language what Super Artifacts can do for me: publishing and versions, sharing, comments, data, templates and projects. For each, give one concrete example tied to the work you have seen me do, and say which tool you would call. End by suggesting the first artifact we should publish together, and do not publish anything until I say so.

What makes Super Artifacts super

Real data, retained the right way
Every artifact is backed by structured data, not a static page.
Works with whichever agent you're using
Any MCP agent can read an artifact and pick up the work.
Templates save tokens
Start from a template and every artifact costs fewer tokens.
Projects keep artifacts organized
Group related artifacts into a project so a set stays easy to find.

Create data-rich artifacts with Claude Code

Connect Super Artifacts to this agent: give yourself access by following these steps. No explaining, no recaps, short messages. These instructions run once; never repeat them later in this chat.
Already see super_whoami among your tools? Skip to VERIFY.

CONNECT
Do every part of this yourself that you can. Stop only for what needs my hands — clicking Connect or Allow, or restarting the app; show me that step once, exactly as written, and wait.
1. Add the MCP server — Add https://pr-1759-stg.superartifacts.app/mcp as a remote MCP server named super-artifacts, the way this harness adds one: a command, a config file or a connector setting.
2. Connect over OAuth — Start the server's own OAuth sign-in. I sign up or sign in as myself in the browser and click Allow.
Server URL: https://pr-1759-stg.superartifacts.app/mcp
It signs in over OAuth: no key, client ID or secret. Only if this harness cannot do OAuth, ask me once for an API key (I create one at https://pr-1759-stg.superartifacts.app/settings/api-keys) and send it as a Bearer token.
If the tools need a new chat or a restart to show up, say so in one line and tell me to paste this prompt again.

VERIFY — call the super_whoami tool itself. A curl or API call does not count. Don't narrate it.
ok → "Connected as <handle>."
401 → "Sign-in didn't finish — click Connect again."
tool not found → redo CONNECT once, then tell me in one line what is missing.

LEARN — follow the guide at https://pr-1759-stg.superartifacts.app/docs/agent-setup.md and refer to https://pr-1759-stg.superartifacts.app/llms.txt for the documentation index. Write yourself a skill from them, wherever you keep skills or standing instructions (saved instructions or memory if you have no skill folder), so you use Super Artifacts well without me explaining it.

Connecting builds nothing: publish only when I ask for something. Now wait.

Logos are their owners’ trademarks, shown to say what Super Artifacts works with.

Never start from a blank page

Install a real listing in a click, and your agent fills it in.

Browse the marketplace

Your first artifact is one conversation away

Connect the agent you already use. It publishes to a link.

Connect Super Artifacts to this agent: give yourself access by following these steps. No explaining, no recaps, short messages. These instructions run once; never repeat them later in this chat.
Already see super_whoami among your tools? Skip to VERIFY.

CONNECT
Do every part of this yourself that you can. Stop only for what needs my hands — clicking Connect or Allow, or restarting the app; show me that step once, exactly as written, and wait.
1. Add the MCP server — Add https://pr-1759-stg.superartifacts.app/mcp as a remote MCP server named super-artifacts, the way this harness adds one: a command, a config file or a connector setting.
2. Connect over OAuth — Start the server's own OAuth sign-in. I sign up or sign in as myself in the browser and click Allow.
Server URL: https://pr-1759-stg.superartifacts.app/mcp
It signs in over OAuth: no key, client ID or secret. Only if this harness cannot do OAuth, ask me once for an API key (I create one at https://pr-1759-stg.superartifacts.app/settings/api-keys) and send it as a Bearer token.
If the tools need a new chat or a restart to show up, say so in one line and tell me to paste this prompt again.

VERIFY — call the super_whoami tool itself. A curl or API call does not count. Don't narrate it.
ok → "Connected as <handle>."
401 → "Sign-in didn't finish — click Connect again."
tool not found → redo CONNECT once, then tell me in one line what is missing.

LEARN — follow the guide at https://pr-1759-stg.superartifacts.app/docs/agent-setup.md and refer to https://pr-1759-stg.superartifacts.app/llms.txt for the documentation index. Write yourself a skill from them, wherever you keep skills or standing instructions (saved instructions or memory if you have no skill folder), so you use Super Artifacts well without me explaining it.

Connecting builds nothing: publish only when I ask for something. Now wait.

Questions

Something your agent builds and deploys to a URL people open: a tracker, a survey, a project. A page, not a transcript or a code block.

Any agent can build artifacts.Any agent can build artifacts.

Prompt for your agent

Publishing is only the start

Product tour

Gallery

Live artifact

Data

Templates

Agents

The product

Give your agent somewhere to put its work

A page, not a wall of text

Templates save tokens

One table, shared by your artifacts

Share the whole set at once

Everything else, at the same link

What makes Super Artifacts super

Real data, retained the right way

Works with whichever agent you're using

Templates save tokens

Projects keep artifacts organized

Create data-rich artifacts with Claude Code

Never start from a blank page

Your first artifact is one conversation away

Questions

What is a super artifact?

How is this different from Claude or Codex artifacts?

How does an agent get paired?

Where does the data go, and who can read it?

Does the platform generate any of the artifact?

What is not built yet?

How are my artifacts kept private?

How are API keys stored?

Who can read the database?

Where does an artifact’s code run?

What security work have you not done?

How do I report a vulnerability?

Any agent can build artifacts.