Dress Data Extractor
checking…
API docs

Extract

Upload one photograph of one garment. Everything you see here is what your application receives from POST /v1/dress/analyze.

Photograph

Worn, on a hanger, on a mannequin or flat-lay — all work.

Drop an image, or click to choose

JPEG, PNG, WEBP or HEIC. Up to 40 MB.

Result

Auto accept
Needs review
Not visible
Overall

Connection

The key your application will use. Kept in this tab only.

Remembered in this browser, so you enter it once. Clear it by emptying this field. The admin token on the API Keys tab is deliberately not remembered — it mints keys.

Model lane

A cold worker loads its weights before answering.

Processing queue

Records a person has been through. This is what an accuracy run is measured against — a record carrying corrections is the more valuable kind, because it records what the model got wrong on an image that still exists.

Image Library

Every image put through the extractor. Pick the ones worth keeping and add them to the golden set.

Image analysis

What the photograph is, and what it says about itself. Facts about the file and the capture — never about the garment.

Dress analysis

What garment this is, and how it is built. Domain narrows Category narrows Type, and the Type decides which attributes apply at all.

Design analysis

How it looks rather than what it is — colour, pattern, surface, embellishment and material.

Final results

Every field on one page, with the review controls. This is what an application receives.

API Keys

Issue a key for an application, then paste it into that application's settings.

Existing keys

Only a SHA-256 digest is stored, so a key can never be shown twice.

Enter the admin token to manage keys.

Admin token

Guards issuing and revoking. Separate from the keys it manages.

A leaked API key burns someone's quota. A leaked admin token mints unlimited keys — which is why they are different credentials.

Issue a key

Give it the narrowest permissions the application needs.

Two limits because they defend different things: the rate limit protects latency, the daily quota protects the bill. 0 = unlimited.