Using RACKVO
Service limits & risks
Understand availability, output quality, payment finality and data handling before buying compute.
Provider availability
A provider can reject a job, delay execution or return an error. A capacity animation is not an availability signal. The real provider interface must determine acceptance and terminal state.
Output quality
Model outputs can be incomplete, unsuitable or incorrect. Receipts help trace a request and its result; payment records help trace a transfer. Neither automatically certifies output correctness.
The buyer must evaluate results against the task requirements. No third-party audit or independent correctness guarantee is claimed.
Payment and refunds
Sending tokens to the wrong network, mint or recipient can lose funds. Live payments must be bound to an approved quote. A provider error does not automatically reverse a confirmed transfer; refund behavior must be defined by the integration.
Inputs and retention
Do not submit confidential inputs to a provider before reviewing its data policy. Provider retention, output access, deletion rules and model-training use must be documented before the live offer is enabled.
Preview limits
Last updated 29 October 2026.