SuggestAPISuggestAPI

Search · Product discovery · Agents

Supported protocols.

SuggestAPI exposes the same search and product-discovery jobs — find, look up, compare, recommend — over the protocols agents and storefronts already speak. This page is the human map of those surfaces.

Last updated:

Two hosts, one discovery job

Shoppers hit the search acceleration API. Agents hit the Knowledge Gateway. Both sit in front of the search engine you already run — Algolia, Typesense, Elastic, or Meilisearch — and return structured catalog results instead of scraped HTML.

HostAudienceWhat it is forStart here
api.suggestapi.comStorefronts, apps, ingestionAutocomplete, typeahead, indexes, merchandising, and catalog APIsopenapi.json
agent.suggestapi.comAgents, plugins, registriesTenant search, product lookup, compare, recommend, and protocol discoveryokg.json

The gateway service index is https://agent.suggestapi.com. Human protocol notes live in AGENTS.md.

Shared product-discovery skills

A2A and MCP expose the same four commerce tools. Each tool is a thin protocol wrapper over a Knowledge Gateway REST call. Tenant is the merchant domain (for example demo.suggestapi.com).

Skill / toolRequired paramsOptionalBackend
searchtenant, queryretrieval_mode (typeahead, autocomplete, search, hybrid), limitPOST /v1/agent/search
recommendtenant, queryPOST /v1/agent/recommend
comparetenant, ids (≥2)POST /v1/agent/compare
product_lookuptenant, idGET /v1/agent/product/{id}

Knowledge Gateway protocol endpoints

Host agent.suggestapi.com. Discovery documents live under /.well-known/. Runtime JSON-RPC lives at /a2a and /mcp. UCP and ACP are REST commerce contracts on the same host.

ProtocolMethodPathWhat it is
A2AGET/.well-known/agent-card.jsonAgent Card (protocol 0.2.0, four skills)
A2APOST/a2aJSON-RPC: agent/card, message/send, tasks/get, tasks/cancel
AIDGET/.well-known/agentAID fallback document (aid2, proto a2a)
AIDGET/.well-known/aiAID agent index (agents[] with suggestapi)
DNS-AIDGET/.well-known/dns-aid.jsonIndex of A2A + MCP agents; A2A capSha256 is base64url of the card
MCPPOST/mcpStreamable-HTTP JSON-RPC (protocol 2025-06-18)
WebMCPGET/.well-known/webmcpTool manifest plus REST endpoints for each commerce tool
MCPGET/.well-known/mcp-manifest.jsonMCP tool/manifest alias
MCPGET/.well-known/mcp-serverWell-known MCP server document (draft-serra style)
MCPGET/.well-known/mcp/server.jsonMCP Registry server schema (streamable-http remote)
MCPGET/.well-known/api-catalogRFC 9727 linkset to WebMCP + MCP
UCPGET/.well-known/ucpUniversal Commerce Protocol profile; catalog search is tenant-scoped
ACPGET/.well-known/acpAgent Commerce Protocol profile; feed and checkout sessions are tenant-scoped

Live copies: Agent Card,/a2a,/mcp,WebMCP,AID,AID index,DNS-AID,api-catalog,UCP,ACP.

A2A and MCP runtimes

A2A is Agent-to-Agent: fetch the card, then send a message that names a skill. Tasks are stored for about 30 minutes so a client can poll or cancel. MCP is Model Context Protocol over streamable HTTP: handshake, list tools, call a tool. Both dispatch to the same gateway skills.

A2A JSON-RPC

MethodRole
agent/cardReturn the Agent Card
message/sendRun a skill; store task ~30 min
tasks/getFetch a stored task
tasks/cancelMark a stored task canceled

MCP JSON-RPC

MethodRole
initializeHandshake + protocol version
notifications/initializedAck client ready
pingLiveness
tools/listFour commerce tools
tools/callDispatch via gateway skills
resources/list, prompts/listEmpty lists (supported, unused)

MCP registry metadata is also at /.well-known/mcp.json.

What each protocol is for

Discovery protocols tell an agent what exists. Runtime protocols let it search the catalog. SuggestAPI publishes both so you are not locked into one agent stack.

