An AI agent for commercetools, without the integration project
Algomo learns the endpoints behind your storefront, so a bespoke stack is the normal case, not an extra cost.
What it does
- Reads what your storefront actually calls, not a standard schema.
- Live catalogue, price and availability, as your projection and pricing rules shape them for that customer.
- Adds to the real cart in the customer's own session.
- Custom fields too: if your storefront can show it, the agent can use it.
What it needs from you
A URL. Public storefront endpoints are discovered. Anything behind customer auth is connected with us.
What the agent works with on commercetools
It sees your data exactly as your storefront receives it.
- Product projections. It works from the projected catalogue your storefront requests, not the raw product schema.
- Price selection. Prices arrive already selected for that customer, with your pricing rules applied.
- Carts. Adds to the real cart in the customer's own session.
- Custom fields. If your storefront can show it, the agent can use it, custom fields included.
FAQ
Does Algomo require a commercetools integration project?
No. It works from the calls your storefront already makes, so there is nothing to scope or build.
Does it work with a bespoke or headless commercetools storefront?
Yes. It reads your storefront's own calls rather than a standard schema, so bespoke and headless builds are the normal case.
Can the agent see customer-specific prices?
Yes. It works in the customer's own session, so price and availability arrive as your pricing rules shape them for that customer.
Can an AI agent add items to a commercetools cart?
Yes. It adds to the real cart in the customer's own session.
Does it work with custom fields?
Yes. If your storefront can show a custom field, the agent can use it.
What does Algomo need to get started?
A URL. Public storefront endpoints are discovered; we help you connect anything behind customer auth.
What happens when our storefront changes?
The agent notices, rescans and rebuilds what depended on the changed endpoint.