Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / E Commerce / CS-Cart
CS-Cart logo

CS-Cart APIs for AI Agents

www.cs-cart.com·Developer portal → docs.cs-cart.com

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.

Use for: Managing a self-hosted CS-Cart storefront over its API: product catalogue and categories, orders and fulfilment status, carts, shipments, payment method configuration, CMS pages, and customer and admin users.

Not supported: payment processing, shipping rate quoting, shipping label generation, hosting infrastructure, storefront theme rendering

Credentials: Both APIs use HTTP Basic authentication with the store admin email as username and a generated API key as password, so one admin credential pair covers both surfaces, though each request is templated against the specific store's own domain.

Across 2 CS-Cart APIs: 1 third-party, 1 Jentic-generated, all indexed by Jentic and kept validated and agent-ready.

CS-Cart is an e-commerce platform for running single-vendor stores and multi-vendor marketplaces. Its APIs expose the storefront lifecycle over HTTP: managing the product catalogue and category tree, handling carts and checkout, processing orders and shipments, configuring payment methods, and administering customer and admin users. Jentic makes both the CS-Cart 2.0 surface and the version 4 REST surface available to AI agents, so an agent can read and write storefront data without a bespoke integration per store.

Jentic One on Github

CS-Cart API Catalog

2 APIs across 1 product group. All share one credential.

E Commerce2

CS-Cart APIRun a CS-Cart 2.0 storefront end-to-end: catalogue management, cart and checkout, order fulfilment, shipments, payments, and CMS pages.~57 endpointsCS-Cart REST APIManage products, categories, orders, and users on a CS-Cart 4 storefront through a 19-endpoint REST surface.~19 endpoints

Which CS-Cart API should I use?

I want to...UseWhy
Full storefront operations including carts, shipments, payment methods, and CMS pagesCS-Cart APIThe CS-Cart 2.0 API spans 57 endpoints covering the whole lifecycle from catalogue through checkout, fulfilment, and content.
Core product, category, order, and user management on a CS-Cart 4 storeCS-Cart REST APIThe version 4 REST surface exposes full CRUD across the major storefront entities in a tighter 19-endpoint set.
Reading or writing products and categoriesCS-Cart APIUse the 2.0 API when you also need carts, shipments, payments, or CMS pages in the same workflow.
Reading or writing products and categoriesCS-Cart REST APIUse the version 4 REST surface when the workflow only touches products, categories, orders, and users.

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" | sh
2

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 instance

Jentic 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.

Catalogue write plus lifecycle operations

Use the version 4 REST surface to bulk create and update products and categories from a source of truth like a PIM, then switch to the CS-Cart 2.0 API to drive the parts of the storefront the slimmer surface does not reach, such as reviewing carts, tracking shipments, and publishing CMS pages. An agent can keep merchandising in one place while still operating checkout and fulfilment.

Example prompt:

Create or update products through the version 4 REST surface, then call the CS-Cart 2.0 API to update shipment status and publish a related CMS page.

APIs used

CS-Cart REST API + CS-Cart API

Order reconciliation across store versions

For merchants operating both a CS-Cart 4 store and a CS-Cart 2.0 store, an agent can list and inspect orders from each surface and reconcile them into a single downstream system such as an ERP or data warehouse. Reading orders through both APIs gives finance one consolidated view across store versions.

Example prompt:

Poll orders from both the version 4 REST surface and the CS-Cart 2.0 API, normalise the line items and totals, and post each order into the ERP.

APIs used

CS-Cart REST API + CS-Cart API

Customer sync with fulfilment follow-up

Create or update customer records through either surface and then use the CS-Cart 2.0 API to inspect the customer's orders, carts, and shipments so an agent can answer support questions or trigger fulfilment follow-up. This joins user administration with the order and shipment detail only the broader surface exposes.

Example prompt:

Create or update the customer through the version 4 REST surface, then call the CS-Cart 2.0 API to list that customer's orders and shipments for a support reply.

APIs used

CS-Cart REST API + CS-Cart API

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.

Are the CS-Cart APIs free to use?

API access is included with every CS-Cart license at no separate per-call charge. CS-Cart sells annual and perpetual licenses with multiple editions, and license pricing is published at https://www.cs-cart.com/buy-license.html.

Can I run both a CS-Cart 4 store and a CS-Cart 2.0 store from one agent?

Yes. The version 4 REST surface and the CS-Cart 2.0 API can both be added to your workspace, and an agent can read and reconcile orders, products, and customers across both store versions into a single downstream system such as an ERP or data warehouse.

If you need a different E Commerce vendor

All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.

ShopifyHosted e-commerce platform with managed REST and GraphQL admin APIs, an alternative when a merchant wants managed scaling rather than a self-hosted store.
MagentoOpen-source e-commerce platform with a broad REST surface and deeper B2B features, an alternative for teams comfortable operating a heavier self-hosted stack.
StripePayments and subscription billing that complement a CS-Cart storefront when the agent needs to reconcile charges or refunds against orders.

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.

Book a Demo