acommerce

Install the Acommerce CLI + SDK from npm as acommerce.

Recommended: run the latest CLI without a global install (avoids PATH issues):

npx acommerce@latest setup --yes

The package's postinstall hook downloads Chromium (~150MB, one time) so the local browser recipes can drive provider signup pages.

Optional global install:

npm i -g acommerce
acommerce setup --yes

Need the SDK in your app code? import { createAcommerceClient } from "acommerce" once you've installed the package as a project dep. Most users never need this — the agent uses the MCP server, not the SDK. See the dashboard docs for the SDK-vs-MCP breakdown.

What acommerce setup does (step by step)

1. Local vault — Ensures a local identity exists under ~/.acommerce/ (X25519 key material used by the vault).
2. Start pairing — POST to https://acommerce.dev/api/cli/pair (or your ACOMMERCE_ORIGIN) to get a one-time authorizeUrl and pollUrl.
3. Browser — Prints the URL and opens your default browser (unless --no-browser). You sign in and authorize the CLI (same device-flow pattern as GitHub’s CLI).
4. Wait for approval — Polls every 2s, up to 10 minutes, until the server marks the pair complete and returns a token plus your email and inbox (address + id, minted on the host’s mail domain).
5. Session file — Writes ~/.acommerce/acommerce.session.json (mode 0600) with: origin, token, email, inbox, obtainedAt.
6. Post-auth onboarding (idempotent; failures are warned, not fatal):
   • API key — Merges or creates ~/.acommerce/.env with ACOMMERCE_API_KEY (generated if missing), ACOMMERCE_EMAIL, ACOMMERCE_INBOX, ACOMMERCE_ORIGIN.
   • Skill — Prompts for install scope: global (default), project (current directory), or skip. Copies the bundled skills/acommerce/SKILL.md into detected Claude / Cursor skill directories.
   • MCP — Prompts to register the acommerce mcp server in ~/.cursor/mcp.json and ~/.claude/settings.json when those config dirs exist (defaults to yes). Use --yes-mcp / --no-mcp to skip the prompt; --skill global|project|skip for non-interactive skill install.
7. Done — Prints a short “Ready” banner suggesting you say in the editor: Use acommerce to create a new stack.

For local development of the web app, point the CLI at your machine:

ACOMMERCE_ORIGIN=http://localhost:3000 npx acommerce@latest setup --no-browser

Set ACOMMERCE_PUBLIC_ORIGIN=http://localhost:3000 on the Next server so pairing URLs resolve correctly.

Inbox (for you and for coding agents)

After setup, list recent mail pulled from your session inbox (same store recipes use):

acommerce inbox list
acommerce inbox list --limit 10 --json   # structured output for agents / scripts

Requires a non-synthetic inbox on the server (MAIL_DOMAIN + ingest). Agents may run this command from the project terminal; it never prints your session token.

Payments

Acommerce does not issue virtual cards yet. If a provider's signup flow demands payment details, the recipe hands off to the user with a clear message — they complete the billing step themselves with their own card, then resume.