Contract-first
A feature card appears only when the route-manifest lists a matching launch path.
← All features
Feature · Discovery
Search and discovery without open-ended crawl claims.
Keyword, category, and suggestion endpoints where the product contract includes them — always with a stated result bound.
What this unlocks
Capability outcomes, not availability claims.
Discovery routes help buyers find candidates; they do not grant a full-platform dump. Absent search support on a family is omitted rather than faked.
Freshness honesty
Trend and suggestion surfaces describe present-tense catalog state, not guaranteed history.
Vendor-neutral payloads
Buyer responses never name upstream suppliers.
Evidence-gated surface
Launch routes that back this feature.
Paths below are taken from each product's committed route manifest. Catalog status still decides whether buyers may call them.
Facebook Master StackVerification pending
/api/facebook/commerce/search/api/facebook/commerce/search-page
TikTok IntelligenceVerification pending
/api/tiktok/profile-search/api/tiktok/posts-by-keyword
Twitch IntelligenceVerification pending
/api/twitch/search/api/twitch/search-live
Pinterest IntelligenceVerification pending
/api/pinterest/posts-by-keyword/api/pinterest/search-pins
Bluesky Engagement & SignalsVerification pending
/api/bluesky/search-actors/api/bluesky/actors-typeahead
Real Estate Master StackNot available
/api/realestate/property-search/api/realestate/search-page
Endpoint presence is not a public-availability claim. Review the canonical catalog before integrating.