Velox TriFit: Virtual Try-On API

io.github.Velox-XR由 GitHub 账号 Velox-XR 发布v2.0.1更新于 Oct 29, 2026

Virtual try-on (VTO) API docs and SDK examples; OAuth account/guest photo uploads and try-ons.

已验证Streamable HTTP可网页运行开发者工具媒体与设计

概览

AI 生成的概览

Velox TriFit 的远程 MCP 服务器,提供官方虚拟试穿 API 文档、SDK 示例,以及经同意的账户或访客照片试穿。

可以做什么
  • 搜索并阅读官方 DressMe 虚拟试穿 API 文档,附来源链接与校验和
  • 获取 JavaScript/Node.js 集成示例与 TypeScript 声明,以及合作伙伴接入与申请指引
  • 查看连接模式、个人资料及每日、每周、每月剩余额度
  • 列出账户库中已保存的照片、商品、造型与试穿请求
  • 生成一次性私有上传链接,导入用户选定的 JPEG、PNG 或 WebP 图片
  • 提交、轮询并展示试穿结果,或使用受限的访客演示会话
适用场景
适合在开发虚拟试穿集成时,让助手查阅准确的 API 约定和可运行示例;也适合在明确同意后,用自有 TriFit 账户或受限访客演示生成服装预览。
运行要求
远程 streamable HTTP 端点;公开文档工具无需本地安装包或 API 密钥。账户与访客试穿工具需 OAuth 连接与同意,账户方式还需 TriFit 登录(Google 或邮箱)。生成会消耗该连接自身的额度。
安装前请注意
该服务器并非只读:上传与试穿工具会把图片发送给 Velox 并消耗额度,失败的尝试也计入。结果是 AI 可视化效果,不保证尺码或合身。切勿泄露令牌或私有上传链接,请求状态不明时不要重试。连接本身不会获得 Partner API 凭证,正式 Partner API 使用可能产生费用。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Velox TriFit: Virtual Try-On API,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.Velox-XR%2Fvelox-trifit-developer/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "velox-trifit-virtual-try-on-api": {
      "type": "http",
      "url": "https://studio.v3lox.com/partner/trifit/mcp"
    }
  }
}

README

Velox TriFit — Virtual Try-On API, MCP Server and JavaScript SDK

Build virtual try-on (VTO) into a website, mobile app or retail platform with the Velox TriFit Partner API, or connect a coding agent to the Velox TriFit MCP server for official API guidance or a user-approved account/guest clothing preview. Use the hosted MCP connection and tool reference for the latter; authenticated client acceptance remains incomplete. DressMe is the virtual try-on operation: it turns a shopper photo and a garment image into an AI outfit preview. The TriFit app is the consumer experience; using it is separate from obtaining Partner API credentials.

This official developer repository contains the JavaScript SDK with TypeScript declarations, runnable REST integrations, tutorials, Codex, GitHub Copilot and Gemini CLI MCP configuration examples, and a portable integration skill. Read the API overview, then choose the integration route below. Other languages can use the documented HTTP API; this repository does not claim an unshipped SDK.

Virtual dressing and visual fitting rooms

Use DressMe for photo-based virtual dressing: a shopper photo and clothing reference produce an AI outfit preview. A virtual fitting room built with DressMe provides a visual preview, not body measurements, clothing-size prediction or a guarantee of physical fit. The REST quickstart explains the upload, job submission and status flow; the JavaScript SDK provides the integration code.

Choose REST API or MCP

Integration routeWhat it providesStart here
REST API in your application backendSubmit virtual try-on requests using your separately approved partner configuration; keep keys out of browsers and mobile appsREST quickstart · JavaScript SDK · Access requirements
MCP in a coding agentSearch official docs, fetch API contracts and get integration examples while building an applicationVirtual try on MCP: Codex, Copilot and Gemini setup · Public MCP guide
MCP for a personal clothing previewUse the connected TriFit account or limited guest session through normal OAuth and consent; generation uses that route's allowanceHosted endpoint, inputs and result tools · Verified release status
Portable integration skillReusable instructions for an agent to plan and implement the integration; it can also use the public source without MCPSkill source and installation

