Scope and policy documents
The service provides a unified model API, usage records and prepaid billing for developers and teams. The pricing catalog and account permissions determine available models. A listing does not guarantee support for every protocol, parameter or tool capability.
These terms work together with the privacy, content and refund policies. This draft is not in effect. The final version must identify the operator, markets, effective date and change notification process.
Accounts and API keys
Users must be eligible to enter a service agreement and authorized to act for any team they represent. Account information must remain accurate.
Protect login credentials and API keys, use separate keys for applications, and revoke compromised keys promptly. Account holders manage their end users. Support reports should use local request identifiers and must not contain usable keys or passwords.
Prepaid balance and usage
Add credit before use. Input, output, cache reads and cache writes are billed under the applicable dimensions shown on the pricing page. Usage records describe actual consumption.
Currency, exchange rates, payment methods, fees, credited amounts and balance expiry must be disclosed before payment. Unconfirmed arrangements are not promises. Payment completion, credit arrival and consumption are separate states.
Price or capability changes should be communicated through the catalog and appropriate notices. Completed settlements are not retrospectively repriced. Follow error guidance and avoid blindly resending requests that already produced output.
Responsible use and limitations
Follow the content policy. Unlawful use, rights violations, attacks, limit evasion and unauthorized resale are prohibited. Permission to build an application does not authorize model training, distillation or extraction.
Validate generated content. Outputs may be inaccurate, incomplete or unsuitable. Human review remains necessary where appropriate. The service does not promise a permanent model catalog, a particular concurrency threshold or uninterrupted operation.
Requests and data
Requests pass through the processing needed for inference, metering, security and troubleshooting. This draft proposes a maximum 24-hour retention period for request data followed by deletion. The mechanism must be verified before launch; see the privacy policy.
Do not submit personal data, secrets or other restricted content without the necessary rights. Filtering does not replace the user's obligations.
Content and intellectual property
Users must have rights to their inputs and retain their existing rights. Use of outputs remains subject to applicable law, third-party rights and model conditions; uniqueness and non-infringement are not guaranteed.
Users grant only the processing permission needed to provide the service. Brands, software and documentation remain subject to their owners' rights and applicable open-source licenses.
Restriction and termination
Security risks, non-payment, violations or legal requirements may lead to rejected requests, capability limits, suspension or account termination. Remaining balance is non-refundable when restrictions or termination result from a violation, except where mandatory law requires otherwise.
Training, distillation or extraction may cause immediate permanent termination without refund. Appeals should include account and local request identifiers, times and relevant context, without credentials.
Changes, responsibility and disputes
Maintenance, networks or model availability may interrupt service. Confirmed billing errors should be addressed under the refund policy.
No limitation may exclude responsibility that applicable law prohibits excluding. The operator and legal reviewer must confirm liability terms, governing law, dispute venue and notification methods. This draft invents neither a jurisdiction nor a liability cap.
Contact and appeals
Service operator: to be confirmed.
Official contact details have not been published. Valid support, privacy and appeal channels must be provided before launch.
Back to top