Velox TriFit / DressMe / Developer tutorial

From first look
to your own app.

Build clothing virtual try-on into a web or mobile experience, with your backend in control.

DressMe accepts a shopper photo and a clothing reference to create an AI outfit preview. TriFit is Velox's consumer app; Partner API credentials are issued separately. AI previews are not measurements or guarantees of fit.

1. Explore the working example

Open the hosted demo and its developer dashboard & SDK download. Viewing these pages does not submit a try-on. Real generation requires an explicit submission, consent and available demo allowance.

The public dashboard shows your browser session's requests and public source downloads, not Velox's operator admin. The demo key remains on Velox's server. Your own private partner dashboard and configuration are supplied after approval.

2. Run the preview without an API key

Install Node.js 22 or later and Git, then use a new local folder:

git clone https://github.com/Velox-XR/trifit-partner-api-example.git
cd trifit-partner-api-example
npm run preview

Open the local URL printed by the server. Preview mode does not upload images or generate results. The optional npm run demo:mock and npm run demo:failure commands use artificial local responses. They are not real AI output or performance evidence.

Read Getting started, the technical walkthrough and the SDK catalogue. Source and hosted deployments can have different release versions.

3. Request your own partner configuration

Apply for Partner API access with your use case, platform and expected usage. After review, Velox supplies an environment-specific integration identity, private API key and configuration. A free TriFit account or MCP connection is not a partner credential.

The example's checked-in key is deliberately invalid. Place only your own supplied partner.config.json beside package.json; keep it out of source control. npm start starts the configured backend and checks its assigned identity and environment. Unlike preview, this enables real API use, which can incur charges when you submit requests.

4. Connect the secure backend

The shipped SDK is JavaScript with TypeScript declarations, available as public source. See its method reference; do not assume a public npm package or an unlisted SDK exists.

Verify your assigned API identity and environment before processing user media.
Derive each shopper's opaque subject from your authenticated server session, never a client-selected identity.
Upload a catalogue product through Partner API and persist the final asset ID. Reuse it within the same permitted catalogue and environment.
Obtain the shopper's permission, upload their photo and persist the upload receipts.
Before submission, durably save the exact input asset IDs and one idempotency key. Save the accepted job ID.
Use the documented signed webhook flow when configured, or read job status. Display a result only to the authorized shopper.
Reconcile uncertain submissions using saved receipts. Do not create a second job or new idempotency key merely because a response timed out.

Your app → your authenticated backend → Velox Partner API. Temporary storage URLs receive only their specified upload headers, never the Partner API credential. Keep private media and signed URLs out of logs.

5. Build for Swift, C# or your web framework

A coding agent can generate application code from the documented HTTP contract. There is no separate official Swift or C# SDK in the current public catalogue. Mobile apps should call your own authenticated backend; that backend holds the Velox key and enforces consent, authorization and spending controls.

Connect the public developer MCP server, then adapt this prompt:

Build a mobile virtual try-on integration using Velox TriFit / DressMe. Ask which platform I need: Swift/SwiftUI or C#/.NET. Read the official API walkthrough and SDK source first. Create the mobile UI and a separate authenticated backend; keep the Velox application key on the backend. Include photo consent, upload receipts, job status, cancellation of local waiting, uncertain-response recovery and privacy-aware error messages. Do not promise that cancelling local waiting cancels an accepted job. Use mocks for tests. Do not upload, generate, provision credentials, deploy or change quotas without my explicit instruction. Cite the exact API contracts used and label generated native code as an example, not a released Velox SDK.

Before enabling real requests

Confirm the assigned environment, usage allowance, concurrency, enabled features and commercial terms. The shared demo's limits are not a universal partner policy.
Agree privacy, retention, deletion and support requirements for your integration. A session-cookie expiry is not a media-deletion promise.
Test authorization, receipts, idempotency, webhook verification and uncertain responses using offline fixtures first.
Obtain explicit approval for live evaluation. Development API calls can also incur charges; a mock is not Production acceptance.

Discuss your integration ↗