For a new direct MCP connection, use https://studio.v3lox.com/partner/trifit/mcp. Documentation-only work needs no TriFit sign-in or Partner API key: allow only search, fetch, get_integration_example and get_partner_access_requirements as described in the client guide. The server as a whole is not read-only. Its account/guest upload and try-on tools require separate OAuth authorization and user consent; they are not part of a documentation check. Connecting MCP or installing a skill does not grant Partner API credentials, generation allowance or deployment access.

The published OpenAI Developer plugin is a separate installation route. Its existing reviewed connection is managed separately; a new direct MCP setup or this README update does not migrate it.

Start here

Want to…Go here
Try without an accountHosted demo — free shared, limited queue
Try with your own saved photos, products and historyTriFit app — sign in/create an account and use its available free daily/weekly/monthly allowance
See your demo requests and download the SDK ZIPDemo dashboard & SDKs
Explore immediately on your computer, without credentialsDownload this repository; run npm run preview with Node.js 22+
Build a real integrationGetting started · Apply for access
Run real DressMe from code with my existing TriFit account, without a partner keyExample 2: account sign-in
Understand which access route to useAll DressMe options
Read the API flowTechnical walkthrough
Choose an SDKSDK catalogue
Use Codex or GitHub Copilot to build a web/mobile integrationMCP setup and mobile starter prompt · Portable integration skill
Use Gemini CLI or Google Antigravity for API guidanceNative Google client setup — documentation tools only
Verify the agent connection, then build safely offlineFour-call MCP check · Agent-to-backend tutorial
Install the published OpenAI Developer pluginVelox TriFit Developer — read-only API guidance
Connect the current MCP serverVelox TriFit MCP — protocol endpoint; documentation-only client setup · account/guest connection reference
Find the current MCP server in the official registryVelox TriFit registry listing · Publication record
Find the public API overviewVelox TriFit Partner API

Two public pages, not the Velox operator admin. The dashboard shows only the visitor's own browser-session requests and public SDK downloads. It exposes no keys, routing, quota editing, other visitors' photos or traffic-test controls. Hosted UI updates follow the Studio Development-to-Production release gates; the public host may run an earlier accepted version than the source you inspect.

See real public try-on examples

Existing official TriFit examples: AI personal portraits, clothing references and their actual TriFit outputs. These are historical examples, not mocks, newly run tests or performance/quality comparisons. Provenance and media notes.

Try your own photos in the TriFit app with available account allowance, or the shared demo without an account. The live host receives UI updates through its separate release.

Outfit-collage starter products

The demo source includes the same five clothing collages used in our provider comparison tests, copied without image edits. Select a whole board as the product reference and use a separate personal photo. Reference models inside a board are not the target person. Accessory transfer and garment fidelity can vary.

These are product inputs, not generated result images or proof of provider rankings. They are separate from the matched Amara/Mateo examples above. Brand names within the boards do not imply endorsement.

Install the Codex plugin

The Velox TriFit Developer OpenAI listing is published as Velox TriFit API Docs 1.1.6 (verified 28 October 2026). Its reviewed binding remains the legacy /partner/docs/mcp with four public documentation tools. It has not migrated to the unified endpoint. You can also connect the public documentation MCP directly in Codex or Copilot without installing the full plugin. Neither route grants live Partner API access. The official MCP Registry listing, io.github.Velox-XR/velox-trifit-developer version 2.0.1, was independently verified active and latest on 28 October 2026. It points to the current connection: https://studio.v3lox.com/partner/trifit/mcp. This follows 2.0.0 and supersedes the initial 1.1.0 legacy-endpoint publication under the same identifier, not a second listing. GitHub's curated registry onboarding is pending; the listing request has been submitted, not approved. See the publication record and update checklist. Registry publication does not guarantee search rankings or automatic agent recommendations.

See installation and test prompts. The GitHub marketplace package is separate from universal directory review and approval.

