SuggestAPISuggestAPI

For · Elasticsearch

Search engine

Keep Elasticsearch, and put a discovery layer in front.

Your Elasticsearch 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, then Adapter: SuggestAPI, then Engine: Elasticsearch, then Results: Ranked products

Client

Storefront or agent

Adapter

SuggestAPI

Engine

Elasticsearch

Results

Ranked products

Elasticsearch

Elasticsearch stays the engine

Indexes, mappings, and ranking stay in Elasticsearch. SuggestAPI does not migrate you off Elastic.

Discovery layer

SuggestAPI is the adapter

One API for autocomplete, full search, compare, and recommend. SuggestAPI rewrites the shopping job, calls Elasticsearch, and normalizes the response for people and agents.

SuggestAPI is an independent layer in front of Elasticsearch. It is not an Elastic product.

What stays

Leave the stack you already trust in place

  • The index

    Documents, mappings, and ranking stay in Elasticsearch.

  • Credentials

    Elasticsearch credentials stay on the server. Clients call SuggestAPI.

  • Your cluster

    SuggestAPI calls the Elasticsearch you already operate.

What SuggestAPI adds

Add discovery without a second catalog

  • Query understanding

    Shopping jobs and follow-ups, not only query 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 Elasticsearch and add discovery

Sign up, connect the catalog or search you already run, and put SuggestAPI in front.

Also for