Commerce API & MCP

Build commerce intelligence into any product.

Search market-wide product data and compare current prices through Commerce API v1. Connect agents separately to the four focused Commerce MCP tools.

Create a developer project →

curl -X POST "https://api.nesika.ai/api/v1/commerce/search-products" \
  -H "X-API-Key: $NESIKA_API_KEY" \
  -H "Idempotency-Key: 8f14e45f-2d3b-4f1c-9a71-8f2c6f2b9c31" \
  -H "Content-Type: application/json" \
  -d '{ "market": "AU", "query": "iPhone 16" }'

Four Commerce operations

Search, resolve, find offers, and go deep when you need to.

Every Commerce API and Commerce MCP integration is built from the same four operations. Use them independently or as a flow.

Search products

Find products across the market using product queries.

Resolve product

Match a product to an exact identifier -- a GTIN or a merchant-scoped product ID -- and return alternatives when no exact match is confirmed.

Find offers

Retrieve current retailer offers for a product.

Deep search

Run a focused, reason-derived query for a specific missing fact, using the same default work budget as retrieving offers directly -- no extra AI reasoning, just a more targeted search.

Commerce API quick start

Every canonical Commerce REST example uses a Developer Project API key from NESIKA_API_KEY, the established X-API-Key header, and the v1 API path.

// Search commerce data with a Developer Project REST API key
fetch('https://api.nesika.ai/api/v1/commerce/search-products', {
  method: 'POST',
  headers: {
    'X-API-Key': process.env.NESIKA_API_KEY,
    'Idempotency-Key': crypto.randomUUID(),
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
  "market": "AU",
  "query": "iPhone 16"
}),
})
  .then(res => res.json())
  .then(data => console.log(data));

Commerce REST docs

Explore the versioned Commerce API

Commerce endpoints use the established https://api.nesika.ai/api/v1 base path. Generated schemas and examples remain aligned with the live v1 contract and return market-wide Commerce data.

Open interactive API reference OpenAPI spec (JSON)

Developer Project REST API key

From the selected Developer Project, create a key with credential_kind=api_key, then send X-API-Key: $NESIKA_API_KEY for Commerce REST requests.

Commerce quickstart

Commerce coverage

Search products
Resolve product
Find offers
Deep search