Choose a starting point
- Build an A–Z list with the complete brand directory.
- Find a brand from a description, reference brands, or filters with Brand Search.
- Complete part of a name with prefix search.
- Find alternatives with similar brands.
totalFound and ranked results. Each result includes brandUuid, brandName, brandSlug, domain, brandDescription, and directorySubheading. Optional metadata can be null. Use the returned slug, or the canonical name when the slug is null, as the identifier for the next request.
Render a brand page
Read the lightweight profile for public metadata, typed article cards, and navigation facets. Use the returned canonical identity for your page URL. Keep article dates at their actual precision, such asMay 2026.
Build navigation with the normalized gender, age_groups, and category_path.depth_* facets. Labels and combinations belong to your application. The top-categories endpoint also provides precomputed category metadata. Both describe the brand’s recorded assortment across the corpus; neither promises live products in your customer’s scope.
Request the separate coverage snapshot when you need approximate product counts, carrying catalogs, facet coverage, or price distributions. Render the profile even if that request fails.
Browse products
Use brand product browsing for a consistent UUID-ordered grid. Follow the returnednextOffset until it is null, including when the projected products list is empty. Offset 11976 is the last supported start, equivalent to page 500 at 24 rows per page. Use Product Search for text, additional filters, and relevance ranking.
Directory, profile, navigation, top categories, and coverage are corpus-wide metadata. Product rows and browse source totals respect your API key’s catalog scope. An explicit empty scope returns no products. A brand match, category, or approximate coverage count does not grant product access.
Handle missing data and failures
Every REST operation requires your Developer organization API key. Keep credentials on your server. The directory has a one-hour private cache and ETag revalidation. Coverage is an independently cached snapshot. Treat404 brand_not_found as a missing identity. Treat 503 as an operational failure, not an empty directory, absent articles, or a missing brand. Empty article and category lists are valid successful results. Validation failures return 422; missing or invalid credentials return 401; forbidden organizations return 403. The standard organization rate limit applies.
Brand filters and SDKs
Brand Search acceptsq, similar_to_brands, facets, exclude_facets, understand, and limit. Omit q for reference- or filter-only requests. Without text, query understanding is skipped. Explicit clauses are preserved and never relaxed. Set understand: false to use text as written.
Brand filters use {name, values} with names such as facet_price_tier, facet_origin_country, facet_styles, facet_genders, and facet_category_path.depth_0 through facet_category_path.depth_6. These differ from the Product Search names in profile navigation. Each inclusion or exclusion list supports up to 20 clauses, with 1–100 nonblank values per clause and 256 characters per value. Product-only filters and internal quality controls are rejected. The separate similarity operation retains brands, facets, and exclusionFacets.
Use the Python SDK, TypeScript SDK, or CLI for typed examples. The canonical operation names are listed on each reference page.
The StoreRouter MCP connection exposes search_brands, similar_brands, brand_prefix, get_brand, browse_brand_products, and get_brand_top_categories. get_brand returns the profile. Use REST or an SDK for the separate coverage snapshot. Developer callers omit org_id; internal super admins select an organization without expanding their own product scope.