StateSet Documentation

Build commerce applications, connect AI agents, and automate customer operations. Choose a starting point and make your first working request.

StateSet provides a commerce engine for orders, inventory, payments and returns, alongside services for customer support, integrations, workflows and verified decisions.

New to StateSet? Start with Your First Operation. Create a local order and inventory fixture, answer a stock question, and hand the same task to an AI agent. The walkthrough generates the connection configuration and real record IDs for you.

Already have business data? Connect your operation explains data ownership, service prerequisites, and how to verify a complete result.

For a specific system or task, choose a path below. Each hosted service has its own setup and credentials; the embedded commerce engine runs inside your application.

Run your first operation

Inspect an order and stock locally, then verify an AI agent’s answer against the same database.

Create a customer support agent

Authenticate, create a ResponseCX agent, and read it back with a complete curl walkthrough.

Give an agent an operational task

Select a data source, supply a task brief, and verify the agent’s tool results.

Find an API endpoint

Match your task to the right service, base URL, authentication header and reference.

Choose how to build

Your starting point	What you need	First verified result
Explore locally	Node.js 20.20.0+ and npm 10+	Order and stock check, with no hosted key
Add an AI agent to the local example	An MCP host with its own model connection	The same record IDs and quantities from tool calls
Configure customer support	ResponseCX workspace and scoped key	Inactive agent created and read back
Connect existing business systems	Tenant access and configured source/destination connectors	Verified workflow across your systems

Choose the interface that fits your application:

Interface	Use it when	Start here
Embedded library	Your application should operate commerce data in its own process	Embedded engine · Language bindings
REST API	Your application needs a service over HTTP	API directory · Developer guide
MCP	An AI agent needs tools for a specific service	MCP servers · Agent setup
ResponseCX app	Your team needs to configure customer support automation	ResponseCX platform

Embedded commerce and hosted APIs have different setup paths. The embedded engine uses a database in your application. Hosted services use their own base URLs and keys. Check the API directory before copying a request between services.

Build a complete workflow

These guides connect individual API calls into a task you can verify end to end.

Resolve an order-status request

Follow a customer question through order lookup, a decision and an operational response.

Sync Shopify and NetSuite

Configure the integration and inspect its sync results.

Run a durable workflow

Start an automation and follow its execution through the Temporal Engine.

Verify a refund decision

Define a policy, inspect the verdict, and verify the approval before executing an action.

Explore the services

Service	What it handles	Guide
iCommerce	Orders, inventory, payments, returns and other commerce operations	Overview
ResponseCX	Customer support agents, knowledge, tools and conversations	Platform guide
Sync	Data exchange between commerce systems	Integration walkthrough
Temporal Engine	Durable workflows and automation	Getting started
NSR	Policy decisions and verifiable proofs	Decision guide
Voice	Voice agents and calls	First voice agent
EDI	Trading partners and business documents	First purchase-order cycle
Sandbox	Isolated runtimes for agent code and tools	First runtime
Computer Use	Tasks in software user interfaces	First task
Mail	Email and inbox operations	Quickstart

Get unblocked

• A request fails: compare the service host and header, then read the error guide.
• A host is unavailable: check the timestamped host status report.
• You need help: use the support checklist to share a reproducible request.
• You are evaluating StateSet: read Why StateSet and the architecture overview.
• You are returning after an update: check the documentation changelog.