SuggestAPI

SuggestAPI exposes commerce tools through MCP and WebMCP on its Agent Gateway

Documentation

Log inSign up

PrivacyTermsOnline Status

Search the site

Search SuggestAPI

Press Enter for the full results page. Shortcut: ⌘K / Ctrl+K.

The discovery layer

Turn shopping intent into products, wherever people start.

Add intent, context, and agent-ready discovery to the search you already run. SuggestAPI understands the full shopping job, then guides retrieval, comparison, recommendations, and checkout handoff—without replacing your catalog, search engine, or checkout.

Works with the search you already run

Algolia · Typesense · Elasticsearch · Meilisearch · Shopify

Start BuildingSee how it works

Shoppers · Apps · AI agents

01

Discovery signal active

What changes

Make the search you already have understand what shoppers mean.

Your search engine still finds products. SuggestAPI turns a messy shopping request into the constraints, context, and next steps that make those results useful.

The same shopper request, “Hiking boots for Iceland in October under $250,” fails as a keyword string in existing search and succeeds when SuggestAPI reads it as a shopping job and passes structured intent to the search engine already in place.

Shopper request

“Hiking boots for Iceland in October under $250”

Without SuggestAPI

Existing search box

Hiking boots for Iceland in October under $250

Search sees a string

Literal / keyword match

→ no result, or loosely relevant results

  • Receives the full request as one text string
  • Often treats it like disconnected keywords
  • Can return zero or loosely relevant results
  • Loses context when the shopper refines

Shopper has to start over

With SuggestAPI

SuggestAPI + your existing search

Hiking boots for Iceland in October under $250

SuggestAPI sees the shopping job

Intent understood

  • → Iceland
  • → October
  • → Under $250
  • → Waterproof
  • → Hiking boots
  • Reads the same request as a shopping job
  • Extracts constraints: destination, time, budget, category, features
  • Sends structured filters and ranking context to the existing search engine
  • Carries intent into refine, compare, recommend, and checkout handoff

Existing Algolia, Shopify, Elasticsearch, and the rest return ranked matching products.

Existing search receives usable intent

What SuggestAPI adds

  1. 01

Understand the request

Extract use case, budget, timing, preferences, and constraints from natural language. 2. 02

Guide your existing search

Rewrite, route, filter, and rank requests for the engine already underneath. 3. 03

Keep context across the journey

Preserve the shopping job when someone refines, compares, or asks a follow-up. 4. 04

Return discovery-ready results

Give shoppers and agents products they can compare, recommend, and hand off to checkout.

Why we built this

You shouldn’t need a new discovery layer for every assistant.

People shop with messy, persistent intent. Existing search drops that context after one query. Merchants shouldn’t have to rebuild discovery for every new assistant just to keep the shopper moving.

Shoppers, apps, and agents reach SuggestAPI first. SuggestAPI understands the job and keeps that context. Your existing search finds and ranks products. Your existing checkout completes the purchase.

Shoppers, apps, and AI agents reach SuggestAPI, which understands intent, keeps context, and structures the journey. Your existing search finds and ranks products from your catalog. Your existing checkout completes the purchase.

Who starts

Shoppers · Apps · AI agents

↓

SuggestAPI

Understands intent · keeps context · structures the journey

↓

Your existing search

Finds and ranks products from your catalog

↓

Your existing checkout

IntentRetrieveCompareRecommendHandoff

One layer for the shopping journey

Keep the intent through the whole path to purchase.

Intent and constraint extraction, search acceleration, and agent discovery sit in front of the engine you already chose, so a new shopping assistant doesn’t mean a new search stack, and a follow-up question doesn’t mean starting over.

01 / Understand

Intent & Constraint Extraction

Extract use case, budget, timing, preferences, and constraints from natural language, then send structured filters and ranking context to the search engine you already run. No replatform.

Intent → Retrieve

Explore retrieval →

02 / Accelerate

Search Acceleration

Get the shopper to the right products fast: query rewriting, routing, caching, and delivery straight through your existing search stack.

Ask → Find

How it works →

03 / Agents

Agent Discovery

The same catalog, structured so AI assistants can search, compare, recommend, and hand off to checkout through MCP and WebMCP on the SuggestAPI Agent Gateway. Shoppers, apps, and agents share that catalog. The merchant keeps the cart, checkout, and customer relationship.

Compare → Handoff

See protocols →

Your search, catalog, and checkout stay where they are.

Read the full category story →

Same intent, ready for agents

Built for the agent that needs to finish the trip.

Agents don’t want a feature list. They need to keep the shopper’s job intact (search, compare, answer, and hand off to commerce) without changing the catalog underneath. The same request—hiking boots for Iceland in October under $250—arrives already interpreted, so the agent can compare and hand off without starting from a keyword string.

{id · title · price · size · in_stock}

Agent path

Intent → structure

For your stack

Keep the shopping journey on the stack you already run.

Keep Algolia, Typesense, Elasticsearch, Meilisearch, or Shopify. SuggestAPI sits in front so you capture shopping intent without replacing the search and checkout you already trust. If you don’t have an engine yet, start on a SuggestAPI index.

ShopifyCommerce platformAlgoliaSearch engineClaude CommerceCommerce agentCloudflare AI SearchAgent search

Also Typesense, Elasticsearch, Meilisearch. Adapter notes in Bring Your Own Search.

For your stack

Built for the agentic web.

Meet shoppers where they already ask.

Intent that starts in ChatGPT, Gemini, a copilot, or a shopping agent still needs to land on your products. SuggestAPI is the discovery layer that makes that handoff possible.

Agents connect over MCP and WebMCP at the SuggestAPI Agent Gateway (agent.suggestapi.com): four commerce tools (search, recommend, compare, and product lookup) plus a WebMCP manifest for browser-oriented agents.

ARDUCPACPMCPA2APAPWebMCPAgent Skills

See supported protocols →

Shopping intent that starts in ChatGPT, Gemini, copilots, or shopping agents still lands on your catalog through SuggestAPI Agent Discovery.

Your catalog

Discovery

SuggestAPI Agent Discovery

Agent-ready

ChatGPT · Gemini · copilots
shopping agents · custom agents

Intent first

Hold the shopping job, not just the query

Zero

Search migration

One API

Every backend you already run

One journey

Shoppers, apps, and agents

Capture demand your search is losing.

Add a discovery layer without replacing the stack you have.

Connect the search you already run, or start on a SuggestAPI index. Hold shopping intent from the first ask through purchase, for people and agents.

Sign upBook a demo

{"@context":"https://schema.org","@type":"Organization","name":"SuggestAPI","url":"https://www.suggestapi.com","logo":"https://www.suggestapi.com/suggestapi-logo.png","sameAs":["https://x.com/suggestapi","https://www.linkedin.com/company/suggestapi","https://medium.com/@suggestapi","https://github.com/suggestapi","https://www.facebook.com/suggestapi"]}
{"@context":"https://schema.org","@type":"WebSite","name":"SuggestAPI - The Discovery Layer","url":"https://www.suggestapi.com","description":"SuggestAPI is the discovery layer that turns shopping intent into products for shoppers, apps, and agents. Keep the search you already run, or start on a SuggestAPI index. No replatform.","publisher":{"@type":"Organization","name":"SuggestAPI"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://www.suggestapi.com/search/?q={search_term_string}"},"query-input":"required name=search_term_string"}}