Velox TriFit — API guidance and try-on in one plugin

The Velox TriFit ChatGPT/Codex plugin combines API guidance with consented account or guest try-on in one package. The v1.2.3 Production-targeted source and reproducible ZIP builder are available for inspection. The current Production endpoint's initial 18-tool inventory and four anonymous documentation calls were verified on 24 October 2026. The 1 November check covered all five public tools; see the dated release status. Neither check proves authenticated try-on/client acceptance or public-directory approval. This repository distributes Production packages only. Private Development packages and connection instructions are not included. The existing developer package and its OpenAI review remain unchanged.

The candidate also includes applying by email inside the chat: confirm your connected sender mailbox, optionally add project details, then review and approve the message to [email protected]. No automatic key issuance. This mailbox workflow still needs an approved end-to-end send/receipt acceptance test.

One demo, one inspectable SDK integration

The hosted application is this repository's browser UI, demo backend and shared queue, using the JavaScript SDK. It is not a separate partner-specific application or a mock presented as real generation.

  • Dedicated hosted partner identity: demo.
  • Real DressMe requests; AnimateMe is not enabled for the public demo.
  • Signed, durable webhook completion with delayed GET-only recovery if a callback is missing. The UI labels the actual completion source.
  • Total elapsed duration, uploads, demo queue and submission-to-observed-completion timings. These are not GPU-only timings.
  • Download one look, or all your latest 25 completed requests, as an asset ZIP containing uploaded inputs, results and a timing/checksum manifest. This is separate from the SDK source ZIP.
  • One active generation, and at least 10 seconds between starts.
  • Personal and product uploads overlap, with durable receipts for both assets. This removes sequential upload waiting without changing generation quality or bypassing the queue and usage limits.
  • The dashboard ZIP contains this same public source, SDK, examples and guides.
  • No API key is needed to visit the Velox-hosted demo.
  • To run your own commercial partner backend, apply for your own partner configuration.
  • For code using your own TriFit account instead, use Example 2 without a partner key.

The checked-in configuration template identifies the demo integration and Production API URL, but its key is deliberately invalid and real generation is disabled. It is not a public API credential. The hosted service loads the real key privately on Velox's server. It never appears in GitHub, JavaScript sent to the browser or public ZIP downloads.

Run locally

Install Node.js 22 or later. No dependency installation is required:

sh
npm run preview

Open the printed URL. The demo and dashboard work locally; the preview cannot upload or generate. The dashboard's ZIP download works in preview too.

Explore the reference workspace

The public workspace follows the fuller partner-demo layout, with a developer sidebar linking to the public code, SDK ZIP, walkthrough and access application.

  • Add up to eight shopper photos and eight product images to local trays. The source also includes five starter outfit collages from the comparison tests. Click one to add it to the product tray without uploading anything. Select a pair and inspect it before sending a request. Adding, selecting or removing a preview performs no upload or generation.
  • JPEG, PNG and WebP photos are prepared locally in the browser: automatically resized to at most 2048 pixels on the longest side (never enlarged), with aspect ratio and browser-decoded orientation preserved. Your original files are untouched; only the prepared copies are submitted. No upload occurs while selecting or preparing images. Output stays within the API's 5 MiB cap. For browser safety, source files above 32 MiB or 100 megapixels are rejected with a prominent error. Unsupported or corrupt files also show clear errors.
  • Only an explicit consented submission sends the selected pair. The example uploads the pair for each new request; trays are not a persistent asset-ID catalogue or a shared partner library.
  • Review the request stages, original inputs, completed result and side-by-side shopper/result comparison. Local inputs are held only in the open page's memory; after reload, request history and available results can be read, not old inputs.
  • History shows only this signed browser session's latest 25 requests. Refreshing history or checking an uncertain request is read-only and never replays a job.

No production/development selector, shared photo library, routing, webhook registration or load-test controls are exposed by this public UI. The private partner workbench is unchanged.