ProtocolJobSearch / product discovery role
A2ARuntimeAnother agent calls SuggestAPI as a commerce specialist: search, lookup, compare, recommend.
MCPRuntimeCoding and shopping assistants attach /mcp and get the four catalog tools. See the MCP and WebMCP notes.
WebMCPDiscovery + RESTBrowser and site agents read a tool list that also names the REST URLs behind each tool. See the MCP and WebMCP notes.
AID / DNS-AIDDiscoveryFind the A2A (and MCP) agent on this host without hardcoding paths. DNS-AID includes a hash of the Agent Card.
ARDDiscoveryGoogle Agentic Resource Discovery catalog of commerce capabilities. Does not execute search itself. See ARD.
UCPRuntime (REST)Universal Commerce Protocol catalog search, tenant-scoped. See /.well-known/ucp.
ACPRuntime (REST)Agent Commerce Protocol product feed and checkout-session handoff, tenant-scoped. Sessions stay not_ready_for_payment; SuggestAPI does not capture payment. See /.well-known/acp.
OKF / OKSKnowledge + plugin searchPortable knowledge plus /oks/{tenant}/search for shops that keep their existing catalog. See OKF.
HTTP QUERYRuntime (HTTP)RFC 10008 safe, idempotent search bodies on autocomplete, typeahead, and agent search. See the QUERY notes.
REST + OpenAPIRuntimeDirect HTTP for apps that do not speak A2A or MCP. Gateway: openapi.yaml. API: openapi.json.
Agent SkillsCoding-agent playbooksSKILL.md folders that teach Claude, Codex, Antigravity, Cursor, and similar clients how to call api.suggestapi.com. Install suggestapi/skills with npx skills add suggestapi/skills. Domain index: /.well-known/agent-skills/index.json.

Knowledge Gateway REST (search and catalog)

Use these when you want JSON over HTTP without JSON-RPC. Tenant plugin search is the adoption path for existing shops.

MethodPathPurpose
POST / QUERY/v1/agent/searchTask-oriented search across a tenant knowledge surface
GET/v1/agent/product/{id}Canonical product lookup
POST/v1/agent/compareCompare products by id
POST/v1/agent/recommendRecommendations from query + context
GET / QUERY/oks/{tenant}/searchPlugin-style search (q, mode)
POST/oks/{tenant}/catalog/searchUCP catalog search for that merchant
GET/oks/{tenant}/feeds/default/productsACP product feed for that merchant
POST/oks/{tenant}/checkout_sessionsACP checkout session (handoff only; payment complete is not offered)
GET/.well-known/ai-catalog.jsonARD capability catalog

Handoff helpers (/v1/agent/cart, checkout guide) exist for merchant-controlled checkout. They are not a payment API. Capability overview: Agent Discovery docs.

Search acceleration API

https://api.suggestapi.com is the HTTP API for storefront typeahead, autocomplete, indexes, ingestion, and graph-style recommendations. It is not the A2A/MCP host — agents that need tenant commerce tools should use the Knowledge Gateway.

MethodPathPurpose
GET / QUERY/v1/autocompleteIntent-ranked suggestions for the search bar
GET / QUERY/v1/typeaheadFast prefix typeahead from a precomputed table
GET / POST/v1/indexes…Create, ingest, merchandising, schema, export
GET / POST/v1/graph/recommendations…Structural, series, application, and spec recommendations
GET/healthLiveness
GET/openapi.jsonFull machine-readable contract

Coding agents that should implement against this API: install suggestapi/skills (npx skills add suggestapi/skills). Engineering adapters and response schema: Bring Your Own Search. Query routing: Retrieval abstraction.

Which protocol should I use?

If you are…Use
Wiring a storefront search barGET https://api.suggestapi.com/v1/autocomplete or typeahead
Building an MCP client (Cursor, Claude, custom)POST https://agent.suggestapi.com/mcp
A coding agent (Claude, Codex, Antigravity, Cursor) implementing against the Search APInpx skills add suggestapi/skillshttps://api.suggestapi.com
Calling from another A2A agentFetch the Agent Card, then POST https://agent.suggestapi.com/a2a
Indexing capabilities without a hardcoded tool listARD ai-catalog.json, AID, or DNS-AID
Implementing UCP shopping catalog searchPOST /oks/{tenant}/catalog/search
Implementing ACP catalog feed and checkout handoffGET /oks/{tenant}/.well-known/acp, then the tenant feed and checkout sessions. Complete stays on the merchant storefront.
Keeping the merchant site as the source of truthOKS plugin search /oks/{tenant}/search