Commerce MCP
Integrator obligations
What the data-use terms (version 2026-09-26) require of you, in short.
In short#
This summary is not the terms. The binding text is on the policies page, which you accept when you apply.
| You must | Policy |
|---|---|
| Send shoppers to the merchant with the product_url a tool returns, unchanged: it carries the UTM attribution for your visits. | Attribution requirements |
| Checkout happens on the merchant’s site. Do not take payment or run checkout for the merchant. | Attribution requirements |
| Honor merchant blocks: when a store stops being served to you, stop presenting its data. | Data-use terms |
| No resale or redistribution of the data, and no copies of catalogs, price histories or inventory. | Data-use terms |
| Present prices with their as_of time, and do not show a live offer after its valid_until. | Data-use terms |
| Keep API keys secret and server-side; rotate a key at once if it may have leaked. | Data-use terms |
All policies#
- Data-use terms: What you may do with merchant data served by the Aiptimise commerce MCP. Accepting these terms is required before any API key is issued.
- Attribution requirements: How shoppers must reach the merchant.
- Privacy: What the MCP records about requests.
- Service terms: Tiers, limits and availability.
When the terms change, new keys and key rotations are blocked until an owner of your consumer accepts the new version on the console Overview. Existing keys keep working.