Skip to content

Commerce MCP

Aiptimise Commerce MCP

Live, merchant-approved product data for AI shopping assistants: search products, check prices and stock, and read store policies, over the Model Context Protocol.

What it does#

AI assistants use this service to answer shoppers' questions about participating merchants: find products that fit a need and budget, check a variant's current price and availability, read product details, reviews and Q&A, list running promotions, and read store policies and loyalty-program terms.

Every tool is read-only. The service does not place orders, take payments or access shopper accounts. Product links go to the merchant's own website, where purchases are completed. Products in restricted categories (for example alcohol and tobacco) are never served.

Tools: search_products, get_store_info, get_live_price_and_inventory, get_active_promotions, get_loyalty_program, get_aiptimise_product_data, get_product_variants.

Endpoints#

MCP streamable HTTP, stateless, JSON responses.
WhoEndpointAuthentication
ChatGPThttps://app.aiptimise.com/api/mcp/p/openaiNone. Install the Aiptimise app from the ChatGPT app directory, or add the URL as a connector in developer mode.
Claudehttps://app.aiptimise.com/api/mcp/p/anthropicNone. Add Aiptimise from the Claude connectors directory, or add the URL as a custom connector.
Platforms and partnershttps://app.aiptimise.com/api/mcpAn API key from the developer console, sent as a bearer token.
POST https://app.aiptimise.com/api/mcp
Authorization: Bearer aip_live_…

Anonymous calls get availability (in stock or not), never exact inventory counts. Sign-in with OAuth 2.1 is optional and only for developer accounts; see Authentication and access. Every response carries an X-Request-Id header; quote it when you contact support.

Documentation#

  • Getting started: From a partner account to a sandbox key, your first call and production access.
  • Demo store: The fictional store every consumer can read, and the answers to expect from it.
  • Authentication and access: Directory endpoints, API keys, optional OAuth 2.1 sign-in and scopes.
  • Calling the server: Transport, raw JSON-RPC with curl, and client setup snippets.
  • Tools reference: Every tool: scope, parameters, output fields and a real example.
  • Limits and errors: Rate limits, HTTP and tool errors, and how fresh prices are.
  • Integrator obligations: What the data-use terms require of you, in short.
  • Changelog: Server versions and where changes are announced.

Data and privacy#

For each request the service records the connecting platform, the tool, the store and products returned, the outcome and timing, and the locale and country the platform reports. The platform's anonymized session identifier and, for anonymous calls, the IP address are stored only as keyed one-way hashes. Shoppers' prompts, conversations, tool arguments and responses are never logged. The one exception: where a platform partner has enabled demand analytics, product search terms are kept with email addresses, phone numbers and long numbers removed.

Retention: request records are deleted after 90 days, and search terms (where enabled) after 90 days. Daily aggregated counts, without session or IP hashes, are kept while the service operates. Product request events (which products were returned, by platform and country) give merchants analytics about their own catalog and are kept while the merchant's account is active; they are deleted when the account is deleted.

Details: privacy policy (section “AI Shopping Assistants”), terms of service, and the developer data-use terms.

For merchants#

Stores take part while AI Discovery is enabled. In Aiptimise, Settings → AI Agents shows which AI platforms can read each store and lets you block any of them; turning AI Discovery off withdraws the store from all of them. Monitoring → AI Agent Activity shows what assistants requested.

Support#

support@aiptimise.com for help and to report a problem, including security issues. Privacy requests: privacy@aiptimise.com.