Commerce Layer for AI agents

Commerce Layer provides the transactional backend for e-commerce, handling orders, inventory, and pricing through an API without a built-in storefront. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

E-commerceOAuth 2.0 client credentialsMCP + RESTcommercelayer.io
AUDIT LOG · COMMERCE LAYERPOLICY: acme-support
09:41:07 · claude · u_8f2read
commerce_layer.list_skus
List SKUs✓ allowed · 212ms
09:41:08 · claude · u_8f2read
commerce_layer.get_order
Get Order✓ allowed · 164ms
09:41:09 · claude · u_8f2write
commerce_layer.create_customer
Create Customer✓ approved · approved by user
09:41:12 · claude · u_8f2destructive
commerce_layer.delete_customer
Delete Customer✕ blocked · policy: deny
EVERY COMMERCE LAYER CALL, ON THE RECORD
01 · USE CASES

What agents do in Commerce Layer.

01

Check an order's status

Check an order's current status before updating a customer on their shipment.

02

Look up stock for a SKU

Look up a stock item's available quantity before confirming a product is in stock.

03

Confirm before deleting a customer

Confirm before deleting a customer record, since their order history stays tied to the account.

02 · ACTIONS

10 Commerce Layer actions, graded by risk.

Every Commerce Layer action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

7

Look things up. Allowed by default.

  • commerce_layer.get_order
    Get Order
  • commerce_layer.list_skus
    List SKUs
  • commerce_layer.list_orders
    List Orders
  • commerce_layer.get_customer
    Get Customer
  • commerce_layer.list_customers
    List Customers
  • commerce_layer.get_order_metric
    Get Order Metric
  • commerce_layer.list_stock_items
    List Stock Items

write

2

Create and change things. Allow, or ask the user first.

  • commerce_layer.create_customer
    Create Customer
  • commerce_layer.update_customer
    Update Customer

destructive

1

Delete, cancel or archive. Ask first, or deny outright.

  • commerce_layer.delete_customer
    Delete Customer
03 · HOW IT WORKS

Commerce Layer in three steps.

  1. 01Your users connect Commerce LayerThey add their Commerce Layer oauth 2.0 client credentials on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, writes like “create Customer” can wait for the user, and “delete Customer” can be denied outright.
  3. 03Any agent can actYour agent calls Commerce Layer through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('commerce_layer', {
  read: 'allow',
  write: 'ask',        // create_customer
  destructive: 'deny',  // delete_customer
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How Commerce Layer connects.

Connect Commerce Layer with a service credential for your workspace. Arc0 keeps it in the vault, exchanges it for short-lived tokens, and never passes it to the model.

The same Commerce Layer connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
OAuth 2.0 client credentials
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use Commerce Layer from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

Commerce Layer and Arc0, answered.

Q01

Can I use Commerce Layer with Claude, ChatGPT or Cursor?

Yes. Connect Commerce Layer to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Commerce Layer actions you allow.

Q02

How do users connect Commerce Layer?

Connect Commerce Layer with a service credential for your workspace. Arc0 keeps it in the vault, exchanges it for short-lived tokens, and never passes it to the model.

Q03

Which Commerce Layer actions can my agent take?

10 in total: 7 read, 2 write and 1 destructive, such as “create Customer”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Commerce Layer?

Yes. Actions like “delete Customer” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Commerce Layer too?

Yes. The same Commerce Layer connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Commerce Layer into your agent.

Your users connect Commerce Layer once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.

Free to build · MCP + REST · Audit log on every plan