IntegrationsStart free

Connect your store. The chat already knows the order.

VTEX and OpenCart connected to the AI agent to look up orders and products mid-conversation. A built-in catalog for businesses selling without an online store. And signed webhooks and an API for any other system.

Start free Talk to sales

Native connectorsEverything else through the API and signed webhooks

9:41

Northwind HomeBusiness accounttyping…typing…

Hi! Has my order 4821 shipped yet?7:40 PM

AI · looked up the order

It left this morning and it's with the carrier now. Want the delivery estimate?7:40 PM

Yes, please!7:41 PM

AI agent

It should arrive on Oct 22.7:41 PM

What the AI seesVTEX connector

Waiting for a questionLooking up order 4821Order found

Order: 4821
Status: Shipped
Amount: US$86.90
Items: 2
Delivery estimate: Oct 22
Address: Stays out
Tax ID: Stays out

Sample conversation. Fictional data.

What connects today, with no integration project.

Everything below exists in the product and runs in production. Anything not listed talks to CCX through the API and webhooks.

Native connector

VTEX

With your store's App Key and App Token, the AI looks up orders and products during the conversation. The catalog is copied into CCX and refreshed every 6 hours.

Native connector

OpenCart

With access to your store's API, the AI finds orders by number and looks up products. The catalog is copied into CCX too.

No online store

CCX catalog

Upload a CSV spreadsheet or add products in the dashboard, with photo, price and availability. The AI answers with them in the chat.

Your system

Agent HTTP tool

Describe an endpoint of yours and the AI calls it to look things up. Anything that writes isn't run by the AI: the conversation goes to a person.

Outbound

Webhooks

Delivery, read, failure and reply events for WhatsApp, SMS, RCS, email and Instagram reach your system signed, plus balance alerts.

Inbound

Events API

Your system reports that the customer bought, and CCX ties the purchase to the last message they received within the window you choose (7 days by default). The same event can start a journey.

Legacy SMS

SMPP

For teams that already have an SMPP client, over a TLS-encrypted connection, without rewriting the integration.

Every other store, ERP or CRM connects through the same API and webhooks

The AI reads the order. Changing anything is up to a person.

Connectors only look things up: orders, products and the catalog. Your own HTTP tool lets the AI look things up in your system too; anything that would write goes to a person.

Reading: answers on its own

Customer asks about order 4821
Connector looks up the order in the store
AI answers with the status and delivery details

Orders, products and the catalog. Reads from your own HTTP tool run directly too.

Writing: goes to a person

AI agent · wanted to use your HTTP tool

Change the delivery address on order 4821Sample request. It would write to your system, so the AI doesn't run it.

Handed to your team, with the conversation and what the customer asked for.

Reads run on their own. Any call that writes, or that you mark as sensitive, is never made by the AI: a person picks up the conversation.

On OpenCart, an order only shows up if its phone or email matches the person in the chat.

The reply carries the order number, status, amount, items and the delivery estimate or tracking. Address and tax ID stay out.

Store credentials are stored encrypted and only shown masked after saving.

Internal network addresses are blocked on outbound calls.

Status updates reach your system, signed.

Every event carries an HMAC-SHA256 signature from your secret and a timestamp. Before saving the URL, CCX checks the address and sends a signed ping.

Five more attemptsIf your endpoint fails, we retry with growing waits: 5 seconds, 30 seconds, 2 minutes, 10 minutes and 1 hour.

Idempotency keyEvery delivery carries an X-CCX-Idempotency-Key so your system can drop repeats.

Your own headersSend the headers your system requires; they're stored encrypted.

Rotatable secretGenerate a new secret whenever you like, without recreating the subscription.

410 responseIf your endpoint answers 410, the subscription is cancelled.

Retries when your endpoint fails, with growing waits

5 s
30 s
2 min
10 min
1 h

POST your-system.com/webhooks/ccx

POST https://your-system.com/webhooks/ccxX-CCX-Signature: t=1791300000,v1=5f2c…X-CCX-Event: message.deliveredX-CCX-Delivery-Id: …X-CCX-Idempotency-Key: …X-Store-Token: …   // your own header {  "event": "message.delivered",  "messageId": "msg_…",  "channel": "whatsapp",  "metadata": { "order": "4821" },  "occurredAt": "2026-10-06T14:02:11Z"}

message.deliveredwhatsapp
message.readwhatsapp
email.openedemail
wallet.low_balancewallet

Sample events from different channels, each signed

Sample webhook delivery, trimmed. Your own headers go along with every delivery, stored encrypted.

No connector? There's an API.

The platform you already use can talk to CCX through the public API, with your organization's key: contacts, lists, events, journeys, sales pipeline and sending on every channel.

/contactsContacts and opt-out

/v2/listsLists

/v2/eventsCustomer events

/v2/journeysJourneys

/pipelinesSales pipeline

/messagesWhatsApp sending

A few routes from the public API. The full reference lives in the OpenAPI document.

See the API Request a connector

Tie the sale to the message

Your system reports that the customer bought, and CCX ties the purchase to the last message they received within the window you choose, 7 days by default. The same event can start a journey.

Inside the window: the purchase counts for the message.

Illustration of the default window. Purchases are reported through /v2/events.

Connectors carry no extra monthly fee.

Connecting your store costs nothing extra. When the AI looks up an order or a product, the interaction is billed as AI with tools.

See full pricing

What you use	Price
Connectors, webhooks and API	No extra charge
AI with tools	from US$0.09 per interaction
Simple AI	from US$0.02 per interaction
Plans	from US$39/mo

International price list in US dollars, euros for eurozone destinations. Messages are billed at each channel's price.

Before you connect your store

Still unsure? Talk to the team that runs the platform.

Talk to sales

Do I need a developer to connect VTEX or OpenCart?

No. For VTEX, generate the App Key and App Token in your store admin and paste them into the AI agent settings; for OpenCart, enter your store's address and API access. Only API integrations need someone technical.

Can the AI change an order?

Not through the connectors: they only look things up. With an HTTP tool of your own, the AI doesn't make calls that write to your system; it hands the conversation to a person.

My platform isn't listed. What now?

It can talk to CCX through the API and webhooks: send contacts and events, receive statuses and replies. If you'd like a ready-made connector, get in touch.

How do I check a webhook came from CCX?

With your secret, recompute the HMAC-SHA256 of the timestamp, a dot and the body, and compare it with the X-CCX-Signature header. You can rotate the secret at any time.

What if my endpoint goes down?

We retry five times, with growing waits from 5 seconds to 1 hour. If it answers 410, the subscription is cancelled.

Can I use it without an online store?

Yes. The CCX catalog takes a CSV spreadsheet or products added in the dashboard, and the AI answers with it the same way.

Customers ask about the order. The chat already knows.

Start free Talk to sales