SuggestAPI · Agentic Resource Discovery
The Discovery Layer for AI Agents.
SuggestAPI implementsGoogle’s Agentic Resource Discoveryspecification — publishing a live capability catalog so agents can find commerce search, comparison, and checkout handoff without hardcoded tools.
Agent Search Layer
Publish once at /.well-known/ai-catalog.json. Agents and registries discover SuggestAPI commerce capabilities through an open standard.
Discovery, not execution
Google announcedAgentic Resource Discovery (ARD)as an open specification for publishing, discovering, and verifying AI capabilities across the web. It helps an agent answer what exists and where to find it — then the selected API or protocol handles runtime auth and interaction. Read theGoogle Developers Blog announcementor theARD specification(v0.9 draft).
Without ARD
- Developers hardcode tool descriptions into each agent
- Agents are limited to tools configured in advance
- Every platform invents its own discovery metadata
With ARD
- Providers publish capabilities in a common catalog format
- Registries can index capabilities for dynamic discovery
- Catalogs can include domain-anchored identity and trust metadata
What SuggestAPI publishes
The Knowledge Gateway hosts an ARD-compatible catalog with domain-anchored host identity and structured entries for each resource surface.
Live catalog
https://agent.suggestapi.com/.well-known/ai-catalog.jsonInspect the machine-readable ai-catalog.json, or read theARD specification(v0.9 draft).
SuggestAPI Agent Registry
Discover commerce search, comparison, recommendation, and handoff capabilities.
Tenant Search Surface
Tenant-scoped product and content search through a documented API surface.
Agent Search Orchestration
Higher-level retrieval, comparison, recommendation, and policy-aware answers.
Agent Cart Handoff
A safe handoff plan with merchant-controlled product, cart, and checkout resources.
Guided Checkout Handoff
Guidance that routes a selected product toward the merchant’s existing checkout.
How agents discover SuggestAPI
An Agent Search Layer that connects intent to live catalog capabilities — without coupling the agent to a specific search engine.
Step 1
Publish
SuggestAPI exposes its ARD catalog from the standard well-known path on the Knowledge Gateway.
Step 2
Discover
An agent fetches the catalog directly, or finds entries through an ARD registry that crawls published catalogs.
Step 3
Select
Descriptions, capability labels, and representative queries help match the user’s intent to the right surface.
Step 4
Connect
The agent uses the resource’s native API or protocol. SuggestAPI routes to the tenant search source and returns structured results.
Merchant control stays intact
Making a capability discoverable does not hand checkout to an agent. SuggestAPI’s cart and checkout resources are handoff surfaces — they prepare links, they do not place orders or process payments.
Keep your search stack
Algolia, Typesense, Elasticsearch, Meilisearch, or a SuggestAPI index stays the source of truth. SeeBring Your Own Search.
Structured product data
Assistants search, compare, and recommend from live catalog information — not brittle HTML scrapes or stale model knowledge.
Checkout stays yours
Product discovery becomes agent-ready while your storefront and commerce platform control cart, checkout, and payment.
ARD FAQ
Short answers for teams evaluating agent discovery standards.
Is ARD a runtime protocol?
No. ARD is a discovery specification. It does not replace OpenAPI, MCP, A2A, or another runtime. Authentication and execution stay with the selected resource.
Do merchants publish their own ai-catalog.json?
Not necessarily. SuggestAPI publishes platform capabilities from the Knowledge Gateway. Merchants can optionally publish a first-party catalog on their own domain.
Is the specification finalized?
Not yet. The current ARD specification is version 0.9 and labeled as a draft. Expect schema evolution as the open project matures.
Where can I read more?
See theannouncement blog post,Google’s ARD announcement, and thehow it worksoverview.
How It Works
Agentic commerce without a replatform
Connect your catalog and keep the search engine you already run.
Bring Your Own Search
Adapters, schema, and trust boundaries
Engineering reference for routing Algolia, Typesense, Elastic, or Meilisearch.
Blog
Full ARD announcement
Deep dive on the catalog, architecture fit, and merchant FAQ.
Ready to add agentic commerce to your storefront?
Join the waitlist to connect your catalog. SuggestAPI becomes The Discovery Layer for AI Agents — with an Agent Search Layer that publishes ARD-compatible capabilities while your checkout stays on your rails.