Skip to content

Fashion AI™ · Data layer

Data & API

Fashion AI uses stable entity records, explicit provenance and reusable identifiers so the same evidence can support public intelligence, research and Private Client workflows. Enterprise API or data-delivery access is scoped separately and is not represented as a self-service public API.

Stable entity architecture

Markets, brands, designers, events, editions and index records use stable identifiers so research can point to a consistent entity even when the presentation layer changes.

/events/{event}                    /events/{event}/{edition}
/events/{event}/{edition}/record   /brands/{brand}
/designers/{designer}              /markets/{market}
/indices/{index}/{edition}

Provenance travels with the value

Every reusable output is designed to keep source state, observation period and method context beside the value. Licensed fields can be withheld from redistribution when a source agreement does not permit onward publication.

{
  "data": { "entity": "market:example", "score": null },
  "provenance": {
    "score": { "label": "MODELLED", "method": "/methodology/", "coverage": 0.00 }
  },
  "meta": { "assessed": false, "owned_property": false }
}

Enterprise access

Institutional engagements can scope structured exports, licensed datasets, additional organization users and future API or first-party-data integrations. Availability depends on the requested dataset, source licence and implementation requirements.