Industry · Retail and e-commerce

Shopping agents that know the shopper.

Remember each shopper's preferences, keep their session state, and let the agent act on store and payment APIs without holding the keys.

Get started Talk to us

How it fits

Built from the primitives you already get.

Preferences that persist

Sizes, brands and past orders are stored as memories per shopper and recalled when they matter.

Session state

Carts, comparisons and order drafts live in KV with a TTL, so abandoned sessions expire on their own and kv_set increments counters atomically.

Store APIs by reference

Commerce and payment API keys are injected per request with host and method grants. The agent never reads them.

Timed follow-ups

Queue delayed messages for restock alerts, abandoned carts and delivery updates.

Solutions

More industries

Developer platforms

Backends for the apps and agents your users build.

Customer support

Support agents that remember each customer and follow up on time.

Financial services

Isolated client data, credentials agents can't read and a full audit trail.

Build

Local-first development.

Build and test on your machine with the open-source engine. No cloud account needed: every primitive runs locally, with the same API as the cloud.

$ curl -fsSL https://useprimitives.com/install.sh | sh

Install the CLI, then run primitives dev. Quickstart

Open source

Built in the open. Contribute freely.

The SDKs, the MCP server and the single-node engine are open source and actively maintained. Submit PRs, report issues, improve docs, or just star the repo to show support.

useprimitives/primitivesFork, star, or open a pull request