이 약관은 영어 원문으로만 제공돼요.
Effective date: September 15, 2026 · Last updated: September 7, 2026
1. Description of the Inference Services
To the extent made available, the Inference Services enable Customer to submit Inputs to an AI Model through a VESSL-managed endpoint and receive Outputs. The available endpoint type, capacity model, interfaces, AI Models, Regions, rate limits, quotas, and other features are only those identified in the then-current Documentation, VESSL console, or applicable Order Form. Customer accesses the Inference Services only through the interfaces VESSL makes available and not through direct, unmodified access to an underlying infrastructure provider’s console, APIs, or credentials.1.1 Definitions
In addition to the terms defined in the MSA, the following terms apply to these Inference Terms: “AI Model” means a computational machine-learning model that, when executed against an Input, generates an Output. “Hosted Model” means an AI Model that VESSL expressly identifies in the Documentation or applicable Order Form as selected, integrated, and operated by VESSL. “Input” means prompts, instructions, code, data, or other content provided by Customer (or its Authorized Users or End Users) for processing by an AI Model. “Output” has the meaning given in the MSA and includes the response returned by the AI Model in respect of an Input. “Model License” means any third-party or open-source license terms applicable to an AI Model that VESSL makes available, as identified in the Documentation or applicable Order Form.2. Models and Licenses
2.1 Third-Party Models
Where VESSL makes a third-party or open-source AI Model available, that model is subject to its applicable Model License. Customer is responsible for reviewing and complying with that Model License and for determining whether the model is suitable for Customer’s intended use. VESSL does not represent or warrant that a Model License permits Customer’s intended use.2.2 No Training of Models
VESSL will not use Customer Content, Inputs, or Outputs to train, fine-tune, or update any AI Model, internal classifier, content-moderation model, security model, or other machine-learning or artificial-intelligence model unless Customer affirmatively opts in in writing. VESSL may apply existing automated security, abuse-detection, fraud-prevention, and content-filtering tools as permitted by the MSA and DPA, but may not use the Customer Content, Inputs, or Outputs processed by those tools to train or update a model without that written opt-in.2.3 Beta and Preview Services
Inference Services, AI Models, endpoints, or features that VESSL designates as “Beta,” “Preview,” “Experimental,” or similar are subject to MSA Section 2.3, are excluded from the SLA, may be modified or withdrawn at any time, and may produce less stable Outputs. Customer may use them for production workloads at Customer’s discretion and risk, but must not use them for a prohibited High-Risk Use under MSA Section 14.19. An applicable Order Form may impose a narrower restriction.3. Inputs and Outputs
3.1 Customer Inputs
Customer is solely responsible for the Inputs it submits to the Inference Services and for ensuring that such Inputs comply with this Agreement, the AUP, applicable Model Licenses, and applicable law. Customer represents that it has all rights and consents necessary to submit the Inputs.3.2 Outputs
As between VESSL and Customer, Customer owns the Outputs generated by the Inference Services from Customer’s Inputs, subject to the rights of model providers under the applicable Model License (including any restrictions on commercial use or distribution of Outputs). Customer acknowledges that Outputs are produced by machine learning models and assumes responsibility for evaluating Outputs for fitness for use in accordance with Section 3.3.3.3 Probabilistic Nature of Outputs
Customer acknowledges that machine learning models produce probabilistic Outputs that may be inaccurate, incomplete, biased, or otherwise unsuitable for a given purpose. Outputs may include “hallucinations,” fabricated facts, or content that resembles but does not actually originate from training data. Customer will (a) evaluate Outputs for fitness for purpose before relying on or distributing them, and (b) implement human review and other controls appropriate to Customer’s use case, including in any high-risk or regulated context.3.4 No Use as Sole Basis for High-Stakes Decisions
Customer will not use Outputs as the sole basis for decisions in domains with significant legal or similarly significant effects on individuals (including credit, employment, housing, healthcare, education, criminal justice, immigration, and benefits eligibility) without meaningful human oversight, transparency to affected individuals, and compliance with applicable law (including the EU AI Act).4. AI Content Restrictions
The MSA and AUP apply in full to Customer’s use of the Inference Services. Customer must not use the Inference Services in a manner prohibited by MSA Section 3.1 or AUP Sections 1 through 3, including to generate child sexual abuse material, non-consensual intimate imagery, content that materially uplifts CBRN weapons, malware or exploits, fraudulent or deceptive content, or content used for unlawful automated decision-making. VESSL may apply existing automated content filters to Inputs and Outputs where reasonably necessary to enforce these restrictions, protect the Services, or comply with applicable law. Applying a filter does not authorize VESSL to use Customer Content to train or update that filter or another model. Any human access to filtered Inputs or Outputs is governed by the DPA and Support Policy. Customer remains responsible for ensuring that its Inputs and use of Outputs comply with the AUP and the applicable Model License.5. Data Handling
5.1 Logging and Retention
By default, the Inference Services operate on a Zero Data Retention basis: VESSL does not persist Inputs or Outputs beyond what is necessary to process the request and return the Output to Customer, and does not use Inputs or Outputs to train, fine-tune, or update any model (consistent with Section 2.2). VESSL processes only operational metadata that does not contain the content of Inputs or Outputs — such as token counts, request counts, timestamps, status codes, and model identifiers — for billing, rate-limiting, security, abuse prevention, and capacity planning, and retains such metadata in accordance with the DPA.5.2 Optional Content Logging and Limited Exceptions
Notwithstanding Section 5.1, VESSL may retain Inputs and Outputs only in the following cases: (a) where Customer expressly opts in — through the VESSL console or the applicable Order Form — to content logging for debugging or quality purposes, in which case VESSL retains Inputs and Outputs for the period selected by Customer (thirty (30) days by default and no more than sixty (60) days), after which VESSL deletes the Inputs and Outputs from active production systems; and (b) to the minimum extent, and for the shortest time, necessary to detect, prevent, or respond to abuse, fraud, or security incidents, or to comply with law or valid legal process. Any residual copies permitted in backups, security or audit records, or under a legal hold are governed by DPA Section 12.3. Any such retention remains subject to MSA Section 6.2 (which prohibits use of Customer Content, Inputs, or Outputs to train, fine-tune, or update any machine learning or artificial-intelligence model, whether internal or externally available, absent Customer’s affirmative written opt-in) and the DPA.5.3 Personal Data
Customer must not submit Restricted Data identified in MSA Section 3.8 unless VESSL expressly agrees in writing. For other Personal Data, Customer is responsible for compliance with Applicable Data Protection Laws.5.4 Confidentiality of Inputs and Outputs
Customer’s Inputs are Customer Content. Inputs and Outputs will be treated as Customer’s Confidential Information under the MSA and, to the extent they contain Personal Data processed by VESSL on Customer’s behalf, as Customer Personal Data under the DPA. VESSL will not use Inputs or Outputs to train, fine-tune, or update any model without Customer’s affirmative written opt-in. VESSL personnel and Sub-processors may access Inputs or Outputs only to the minimum extent permitted under the DPA for operation, Customer-authorized support, security, abuse prevention, valid legal process, or an approved emergency response, and only under applicable confidentiality, access-control, minimization, and logging requirements.6. Rate Limits and Quotas
The Inference Services are subject to rate limits and to context-length, token, request-size, and concurrency limits as set out in the Documentation or Order Form. VESSL may modify these limits as necessary to protect the integrity, security, and availability of the Inference Services, with reasonable notice where practicable.7. Billing for Inference
For Self-Service, if VESSL makes a Self-Service Inference Service available, billing is governed by Annex A using the rates and billing units displayed in the VESSL console or Documentation. For B2B, the applicable billing basis and Fees are stated in the Order Form. Customer is not charged for a request that fails in the circumstances described in Section 6.3(a) of the SLA. VESSL’s applicable usage and billing records are authoritative except in the case of manifest error.8. Service Levels
The Inference Services are Covered Services under the public SLA only to the extent, and from the date, that VESSL expressly designates them as such in the then-current public SLA. Where so designated, the availability commitment, the measurement method, and the exclusions applicable to the Inference Services are those stated in that SLA, and the remedy for on-demand use is the one stated there. Service Credits are not issued for on-demand use of an Inference Service. Any other service-level commitment — including any throughput, capacity, latency, or token generation rate commitment — and any Service Credit or other remedy for it, applies only if expressly stated in the then-current public SLA, an applicable private SLA, a Custom SLA Addendum, or an Order Form. Beta, Preview, Early Access, and other pre-general-availability Inference Services remain excluded from the SLA under MSA Section 2.3.9. No Indemnification for Outputs
Except as expressly set out in MSA Section 12.1, VESSL does not indemnify Customer against claims arising from the content or Customer’s use of Outputs, including Outputs of a third-party AI Model. Any rights or remedies provided by a third-party model provider are governed by the applicable Model License or agreement with that provider.10. Model Lifecycle and Deprecation
10.1 Model Availability
VESSL may add, update, or withdraw an AI Model made available through the Inference Services. The Documentation identifies the AI Models then available and, where VESSL supports version pinning for a model, the model versions Customer may pin.10.2 Deprecation Notice
For a Hosted Model that VESSL has made generally available, VESSL will give Customer at least fourteen (14) days’ notice before that model ceases to be available through the Inference Services. Notice is given through the Documentation, the VESSL console, or by email to the address on file for Customer. Where VESSL’s usage data indicates that a model is in broad production use, VESSL will use commercially reasonable efforts to provide a longer notice period.10.3 Beta, Preview and Experimental Models
An AI Model, endpoint, or feature designated as Beta, Preview, Experimental, or otherwise pre-general-availability may be modified or withdrawn at any time without notice, consistent with Section 2.3.10.4 Immediate Withdrawal
Notwithstanding Section 10.2, VESSL may suspend or withdraw an AI Model immediately and without the notice period in Section 10.2 where (a) the applicable Model License terminates, expires, or is modified so that it no longer permits VESSL to make the model available, (b) continued availability would create a security, safety, or abuse risk, or (c) withdrawal is required by applicable law or regulation, by a governmental or judicial order, or in response to a claim that the model or its outputs infringe or misappropriate a third-party right. VESSL will notify Customer as promptly as reasonably practicable in each such case and will identify a replacement model where one is available.10.5 Effect
Withdrawal of an AI Model in accordance with this Section 10 is not a failure to provide the Inference Services and does not give rise to a Service Credit under the SLA. Customer is responsible for migrating to a replacement model before the stated end date. A request submitted to a withdrawn model after that date may return an error.11. Modifications
VESSL may modify these Inference Terms from time to time, subject to MSA Section 14.10.VESSL AI, Inc. — legal@vessl.ai