Creator setup

What is Curatoria?

Curatoria is a small HTTP service you run so AI agents can find your design assets, pay per download, and fetch them — no marketplace middleman and no traditional checkout page. It is for creators who sell design systems, token packs, markdown guides, zip bundles, and similar downloadable work.

You keep your files where they are, publish a catalog of what is for sale and at what price, and deploy a small Node service that handles payment and delivery. Agents pay in USDC on Base before any file is served. curatoria-starter is the template you fork to build your own instance.

Start here

Paste this into Cursor or another agentic coding app. It uses the hosted creator setup skill as the backing workflow, but starts with decisions instead of a long checklist.

I want to set up Curatoria from the public starter repo:
https://github.com/margaretsommers/curatoria-starter

Use the Curatoria creator setup workflow at:
https://curatoria.dev/.well-known/agent-skills/creator-setup/SKILL.md

Guide me step by step. Start by asking whether I want you to run commands or explain them, then walk me through clone/install, payout wallet, local .env, local dev, smoke/bug-bash, publishing my first product, and only then deploy/mainnet. Do not ask for private keys or seed phrases. Keep docs links secondary unless I need detail.

The chapters below cover the same ground if you prefer to read before you run anything.

Setup chapters

Full chapters live in the starter repo under docs/creator/. Start at the top and follow in order.

Start here — Understand what is available today.
Accounts and env — Accounts, env vars, deployment order, and common setup failures.
Happy path — Short ordered checklist from clone to mainnet.
Before you start — x402, catalogs, and how agents pay for files.
Wallet basics — Set a public Base-compatible payout address.
Connect your storage — Use local files, direct URLs, Google Drive, or supported Dropbox paths.
Products and prices — Add Markdown products and zip bundles.
Markdown vs bundle — Choose the right product format.
Test on testnet — Run bug-bash, unpaid 402 checks, and optional paid proof.
Go live — Switch to Base mainnet only after testnet is green.
Bazaar listing — Built-in 402 metadata plus manual catalog sharing.
Troubleshooting — Common startup, catalog, 402, payment, and delivery problems.
Advanced self-hosting — Railway, Fly, Render, VMs, DNS, and production checks.
Agent setup skill — Agent skill to walk setup interactively in Cursor.