Community OpenAPI document · agent-readyE CommerceOrder ManagementapiKey146 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Lets an AI agent read and write products, orders, categories, and customers across many e-commerce platforms through API2Cart's single unified interface.
Use for: I need to list products from a connected Shopify or Magento store, Add a new product to a merchant's store through API2Cart, Fetch recent orders across all connected stores, Create a customer record in a linked store
Not supported: Does not process payments, host storefronts, or manage shipping carriers; use it to read and write catalog, order, and customer data across connected e-commerce platforms only.
The API2Cart API gives developers a single integration to dozens of shopping cart and marketplace platforms. It reads and writes products, categories, orders, and customers across connected stores through one unified request format, and reports which platforms and webhooks each account supports. A store is linked once with a store key, after which the same calls work regardless of the underlying cart.
Install Jentic One Beta
Connect the API2Cart to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API2Cart, 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%2Fapi2cart.com%2Fapi2cart" | 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%2Fapi2cart.com%2Fapi2cart" | 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.
Capabilities
What an agent can do with API2Cart API.
Connect a merchant store to a supported cart or marketplace platform
Read and write products and their attributes across connected stores
Retrieve and create orders through one platform-agnostic interface
Organize catalog categories and product-to-category assignments
Access customer records from any connected store
Register webhooks and check which platforms an account supports
Use Cases
Patterns agents use API2Cart API for, with concrete tasks.
★ Sync products across multiple shopping carts
Merchants and tools that span several store platforms need one way to keep catalogs consistent. API2Cart reads and writes product data through a single interface, so an integration can push the same product update to a Shopify, Magento, or WooCommerce store without writing platform-specific code for each.
Read a product from one connected store and create the same product in another connected store.
Aggregate orders from every connected store
Back-office tools need a consolidated view of orders no matter where a sale happened. API2Cart lists and reads orders across all linked stores through one call format, letting an integration collect recent orders and their line items regardless of the underlying platform.
List orders created in the last day across all connected stores and read the line items for each.
Onboard a new merchant store
Before any data flows, a merchant's store must be connected. API2Cart links a store from its platform credentials, confirms which platform it is, and reports the operations and webhooks that store supports, so an onboarding flow can verify a connection end to end.
Connect a store with its platform credentials and confirm the connection by listing its supported operations.
Let an agent manage catalogs across platforms
An AI agent that maintains merchant catalogs can work across every platform at once through API2Cart. It reads current products and categories, applies updates, and registers webhooks for changes. Through Jentic the agent discovers these operations by intent and runs them under the integration's own credentials.
Given a product change, find the matching product in each connected store and apply the update.
Key Endpoints
146 endpoints — the api2cart api gives developers a single integration to dozens of shopping cart and marketplace platforms.
METHOD
PATH
DESCRIPTION
GET
/account.supported_platforms.json
List supported e-commerce platforms
POST
/account.cart.add.json
Connect a store to your API2Cart account
GET
/product.list.json
List products from a connected store
POST
/product.add.json
Add a product to a store
GET
/order.list.json
List orders from a store
POST
/order.add.json
Create an order in a store
GET
/category.list.json
List catalog categories
GET
/customer.list.json
List store customers
GET
/account.supported_platforms.json
List supported e-commerce platforms
POST
/account.cart.add.json
Connect a store to your API2Cart account
GET
/product.list.json
List products from a connected store
POST
/product.add.json
Add a product to a store
GET
/order.list.json
List orders from a store
POST
/order.add.json
Create an order in a store
GET
/category.list.json
List catalog categories
GET
/customer.list.json
List store customers
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
S
Swagger API2Cart
- Foundational (C-)50/100
47
Foundational Compliance56
Developer Experience & Jentic Compatibility34
AI-Readiness & Agent Experience69
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
47
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
88%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
34
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
37%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
0%
Summary Coverage
Coverage of summaries across operations/tags/info.
69
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: B+Signals: 1
69%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Integrating API2Cart yourself means juggling two keys, the store-linking step, and the per-platform quirks each cart hides behind its unified calls. With Jentic you install once, import the API from the Directory, and store your keys a single time.
Permission scoping
Running Jentic in your own instance, you decide which API2Cart operations the agent may call, so you can allow product and order reads while blocking writes or store changes. Access is granted per operation.
Credential isolation
Your API2Cart keys are held encrypted by your own Jentic One instance and injected only when an operation runs, so they never appear in the agent's prompt, logs, or context.
Intent-based discovery
Agents find API2Cart through Jentic's intent search: a request like list products from a store or create an order resolves to the right operation with inputs and auth prepared.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using API2Cart API through Jentic.
Is there an MCP server for the API2Cart API?
You do not need a dedicated MCP server. Through Jentic your self-hosted agent can call API2Cart operations directly by intent, so you connect the API without maintaining separate MCP tooling.
Can I control what my agent is allowed to do with the API2Cart API?
Yes. Because you run Jentic yourself, you choose which API2Cart operations your agent can call, so you can allow product and order reads while withholding writes or store connections. Scoping is applied per operation.
What authentication does the API2Cart API use?
API2Cart uses two keys. Your account key travels in the `x-api-key` header, and the key identifying a specific connected store travels in the `x-store-key` header. Jentic injects both from your stored credentials when a call runs.
Which e-commerce platforms does API2Cart cover?
API2Cart connects to many shopping cart and marketplace platforms behind one interface, and the account operations report the current list of supported platforms so an agent can confirm coverage before it connects a store.
Does API2Cart process payments or host storefronts?
No. It reads and writes catalog, order, and customer data on stores that already exist. Payment capture and storefront hosting stay with the underlying platform, not with these endpoints.
How does an agent discover API2Cart operations in Jentic?
The agent searches Jentic by intent, such as listing products from a store or creating an order, and Jentic returns the matching API2Cart operations ready to run under your credentials.
GET STARTED