Programmable end-to-end
Everything the portal UI does, the CLI does — same API, same auth. The portal is one client; you, your CI, and your AI agents are others.
$ vantage websites create --name "Joe's Plumbing" --slug joes-plumbing
✓ Created website wb_01J7XB4MQH. Provisioning queued.
GitHub repo: github.com/Vantage-Connections-Org/client-joes-plumbing Vercel project: client-joes-plumbing Status: provisioning → active in ~90s
$ vantage domains add wb_01J7XB4MQH --domain joesplumbing.com
✓ Added joesplumbing.com (pending DNS). Set: A @ 76.76.21.21, CNAME www cname.vercel-dns.comThat’s the whole “set up a new client site” flow. Same commands work from the SDK, the REST API, or directly from Claude Code via MCP.
Programmable end-to-end
Everything the portal UI does, the CLI does — same API, same auth. The portal is one client; you, your CI, and your AI agents are others.
Multi-channel commerce, not just hosting
A Shopify store + first-party channel apps (TikTok, Meta, Pinterest, Google, Marketplace Connect) get provisioned and status-detected automatically.
Visual + textual, same graph
The Blueprint canvas in the portal and the CLI edit the same underlying website graph. Operators see; agents act.
CMS as a document, not a schema
One JSON document per site, edited by the client through their portal login. The template reads it at request time — no migrations, no headless-CMS ceremony.