CS-Cart APIs for AI Agents
E CommerceStorefrontMixed ProvenanceBasic authAgent Ready
For Agents
APIs2 in catalogue
Endpoints76 indexed
AuthBasic auth — 1 credential for all 2 APIs
ProvenanceMixed provenance
An agent can run a CS-Cart storefront end-to-end: create and update products, reorganise the category tree, inspect and progress orders, manage carts, track shipments, configure payment methods, and administer customer and admin users across both the CS-Cart 2.0 API and the version 4 REST surface.
CS-Cart is a self-hosted e-commerce platform, so both API surfaces authenticate against the merchant's own store domain rather than a hosted tenant, and the resource id sits in the URL path for every product, order, and user. The 57-endpoint CS-Cart 2.0 API covers the full storefront lifecycle including carts, shipments, payments, and CMS pages, while the version 4 REST surface offers a tighter 19-endpoint slice for products, categories, orders, and users.
CS-Cart API Catalog
2 APIs across 1 product group. All share one credential.
E Commerce2
Which CS-Cart API should I use?
| I want to... | Use |
|---|---|
| Full storefront operations including carts, shipments, payment methods, and CMS pages | CS-Cart API |
| Core product, category, order, and user management on a CS-Cart 4 store | CS-Cart REST API |
| Reading or writing products and categories | CS-Cart API |
| Reading or writing products and categories | CS-Cart REST API |
Install Jentic One Beta
Connect the CS-Cart APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CS-Cart APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcs-cart.com" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcs-cart.com" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “manage a CS-Cart storefront products and orders”.
What AI Agents Can Do with CS-Cart
Each workflow spans multiple CS-Cart APIs. Jentic routes each operation to the right API automatically.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the CS-Cart APIs by hand means building the Basic auth pair from an admin email and API key, resolving your own store domain into the base URL, and handling retries across dozens of endpoints on two surfaces. With Jentic you install once, add the CS-Cart APIs you need from the Jentic API Directory, store the email and API key once, and your agent calls both surfaces with the same setup.
Permission scoping
CS-Cart puts the resource id in the URL path for products, orders, and users across both APIs, so a rule can pin your agent to a specific resource. You choose which operations the agent may call, so writes like creating or updating a product are not included unless you add them, and read-only workflows stay read-only.
Credential isolation
Your CS-Cart admin email and API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They cover both API surfaces and never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as 'add a product to a CS-Cart store' or 'update an order status', and Jentic returns the matching CS-Cart operation with its input schema so the agent calls the right endpoint on the right surface without browsing the reference docs.
FAQs
Specific to using CS-Cart APIs through Jentic.
What can an AI agent do across the CS-Cart APIs?
An agent can manage the product catalogue and category tree, inspect and progress orders, review in-progress carts, track shipments, configure payment methods, publish CMS pages, and administer customer and admin users. The CS-Cart 2.0 API covers the full storefront lifecycle across 57 endpoints, while the version 4 REST surface offers a tighter 19-endpoint slice for products, categories, orders, and users.
Which CS-Cart API should I use?
Use the CS-Cart 2.0 API when a workflow needs carts, shipments, payment methods, or CMS pages, since it is the broader surface. Use the version 4 REST surface when the workflow only touches products, categories, orders, and users on a CS-Cart 4 store. Both authenticate the same way, so an agent can move between them without new credentials.
Do the two CS-Cart APIs share credentials?
Yes. Both surfaces use HTTP Basic authentication with the store admin email and a generated API key, so a single admin credential pair works for both. Each request is still templated against the specific store's own domain, so the store URL is configured per store.
Does CS-Cart publish an official OpenAPI specification?
CS-Cart does not publish its own OpenAPI specification. Jentic generates and maintains the specs for the version 4 REST surface and the read-focused slice, keeping them validated against the live API so agents and developers can call them through structured tooling.
Is CS-Cart self-hosted, and how does that affect the APIs?
CS-Cart is a self-hosted platform, so the store runs on the merchant's own infrastructure and every API request is templated against that store's own domain. There is no shared hosted tenant, and throughput is bounded by the host's PHP-FPM and database capacity rather than a published application rate limit.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.