For · Meilisearch
Search engine
Keep Meilisearch, and put a discovery layer in front.
Your Meilisearch index already holds the catalog and ranking. SuggestAPI routes storefront and agent requests to that index and returns a consistent, agent-ready result shape.
Client
Storefront or agent
Adapter
SuggestAPI
Engine
Meilisearch
Results
Ranked products
Meilisearch
Meilisearch stays the engine
Indexes, documents, and ranking stay in Meilisearch. SuggestAPI does not migrate you off Meilisearch.
Discovery layer
SuggestAPI is the adapter
One API for autocomplete, full search, compare, and recommend. SuggestAPI rewrites the shopping job, calls Meilisearch, and normalizes the response for people and agents.
SuggestAPI is an independent layer in front of Meilisearch. It is not a Meilisearch product.
What stays
Leave the stack you already trust in place
The index
Documents and ranking settings stay in Meilisearch.
Credentials
Meilisearch keys stay on the server. Clients call SuggestAPI.
Your instance
SuggestAPI calls the Meilisearch you already operate.
What SuggestAPI adds
Add discovery without a second catalog
Query understanding
Shopping jobs and follow-ups, not only prefix strings.
Agent-ready results
Structured product context for compare, recommend, and handoff.
Swap later if you need to
The client stays on SuggestAPI if the backend changes.
Start with the stack you have
Keep Meilisearch and add discovery
Sign up, connect the catalog or search you already run, and put SuggestAPI in front.
Also for