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

# Centra Checkout API

The Centra Checkout API powers a headless storefront checkout. It reads the current selection, adds items and lines to it, adjusts line quantities, and places an order with a payment. It also registers and logs in customers, reads the customer, and lists reference data such as markets, countries, and warehouses. Authentication uses an API token, with a bearer shared secret on some operations.

## For AI agents

Read a Centra selection, add items and lines, adjust line quantities, place an order with payment, register and log in customers, and list markets, countries, and warehouses.

## Scope

Does not manage catalog inventory, fulfill orders, or run store administration. Use for building a Centra selection and placing checkout orders only.

## Capabilities

- Read the current selection and add items and lines to it
- Adjust the quantity on a selection line
- Place an order and submit a payment
- Register and log in a customer
- List reference data such as markets, countries, and warehouses

## Use cases

### AI agent headless checkout

An AI shopping agent can build a cart and place an order on a Centra storefront on demand. Through Jentic the agent searches by intent and the API token never enters its prompt context, so a checkout assistant can add items and order without a hand-built integration.

Example prompt: Use Jentic to search 'add an item to a cart', call POST `/items/{item}` to add it, then POST /orders followed by POST /payment to place and pay for the order.

### Cart line management

As a shopper changes their mind, the agent adjusts the cart. It reads the current selection and updates a line's quantity, keeping the cart accurate before checkout.

Example prompt: Read the cart via GET /selection, then adjust a line with PUT `/lines/{line}/quantity/{quantity}.`

### Customer account flow

A storefront agent registers a new shopper or logs in a returning one before checkout. It registers or logs in the customer and reads the customer record, so the order is tied to the right account.

Example prompt: Register a shopper via POST /register or log one in with POST `/login/{email}`, then read the account with GET /customer.

### Storefront reference data

Building a valid order needs reference data like markets and countries. The agent lists the markets and countries the store supports so a checkout workflow presents the right options.

Example prompt: List markets with GET /markets and countries with GET /countries to build a valid checkout.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/selection` | Read the current selection |
| POST | `/items/{item}` | Add an item to the selection |
| POST | `/lines/{line}` | Add a line to the selection |
| PUT | `/lines/{line}/quantity/{quantity}` | Set a line's quantity |
| POST | `/orders` | Place an order |
| POST | `/payment` | Submit a payment |
| POST | `/register` | Register a customer |
| POST | `/login/{email}` | Log in a customer |
| GET | `/customer` | Read the customer |
| GET | `/markets` | List markets |

## Key resources

- **Selection** — The current cart of items and lines
- **Orders** — Placed orders and their payment
- **Customer** — Registered and logged-in shoppers
- **Markets** — Markets, countries, and warehouses the store serves

## 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:** 35 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 33 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 17 / 100
  - Agent Usability: 88 / 100
  - Security: 53 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/centra.com/centra/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 Centra Checkout API by hand means managing its API-Token header, and a bearer shared secret on some calls, against johnsmedley.centraqa.com and encoding the selection, order, and payment calls yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Centra puts the item, line, and quantity in the URL path (`/lines/{line}/quantity/{quantity}`), so a rule can pin your agent to cart operations. You choose the operations it may call, so placing an order or submitting a payment is not included unless you add it.
- **Credential handling:** Your Centra API token and bearer secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add an item to a cart' or 'place an order', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Shopify runs storefronts and checkout across a broad commerce platform
- **Shopware** — Shopware provides storefront and checkout for its commerce platform
- **Square** — Square processes payments and manages orders across online and in-person sales

## FAQ

### Is there a Centra Checkout API MCP server?

You don't need an MCP server to give your agent Centra. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the selection, order, and payment operations. That keeps your agent's context free of an extra server's tool definitions.

### What authentication does the Centra Checkout API use?

It authenticates with an API token in the API-Token header, and some operations use a bearer shared secret, per its OpenAPI spec. Through Jentic these are stored encrypted by your own instance and injected at call time, so they never reach the agent's context.

### Can I build a cart and place an order with the Centra Checkout API?

Yes. POST `/items/{item}` adds an item to the selection, GET /selection reads the current cart, and POST /orders followed by POST /payment places and pays for the order.

### How do I add an item to a cart through Jentic?

Search Jentic for 'add an item to a cart', load the input schema, and execute POST `/items/{item}.` To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only the selection-read and add-item operations, so the agent can build a cart and read it and nothing else, and every call it makes is logged. Placing an order or submitting a payment stays out unless you add those operations.