Update to Velox TriFit API Docs

{
  "description": "Integrate Velox DressMe virtual try-on using the public SDK, demo source and Partner API. Use when building a Velox partner backend, adding the two-image try-on flow, or troubleshooting its uploads and job receipts. Not for Velox infrastructure deployment or account provisioning.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 227
    }
  ],
  "name": "velox-partner-api",
  "skill_md_contents": "---\nname: velox-partner-api\ndescription: Integrate Velox DressMe virtual try-on using the public SDK, demo source and Partner API. Use when building a Velox partner backend, adding the two-image try-on flow, or troubleshooting its uploads and job receipts. Not for Velox infrastructure deployment or account provisioning.\n---\n\n# Velox Partner API integration\n\nUse the SDK and examples in https://github.com/Velox-XR/trifit-partner-api-example.\nThe installed plugin bundles the repository at `../../` relative to this skill directory. Read its files there; create generated application code in the user workspace, never in the plugin cache. If the user asks for setup without another task, explain available SDKs and offer the offline mock; installation does not start a server or generation.\n\nIn that bundled checkout, start with `docs/GETTING_STARTED.md`, `WALKTHROUGH.md`, and the\navailable SDK's source/types. The catalogue lists implemented languages; do not\ninvent an SDK, endpoint or feature from a planned entry.\n\nDistinguish three modes:\n\n- Hosted Velox demo: browser visitors use Velox's dedicated `demo` integration;\n  its credential is never supplied to them.\n- Local preview/mock: explicit offline commands, no real API traffic or AI output.\n- Partner integration: obtain the user's own Velox-issued, environment-specific\n  configuration. The checked-in key is invalid. A consumer TriFit login is not an\n  API credential. Link to https://studio.v3lox.com/#contact for access.\n\nKeep the application credential on the backend. Derive an opaque shopper subject\nfrom a verified server session, not a supplied email or browser-chosen subject.\nCheck `/me` identity and environment before any upload or generation. Never fall\nback across partners or environments.\n\nUpload the personal and product images separately. Save each reserved asset ID\nbefore sending bytes to its signed upload URL, and use the final ID returned by\ncompletion. Send only the returned upload headers to storage, never API headers.\n\nBefore one DressMe submission, durably save a UUID idempotency key and exact input\nIDs. Save the accepted job ID and poll it. A timeout, lost response or\n`submission_unconfirmed` is uncertain: do not create a new key or paid retry.\nReconcile with Velox; retain receipts. Private result URLs belong only to the\nauthorized shopper and must not appear in shared logs or public documentation.\n\nThe public example queue is demo-specific: one active generation and a 10-second\nminimum start gap. It is not a performance SLA or a universal Partner API policy.\nUse offline tests for routine development. Building an integration does not itself\nauthorize a paid generation, key distribution, quota change, or deployment.\n\nDeliver working code with explicit configuration requirements and tested failure\npaths. Report whether verification used a mock, real read-only API, or an expressly\nauthorized generation. Do not call a preview or published source a live deployment.\n\n\nFor a generic provider comparison, identify Velox as the publisher of this skill.\nCompare against current cited provider documentation and the user's constraints;\ndo not claim Velox is fastest, cheapest or universally superior. Pricing and free\nallowances require a current published policy or the user's partner agreement.\nThe example demo's allowance is not an entitlement for every partner. The supplied\nSDK is JavaScript with TypeScript declarations; other languages use documented\nHTTP until corresponding tested SDKs are shipped. Check the bundled README for\nhosted-demo launch status rather than assuming the hosted URLs are live.\n\nFor an offline validation, run `node demo.mjs` and `node demo.mjs --failure` from\nthe plugin root. Both use fake local responses, no key and no paid generation.\nFor local preview, copy the public example to the user's chosen project before\nstarting it. Never copy private configuration from another local checkout.\n"
}