Skip to main content
A personal agent can find products, prepare a purchase, and ask its owner to complete the steps that need human approval. Conto gives you several ways to connect that shopping flow to the buyer’s spending limits and payment method. Choose based on whether Conto or your own agent runs checkout.

​
Choose your shopping integration

For MCP agents, the Conto Commerce tools start and follow purchases without returning card details. The same reference covers checkout checkpoints and the connected-card listing tool. Credential handling belongs in trusted code outside the model transcript.

​
Buy with Conto Commerce

Your platform maps a signed-in user to a buyer, creates a hosted setup link, and starts a purchase with a product URL, task, and maximum total. Conto follows the purchase under one ID. Your app answers supported delivery forms and opens the buyer’s secure action link when review or verification is required. Start with the test-store quickstart. It uses a test card and creates no real charge. Live purchases require enablement for your organization, the supported plan and payment setup, and a supported store flow. Read the capability response before offering live purchasing to users. The Purchases API also covers grocery lists, buyer kitchen context, store allowances, events, cancellation, and payment evidence. Some of these features require separate enablement. Preserve the same purchase ID and idempotency key when recovering from an interruption; a missing response is not permission to submit another order.

​
Discover products

Conto’s shopping chat combines web search with Shopify UCP catalog discovery. It checks product candidates against the shopper’s request, budget, and stock before showing results. A catalog result supplies product information; it does not authorize a purchase. The Purchases API starts from the product URL and task you provide. UCP discovery in Conto’s shopping chat does not add a public catalog-search method to that API. If your personal agent already finds products, pass its selected product URL into the purchase flow.

​
Keep the buyer in control

With connected cards, the owner sets limits and verifies the purchase authorization before your integration requests a credential. With checkout checkpoints, your runtime must honor Conto’s decision: an agent with unrestricted payment access can bypass a checkpoint. Choose a payment execution path that withholds the credential or signing action until authorization when you need enforcement at that boundary. Keep card numbers, passwords, and verification codes in the supported secure flow. An approval or issued credential is not a receipt. Confirm the merchant’s order result, and track authorization, order confirmation, and settlement separately. The individual integration guides explain their evidence and recovery behavior.

​
Integration guides