Try the Mercari master API

- This is a large response — tens of thousands of brand entries. It is effectively static day to day; the endpoint is served with a 24-hour edge cache, so repeated calls do not re-fetch from Mercari each time. - `categories` is a flat list with `parent_id` linkage rather than a nested tree, matching the shape Mercari's own data uses. `parent_id` is omitted (zero) for a top-level category (e.g. "Women", "Men", "Home"); `icon_url` is only populated for top-level categories. - `sizes` is one flat list spanning all size-bearing categories — it is not scoped per-category. `short_name` and `code` are the two parts a size's `name` is composed from when both are present (e.g. name `"XS (0-2)"` = short_name `"XS"` + code `"(0-2)"`); either may be absent when Mercari's own data doesn't split them out. Example response (truncated — the real response has ~3,000 categories, ~28,000 brands, and ~380 sizes): ```json { "code": 200, "msg": "OK", "data": { "categories": [ { "id": 1, "name": "Women", "icon_url": "https://u-mercari-images.mercdn.net/assets/img/home_categories/1.png" }, { "id": 11, "name": "Dresses", "parent_id": 1 } ], "brands": [ { "id": 1, "name": "104+ Octane Boost" }, { "id": 4, "name": "3.1 Phillip Lim" } ], "sizes": [ { "id": 1, "name": "XXS (00)", "short_name": "XXS", "code": "(00)" }, { "id": 2, "name": "XS (0-2)", "short_name": "XS", "code": "(0-2)" } ] } } ```