Generate a digitalTwinId once, then reuse it across many garment try-on jobs.
Reusable avatars for faster try-on
Digital Twin API
Create reusable customer avatars from a face photo paired with a body photo, silhouette, measurements, or clothing size.
Core endpointPOST /api/v1/virtual-fitting
OpenAPIhttps://api.wearfits.com/doc
Agent context/llms.txt and /llms-full.txt
POST /api/v1/digital-twin requires faceImage plus exactly one of bodyPhotoUrl, silhouetteImage, clothingSize, or bodyMeasurements.
Digital twin caching is designed for repeat sessions and lower per-try-on latency.
Machine-readable surfaces
Built for developers and AI agents
- /llms.txt concise AI context and link map
- /llms-full.txt expanded endpoint and integration context
- /docs/openapi-summary.md human and agent-readable API summary
- /widget/tryon.js lightweight API-backed modal without the hosted size-fitting overlay; for the complete UI use the hosted iframe (guide, demo)
Key Questions
How long are digital twins cached?
Digital twins are cached for 30 days by default.
Can users avoid full-body photos?
Yes. Pair faceImage with clothingSize or bodyMeasurements instead of a full-body photo. A face photo is still required. Size recommendations additionally require a supported stored body profile of sufficient quality.
How is a saved twin checked?
Call GET /api/v1/digital-twin/{id} to verify that a saved digitalTwinId is still valid.