Commerce Layer for AI agents
Agents read Commerce Layer at once. Changes and sends are held for a person's approval by default.
About Commerce Layer
Commerce Layer provides transactional commerce and analytics APIs for managing orders, inventory, pricing, customers, fulfillment, and related ecommerce operations.
What an agent can do in Commerce Layer
Every Commerce Layer action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Commerce Layer without asking first. 7 actions.
- Get CustomerRetrieve one customer by its Commerce Layer resource ID.
- Get OrderRetrieve one Commerce Layer order by ID, optionally including customer, line-item, shipment, or return context.
- Get Order MetricCompute one common order KPI over optional date, market, currency, and status filters using the Commerce Layer Metrics API.
- List CustomersReturn one page of customers, optionally filtered by an exact email address.
- List OrdersReturn one page of orders, newest first by default, for operational review and follow-up by order ID.
- List SKUsReturn one page of catalog SKUs for product discovery and ID lookup.
- List Stock ItemsReturn one page of stock items with inventory quantities and SKU codes.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 3 actions.
- Create CustomerCreate one Commerce Layer customer from an email and optional external-reference metadata. Use a unique email or reference for automation. This mutation is cleanly undoable with DELETE_CUSTOMER using
- Delete CustomerPermanently delete one Commerce Layer customer by exact ID. This irreversible operation requires explicit confirmation and is intended only for confirmed cleanup or erasure, never bulk deletion. Never
- Update CustomerUpdate selected attributes of one Commerce Layer customer. Only non-null fields supplied by the caller are changed. Inspect the customer first when rollback matters; restoring the captured values reve
Changes wait in Needs you
Changes and sends in Commerce Layer are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Commerce Layer questions
Can an agent change data in Commerce Layer on its own?
Not by default. Changes and sends in Commerce Layer are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Commerce Layer?
This connector lists 7 read actions. Reads run at once, without waiting for approval.
How does Commerce Layer connect?
It connects with Server-to-server OAuth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.