id and url you can drop into
Generation.
By text
Natural-language queries like
red summer dress. Ranked by relevance.By attributes
Exact filters — category, color, season, and more. Combine to narrow down.
By image
Pass a garment image URL to find visually similar items in your catalog.
Before you start
Search needs only your tenant key — send
x-api-key and nothing else. Unlike
Generation and User & Image, there’s
no Authorization: Bearer token: search runs against your catalog, not a
specific end-user. See the
authentication model.How relevance works
Text and image search return az_score on every garment — a relative
relevance metric, not an absolute one. It measures how far a garment stands out
above the average match for this specific query, in standard deviations.
- A
z_scoreof2.0means the garment is two standard deviations more relevant than the typical candidate for your query — a strong, standout match. - A
z_scorenear0means it’s only about as relevant as average — a weak match.
Attribute search is an exact filter, not a
relevance ranking — its results have no
z_score (the field is null).Pick a search mode
Search by text
POST /search/text-search — natural-language query, ranked by z_score.Search by attributes
POST /search/attribute-search — exact faceted filters across ten attributes.Search by image
POST /search/image-search — visual similarity to a reference image URL.Errors
These status codes apply to all three search endpoints.A successful search can legitimately return an empty
garments array — for
text and image search when nothing clears min_z_score, and for attribute search
when no garment matches every filter. Handle the empty case in your UI.Next steps
Try a garment on
Take a garment
url from any search result and pass it to
POST /try-on/generate to render it on your user.Review the full flow
See how authentication, search, and generation fit together end to end.