Commerce that runs itself
Agents can reason. What they cannot yet do safely is execute — find the order, check the policy, issue the refund, update inventory, close the ticket — across systems that were built for a person with a mouse. Critical commerce work still sits between those systems, and today humans are the glue. StateSet is the iCommerce company. The StateSet iCommerce Engine is the execution layer for AI commerce: it gives autonomous agents a safe, deterministic way to operate orders, inventory, payments, returns, subscriptions and fulfillment across the systems you already run. From AI that answers to AI that executes.I'm building an agent
Embed a full commerce engine in your runtime. Orders, inventory, payments, returns — local,
typed, and agent-callable.
I'm running operations
Deploy agents that resolve customer work end to end. Priced per outcome, not per seat.
What we built
Plus the operational spine commerce actually needs:
EDI for trading partners,
Voice for phone,
Mail for email,
Sync across the platforms and 3PL/WMS systems a brand runs on, and a
Temporal engine that makes every automated action durable and
replayable.
Why it’s different
StateSet is not only an AI interaction layer or a workflow connector. It combines commerce semantics, deterministic execution, policies, integrations, auditability and outcome measurement. Commerce-native. The Engine understands commerce objects and their state transitions — not just text and API calls. Orders, inventory, payments, returns, fulfillment, warehouse, finance, with the invariants between them enforced in code. Safe execution. Probabilistic reasoning is bounded by deterministic validation, policies and approvals. When an agent issues a refund or grants access, NSR returnsapproved, denied, or refused with the cited rules behind it; an approval only executes
when its proof is grounded, and if the policy engine is unreachable the action escalates to a
human. A confidence number is not an authorization.
Close the operation, not just the conversation. Helpdesk AI automates the interaction and a
selected set of actions. StateSet is built to execute — and keep correct — the commerce operation
underneath it. That is also the only honest basis for pricing per outcome instead of per seat.
Embedded and deployable. iCommerce is an engine you compile into your runtime, not an
endpoint you call over the network — in-process, offline-capable, type-safe, with the data in a
database you control. Execution can run as close to your systems as you need it to.
Interoperable. No proprietary front door: every service speaks REST, most expose an MCP
server and a skill, and the protocols are the ones your agents already use.
The full case — differentiation, value, and the hard questions
How we compare to Stripe, RPA, and copilots, what it costs, and honest answers on trust,
lock-in, and where AI still gets things wrong.
Start building
The engine is open source, dual-licensed MIT OR Apache-2.0. Inspect it, fork it, run it anywhere.iCommerce Quickstart
Run the embedded engine.
MCP Servers
Connect any service to Claude.
API Reference
Every endpoint.
Explore by product
iCommerce
The embedded commerce engine — a Rust core with 10 language bindings.
ResponseCX
Outcome-priced AI agents for CX and commerce ops.
Temporal Engine
Durable, replayable automation in Rust.
NSR
Verified decisions with cited proofs.
Voice
AI voice agents over Twilio and OpenAI Realtime.
EDI
X12 and EDIFACT for trading partners.
Sandbox
Isolated execution environments for agents.
Sequencer
Verifiable event sequencing.
Set L2
On-chain anchoring of commitments and proofs.