canonical: https://jentic.com/apis/surecart.com/surecart

# SureCart API

SureCart e-commerce platform API for managing products, customers, orders, subscriptions, coupons, prices, and more. The API exposes 34 endpoints secured with bearer authentication.

## For AI agents

Programmatically create product, list products. Covers 34 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create product
- List products
- Get product
- Update product
- Delete product

## Use cases

### E-Commerce Operations

Use the SureCart API to perform e commerce operations programmatically. The API provides 34 endpoints covering core functionality including create product, list products, get product.

Example prompt: Call POST /products to create product

### Automated Account Management

Automate account operations by combining multiple SureCart API endpoints. Agents can list products and then get product in a single workflow.

Example prompt: Call GET /products to list products, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SureCart API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'create product', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/products` | Create product |
| GET | `/products` | List products |
| GET | `/products/{id}` | Get product |
| PATCH | `/products/{id}` | Update product |
| DELETE | `/products/{id}` | Delete product |
| POST | `/customers` | Create customer |
| GET | `/customers` | List customers |
| GET | `/customers/{id}` | Get customer |

## Key resources

- **Account** — Operations related to Account
- **Charges** — Operations related to Charges
- **Coupons** — Operations related to Coupons
- **Customers** — Operations related to Customers
- **Orders** — Operations related to Orders

## AI readiness

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.

- **Score:** 69 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/surecart.com/surecart/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the SureCart API by hand means handling its bearer token auth against api.surecart.com and managing retries yourself. Through Jentic you install once, import the SureCart API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The SureCart API puts the product and customer ids in the URL path (`/products/{id}`, `/customers/{id}`), so a rule can pin your agent to one product or customer: it can read and update that resource and nothing else. You choose the operations it may call, so destructive ones like deleting a product are not included unless you add them.
- **Credential handling:** Your SureCart API bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a product' or 'list customers', and Jentic returns the matching SureCart API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the SureCart API use?

The SureCart API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I create product with the SureCart API?

Yes. Use the POST /products endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the SureCart API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I create product through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create product'. Jentic returns the matching SureCart API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the SureCart API have?

The SureCart API exposes 34 endpoints covering account, charges, coupons operations.

### Can I limit what my agent is allowed to do with the SureCart API?

Yes. Because you run Jentic One yourself, your own rules decide which SureCart API operations and credentials the agent may use, and you can grant it only the calls you intend. Since product and customer ids sit in the URL path (`/products/{id}`, `/customers/{id}`), a rule can pin the agent to a single product or customer so it reads and updates that resource and nothing else. Destructive operations like DELETE `/products/{id}` stay off unless you explicitly add them.