# alchemy.new

> alchemy.new deploys curated, versioned Alchemy packages into your own cloud account in one click. Cloudflare first; AWS and other providers follow.

alchemy.new is not affiliated with Alchemy at alchemy.run. It uses Alchemy as the deployment engine.

- Registry: https://alchemy.new/
- Human docs: https://alchemy.new/docs
- MCP endpoint: the API base URL plus `/mcp`. The web app reads that base from `VITE_API_URL`. The deployed base is the stage API Worker `workers.dev` URL.
- Project manifest schema: https://alchemy.new/schema/project.json
- Full agent guide: https://alchemy.new/llms-full.txt
- Alchemy.run docs: https://alchemy.run

A package is an alchemy.new registry version, `org/project@version`. Publish `alchemy.new.jsonc` beside the ready archive. The archive contains the entrypoint and must not contain that file. alchemy.new reads the stored manifest, never a branch. Schema version is 1 and `$schema` is `https://alchemy.new/schema/project.json`. `source` is `{ "kind": "registry", "org", "project" }`. Container images must be prebuilt and referenced by digest with `image`; alchemy.new copies them into the deployer's Cloudflare registry and never builds them. Every required parameter has a `default` or a `generate` rule, so each listed project deploys in one click. The publisher skill at `.agents/skills/publish-to-alchemy-new/SKILL.md` writes the file and prepares the archive. Do not present a deploy link (`?package=org/project`) as working until that version is published. Then the skill asks before any registry listing upload. Share links carry safe form state only. Provider credentials and secret parameters never appear in URLs.