Make your Saleor store shoppable by AI agents.
This SDK adds UCP and ACP protocol endpoints to your existing Next.js storefront, so AI shopping agents can discover your products, create checkouts, and complete purchases — without any changes to your Saleor backend.
AI agents are becoming the next commerce channel. Just like merchants once added mobile apps alongside their websites, they'll soon need to serve autonomous agents that shop on behalf of consumers. But agents don't browse — they need structured APIs with standardized discovery, checkout flows, and payment settlement.
UCP (Universal Commerce Protocol) and ACP (Agentic Commerce Protocol) are the emerging open standards for this. This SDK implements both, so your Saleor store speaks the language agents understand.
- Agent discovery — A
.well-known/ucpprofile that tells agents what your store supports, which payment methods are available, and where the API lives - Checkout sessions — Agents can create carts, set shipping addresses, select delivery options, and complete purchases through protocol-compliant endpoints
- Pluggable payments — Ships with Finance District Prism for stablecoin payments (x402/EIP-3009), or implement your own payment handler
- No backend changes — Everything runs in your Next.js storefront layer, consuming the same Saleor GraphQL API your storefront already uses
- Zero runtime dependencies — The packages add no transitive dependencies to your project
| Package | What it does |
|---|---|
@financedistrict/saleor-agentic-commerce-core |
Protocol types, Saleor-to-protocol formatters, payment handler interface |
@financedistrict/saleor-agentic-commerce-nextjs |
Ready-made Next.js App Router route handlers for UCP and ACP |
@financedistrict/saleor-prism-payment |
Prism payment handler — stablecoin settlement via x402/EIP-3009 |
@financedistrict/saleor-dummy-payment |
Always-succeeds simulator — for integration testing and as a reference implementation for new handler authors |
@financedistrict/saleor-agentic-commerce-skill |
Claude Code plugin — /setup-agentic-commerce, /add-payment-handler, /diagnose-agentic-commerce |
The apps/saleor-agentic-commerce-app folder also contains an optional Saleor Dashboard App that acts as a control plane for the SDK — see The App is Optional on the wiki for the three configuration paths.
The wiki is the canonical reference. Highlights:
- Quick Start — get a Saleor storefront agent-shoppable in 5 minutes
- Architecture — the gateway pattern and design framing
- Storefront SDK — full configuration reference and route wire-up
- The App — what the Saleor Dashboard App does (FD-hosted by default, self-host optional)
- The App is Optional — three configuration paths (env-only, App-managed, hybrid)
- Build a Handler — author your own payment handler package
- Saleor Cloud — Cloud-specific setup notes
- UCP and ACP — protocol overview and conformance status
- Authentication — five token contexts in this stack
- Glossary — terminology reference
If you use Claude Code, install the skill plugin and let Claude set everything up:
/setup-agentic-commerce
See packages/claude-skill for installation options.
All published packages follow semver. Releases are automated via Changesets — see CONTRIBUTING.md for the flow.
Issues and pull requests welcome. See CONTRIBUTING.md for the basics and the wiki for architecture and integration guides.
If you're shipping a new payment handler package, you don't need to fork or PR this repo — handler packages live in their own repos and self-register at storefront boot. See the Build a Handler wiki page.
MIT © 2026 Finance District.
The project is built for eventual handover to a neutral steward (e.g. Saleor, a protocol foundation) — see Architecture: The gateway pattern on the wiki for the framing.