Commerce API & MCP › API reference

Commerce REST API Reference

Build market-wide Commerce data workflows -- product discovery and pricing -- against the four canonical operations at https://api.nesika.ai/api/v1. Authenticate canonical examples with a Developer Project REST API key.

Get started

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 with a client-generated Idempotency-Key on every request.

Canonical v1 request

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" }'

The four Commerce operations

These are the only Commerce REST operations. Each has a matching Commerce MCP tool of the same name. Use generated OpenAPI documentation for complete request and response schemas.

POST https://api.nesika.ai/api/v1/commerce/search-products

search_products

Searches retailer product candidates through the Commerce engine.

POST https://api.nesika.ai/api/v1/commerce/resolve-product

resolve_product

Matches a supplied product to an exact identifier -- a GTIN or a merchant-scoped product ID -- and returns alternatives and ambiguity notes when no exact match is confirmed.

POST https://api.nesika.ai/api/v1/commerce/find-offers

find_offers

Finds retailer offers for a product identity.

POST https://api.nesika.ai/api/v1/commerce/deep-search

deep_search

Performs bounded deep product research when standard search is insufficient.

Need native tools instead of REST calls?

Commerce MCP is a separate public developer surface with four focused tools, its own endpoint, and a separate Commerce MCP credential. A REST API key cannot connect it.

View Commerce MCP
Logos provided by Logo.dev