For real Partner API access:

  1. Apply through your connected mailbox in the updated plugin, or use the website form. In-chat project, expected usage and launch timing details are optional.
  2. Velox reviews your request, creates a unique partner integration and emails private, environment-specific configuration.
  3. Save the supplied partner.config.json beside package.json.
  4. Run npm start. Startup verifies the assigned API identity and environment.

For webhook-first completion, ask Velox to grant webhooks:write on your own backend key, then register your public HTTPS receiver:

sh
node setup-webhook.mjs https://YOUR_HTTPS_HOST/webhooks/dressmenpm start

The setup command saves the endpoint ID and signing secret privately in partner.config.json. Hosted mounting prefixes must be included in the callback URL. See hosting for the exact origin/proxy contract. With no webhook configured, the local example remains explicitly polling-only; it does not claim webhook delivery. The standalone mock remains an unpaid API-flow fixture.

A free TriFit account is not a partner credential, but can authorise the separate personal-account example using its own available allowance. Real Partner API use can incur charges, including in Development. Never commit the private configuration or reuse the Velox-hosted demo key in another deployment.

Available SDKs

JavaScript (Node.js) + TypeScript declarations are available now, under MIT: SDK source · SDK reference.

The runnable demo is one complete integration of this SDK. More language packages, framework examples and agent guides can be added to this hub; the catalogue lists only implementations that actually exist. Other languages may use the documented HTTP API, but are not advertised as downloadable SDKs until shipped and tested.

Queue, privacy and safe recovery

The 10-second gap is a minimum start interval, not an ETA or performance guarantee. A job taking longer keeps the active slot until it finishes. One pending request per visitor and a backlog of 25 bound temporary admission; there is no lifetime request cap in the example. Velox API quotas and commercial permissions still apply. The newly created hosted partner currently has its default 100/month allowance; this repository does not silently increase it.

Browser sessions are private, signed and HttpOnly, with Secure cookies on HTTPS. The dashboard is session-scoped; clearing cookies loses access to that session's history. A 48-hour cookie expiry is not automatic media deletion. Image consent, the privacy policy and agreed retention apply.

The local evaluator stores receipts in ignored .demo-state/, with a single exclusive owner. It saves input IDs, idempotency keys and job IDs, not image bytes, API keys or signed URLs. An uncertain submission pauses the queue; it is never automatically replayed. After a crash, retain the journal and lock for operator reconciliation. Do not run multiple copies with the shared demo credential.

See hosting and release requirements and security. The queue's rate limit alone is not a financial budget or full bot defence.

Test without paid API calls

sh
npm testnpm run demo:mocknpm run demo:failure

Tests and explicit mock modes use local fixtures only. They do not read private configuration or call Velox. A mock result is not a real AI result or latency proof.

Licence

The public SDKs, examples, documentation and agent skill in this repository are MIT licensed. This does not license Velox's hosted API service, private product code, trademarks or customer material. API access and usage remain subject to separately agreed terms. AI previews are not guarantees of fit, sizing, colour or garment detail.

来源:README.md,提交 e49068e

工具

18

get_trifit_account

Read your connected TriFit profile

Identify whether this verified connection is a guest session or a personal TriFit account before choosing tools. Does not link, switch, create an account or trust a conversational email hint.

无需输入参数。

get_trifit_profile

Identify your connected TriFit profile

Read the stable profile represented by this connection. No account creation, switching, uploads or generation. Use get_trifit_account for connection mode and allowance source.

无需输入参数。

get_trifit_allowance

Read your TriFit account allowance

Read the same daily, weekly and monthly allowances as the TriFit website. Does not create, reset or spend credits.

无需输入参数。

list_trifit_library

List your TriFit account history

Read metadata for your saved personal photos, products, looks and DressMe requests. No image bytes or guest history transfer.

输入参数kindlimitoffset

prepare_trifit_upload

Prepare a local photo upload to TriFit

