ai.virtual_try_on
No public human summary is currently bound to this canonical operation identity.
Canonical operation ID · ai.virtual_try_on
Current access · No public execution path
Public route · not bound
Operation contract · canonical identity
ai.virtual_try_on
No public human summary is currently bound to this canonical operation identity.
ai.virtual_try_onUnavailableNo operation-specific incident feed is boundNot bound in public operation truthcontract 2026-07-29.1
FamilyAI
Family probelive
QuoteNo public price record
NetworkNot bound at operation level
Proofpaid outcome verified
Observed
2026-08-11T08:48:34.576Z01 · What it does
The callable contract for this task.
Human meaning and machine truth stay together. Anything not bound by current canonical artifacts remains explicitly unavailable rather than filled from the design fixture.
Boundary
Unknown fields stay unknown.
Action class, operation-specific health, latency, provider identity, and history are not inferred from family or fixture copy when current public truth does not bind them.
No hidden live execution from this page.
No fake quote, wallet, receipt, transaction, or settlement.
Gold only marks explicitly verified proof.
02 · Required input
Inputs are explicit before execution.
Where the current OpenAPI route binds an input schema, this page renders that exact schema. Otherwise the structure remains visible with a truthful unbound state.
operationai.virtual_try_on
canonical identityHTTP routeNo public execution route bound
unavailableIdempotency-KeyNo operation-level requirement is asserted here.
not boundRequest schema · canonical OpenAPIOpen raw
No operation-specific public request schema is bound.
03 · Returned result
Result, evidence, and receipt stay separate.
A useful response is not automatically a verified paid outcome. The page keeps schema, evidence, receipt, and proof state distinct.
result contract · canonical where bound
No operation-specific public response schema is bound.
04 · Availability & limitations
Current availability before the call.
Operation publication and family probe truth are shown separately so a family-level live observation cannot silently make every operation callable.
Operation lifecycleUnavailable
No public execution path is claimed for this operation.
Family probelive
Observed family state; not substituted for operation publication.
Operation healthNot bound
No operation-specific incident feed is bound.
Proof levelpaid outcome verified
Current observed family proof vocabulary.
05 · Price, asset, network & approval
No hidden charge. No standing permission.
Current pricing truth is bound where the public pricing document has an exact operation record. Approval controls below are a labeled visual fixture and perform no authorization.
Current price boundary
No public price record
A single amount is not published; the executable route returns its own bounded quote where supported.
Operationai.virtual_try_on
MaximumNo single amount published
NetworkNot bound at operation level
AssetNot bound
Price versionnot bound
Observed2026-08-11T08:48:34.576Z
Approval boundary · design fixture
Not approved
QUOTE required
Standing authorityNone
This UI state does not sign, authorize, fund, or settle anything. It exists only to preserve the locked approval information architecture.
06 · Execution states
Verified, refused, and unresolved are different outcomes.
Request red enters. Qualification, execution, and unresolved investigation use cyan. Gold appears only on the verified proof state.
Scenario · design fixture
Run the operating contract visually.
No API, provider, wallet, payment, or settlement action is performed.
Design-state fixture only. No live request, wallet action, payment, settlement, or receipt generation occurs here.
Request
waitingBounded task and identity received.
Qualify
waitingLifecycle, schema, policy, route and price boundary checked.
Execute
waitingSelected route would perform the approved task.
Verify
waitingOutput, evidence and settlement truth would be checked.
Prove
waitingResult, evidence, receipt and replay state close the contract.
07 · Expected latency & timeout
Unknown timing stays unknown.
The locked structure is preserved without fabricating a percentile chart, SLA, provider deadline, or reconciliation duration.
Operation latency
—
Not published.
No reproducible operation/version latency measurement is currently bound to this page.
Timeout & reconciliation
—
Not bound at operation level.
Platform recovery rules remain available below. A blind retry is never implied when settlement is unknown.
08 · Evidence & receipt fields
Proof is part of the product surface.
Exact paid proof is shown only when the current status authority names this operation. Otherwise the page keeps proof neutral.
Current proof boundary
paid outcome verified
family observation · AIoperationai.virtual_try_on
response schemanot bound
receipt generation herenone
customer revenue claimnone
Operation-specific proof
No paid outcome proof bound.
No gold production claimsettlementnot asserted
replaynot asserted
receiptnot invented
09 · Skill, MCP, SDK & HTTP
The same operation identity across every interface.
Only package publication and raw routes proven by generated public artifacts are shown. Operation-specific client syntax is omitted when it is not safely generated here.
No public HTTP execution route is bound for ai.virtual_try_on. Inspect /openapi.json for current machine truth.
Canonical publication evidence only. No `@clervo/router` publication or unsupported client compatibility is implied.
10 · Errors & recovery
Every known failure keeps a next action.
HTTP errors come from the mapped OpenAPI route where one exists. Platform recovery codes come from the generated onboarding contract and remain separate from operation-specific claims.
SourceCodeMeaningRecovery
OpenAPI
not boundNo operation-specific public error map is bound.Inspect lifecycle and current machine artifacts before attempting execution.Platform recovery
insufficient_fundsinsufficient_fundsAdd enough of the quoted asset on the quoted network, then request a fresh quote. · retry: after actionPlatform recovery
wrong_network_or_assetwrong_network, wrong_asset, unsupported_network, unsupported_assetSwitch to the quote's exact network and asset, then request a fresh quote. · retry: after actionPlatform recovery
expired_quotequote_expired, expired_quoteRequest a fresh quote and never reuse the expired authorization. · retry: after actionPlatform recovery
rejectedauthorization_rejected, payment_rejected, user_rejectedReview the maximum charge and approve again only if you still intend to pay. · retry: after actionPlatform recovery
timeoutauthorization_timeout, payment_timeoutReconcile the existing idempotency key before deciding whether to retry. · retry: prohibited until reconciledPlatform recovery
unknown_settlementsettlement_unknown, unknown_settlementReconcile the existing operation and do not authorize or retry until settlement is definitive. · retry: prohibited until reconciled11 · Idempotency & safe replay
The same bounded task does not silently become a second effect.
Where current OpenAPI requires an Idempotency-Key, that requirement is shown directly. Retention windows and scope are not invented.
Replay contract
Identity before retry.
No operation-specific idempotency header requirement is bound. Retention duration and account scope are not published on this page.
Operation: ai.virtual_try_on
Idempotency-Key: not bound
Retention: not published
Unresolved settlement: retry blocked until reconciliation
Idempotency-Key: not bound
Retention: not published
Unresolved settlement: retry blocked until reconciliation
Replay · design fixture
Awaiting verified fixture
Live executionNone
Fixture replayNot requested
Additional live chargeNone
Run the verified design state first to demonstrate safe replay semantics.
12 · Version history & related operations
Current version truth without invented history.
The current contract, catalog, pricing, and observation identifiers are visible. Historical operation versions remain unclaimed until a canonical history exists.
Contract 2026-07-29.1Current generated contract
Catalog 2026-08-02.2. OpenAPI 2026-07-29.1. Observed 2026-08-11T08:48:34.576Z.
Operation historyNot bound
No synthetic changelog, sunset date, compatibility window, or replacement history is generated here.
Current machine surfaces