Commerce state
Represent orders, inventory, customers, payments, and related records through explicit domain operations.
Developer infrastructure · Embedded iCommerce Runtime
Commerce state.
Inside your application.
Build with a Rust commerce runtime and explicit operations for applications and agents. The runtime runs in your environment; the StateSet iCommerce product suite provides separately scoped operational offerings.
The application path
Your application or agent
Defines the task and presents its authority.
Supported SDK, CLI, or MCP interface
Invokes the configured commerce operation.
Commerce runtime and controls
Applies the supported rules and state transitions.
Persisted state and operation evidence
Records the resulting business state for inspection.
A foundation you can inspect.
Controlled changes
Use supported policies, principals, budgets, and approval controls to define what an actor may change.
Recovery and evidence
Inspect persisted state, operation results, and supported receipts when work is retried or interrupted.
Application interfaces
Choose the SDK, language binding, CLI, or MCP server appropriate to the release and your environment.
Available tools, bindings, transports, and controls depend on the release and configuration. The repository’s current catalog and release documentation are the authority for supported interfaces.
Local evaluation
Start with the core MCP profile.
Use a supported Node.js environment and a local test database. The documented core profile keeps the tool surface focused; writes are preview-only by default. Review the current setup instructions before configuring authority for changes.
Client setup and authentication →CLI + MCP
npx -y -p @stateset/cli stateset-mcp --db ./store.db --profile coreEmbedding comes with operating responsibilities.
Your deployment owns hosting, access control, backups, upgrades, monitoring, and integration behavior. Test the operations and failure paths you intend to expose. A local runtime example does not establish acceptance by a payment provider, warehouse, or trading partner.
Read the engineering documentation ↗Choose the right commercial scope.
The repository publishes its own license and release terms. StateSet iCommerce CX, OMS, WMS, TMS, and EDI have their own service scope, availability, and commercial agreement. Discuss hosted services or implementation support explicitly.
Looking for the engine that runs iCommerce CX workflows? Explore the StateSet iCommerce Engine →