For a user-selected local file in Codex, with explicit permission: create a private, one-use upload URL valid for at most five minutes. PUT only that JPEG/PNG/WebP file as raw bytes, with its image Content-Type, no API/OAuth headers and no redirects. Do not print or share the URL. The PUT saves/resizes the image in the connected account library and selects its website photo/product slot; product images use cached description preparation. Preserve clientImportId and the returned assetId. Never retry an uncertain upload automatically. Preparing does not upload or generate.

输入参数role必填clientImportId必填permissionConfirmed必填

upload_trifit_image

Save a selected photo to TriFit

With explicit permission, import the selected personal or clothing image into the connected TriFit account. Resizes automatically, saves it in the website library and selects its photo/product slot. Product images also use the existing cached description preparation. Never import arbitrary URLs or retry an uncertain import automatically.

输入参数file必填role必填clientImportId必填permissionConfirmed必填

create_trifit_try_on

Create a TriFit account try-on

Only after explicit user approval, submit one DressMe request using two existing account image IDs. Uses the website queue and existing account allowance, not the guest demo. The attempt can consume allowance. Never automatically retry, replace the request ID or claim that a timeout means it did not run. Check the original receipt.

输入参数requestId必填productAssetId必填personalAssetId必填permissionConfirmed必填

get_trifit_try_on

Read an existing TriFit request

Read the status, recorded duration and result ID of an existing account DressMe request without generating or replaying. A missing receipt means acceptance is uncertain, not that it never ran.

输入参数jobIdrequestId

show_trifit_try_on

Show an existing TriFit result

Show a completed account DressMe image inside the conversation. Requires separate private-image permission. Uses only the existing result; no generation, upload, public share or new allowance is used.

输入参数jobIdrequestId

get_guest_demo_status

Check guest try-on allowance

Read the current private guest-session allowance and its perSessionLimit denominator. Does not upload images or generate anything.

无需输入参数。

prepare_guest_upload

Prepare a private local image upload

For Codex/local files: reserve one single-use HTTPS PUT upload for a personal photo or product image. Upload the user-selected file bytes to the returned URL; do not disclose that capability. Server resizes JPEG, PNG or WebP automatically. At most one upload per role per guest session. This does not generate a try-on.

输入参数role必填

create_try_on

Create one guest virtual try-on

Generate a DressMe virtual try-on from the user’s personal photo and clothing reference only after their explicit request and permission. In ChatGPT pass both attached image files; in Codex pass the two asset IDs returned by completed private uploads. Use one method, not both. Consumes one session attempt and one shared daily attempt. One attempt per guest session, ten per day across all guests. Do not automatically retry or bypass limits. Returns a receipt; get_try_on retrieves its status/result.

输入参数consent必填garment_imagepersonal_imageproduct_asset_idpersonal_asset_id

get_try_on

Read your guest try-on result

Read only an existing request belonging to this authenticated guest session. With include_image=true, shows the completed image in a result card in ChatGPT and an inline image in other MCP clients. Does not create/retry a generation. Poll no more often than once every five seconds. A needs_review result must not be replayed.

输入参数request_id必填include_image

fetch

Read a Velox developer document

Read the full public document for an ID returned by search, with an official source URL and deployed content checksum. Does not fetch arbitrary URLs or private files.

输入参数id必填

get_integration_example

Get a Velox SDK integration example

Retrieve the runnable offline JavaScript/Node.js integration example or accompanying TypeScript declarations. Other language SDKs are not released. The example uses dummy local responses, with no cloud calls or generation charges.

输入参数language必填

get_partner_access_requirements

Get Velox partner access requirements

Explain how to apply for manually provisioned Velox Partner API access and keep the scoped application key on a backend. Does not create accounts, issue keys, send an application or promise a universal free allowance.

无需输入参数。

get_partner_application_guide

Apply to the TriFit team through your connected mailbox

Read the official in-chat Partner API application workflow: [email protected], sender confirmation, optional project details, draft preview, send approval and actual reply verification. Public guidance only; this tool does not send email, inspect a mailbox, submit a form, issue keys or change access. No TriFit account is required.

无需输入参数。

版本历史

2
  1. v2.0.1最新Oct 29, 2026
  2. v2.0.0Oct 25, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分