Vtex Checkout API

Setup

Wiring the VTEX Checkout API by hand means setting both the X-VTEX-API-AppKey and X-VTEX-API-AppToken headers, resolving the account and environment host template, and managing the order form calls yourself. Through Jentic you install once, import the Checkout API from the API Directory, store the key pair once, and your agent calls it.

Permission scoping

The Checkout API puts the order form id in the URL path (/api/checkout/pub/orderForm/{orderFormId}), so a rule can pin your agent to reading one order form and simulating a cart. You choose the operations it may call, so ones like removing all items are not included unless you add them.

Credential isolation

Your VTEX AppKey and AppToken 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.

Intent-based discovery

Agents search Jentic by intent such as 'simulate a cart' or 'read an order form', and Jentic returns the matching Checkout API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.