Legal
Service Agreement
Effective date: August 11, 2026
This Service Agreement describes the scope, billing, orchestration, and delivery rules for the platform API, model capabilities, playground, tasks, and artifacts.
1. Services
We provide unified authentication, model routing, synchronous or asynchronous task submission, task status, events, billing, and artifact delivery. Available models, parameters, regions, prices, rate limits, and processing times are stated in the market, model detail, and API response.
2. Activation and subscription
Create an application and satisfy the product subscription, balance, or activation requirements. Acceptance may depend on region, account state, supplier availability, quota, and risk controls.
3. Multiple outputs
Supported image and video capabilities use n to select 1–4 outputs; omitted n means 1. The platform creates one independent subtask per output and charges and settles each subtask separately. A task may finish as partial_succeeded, so read subtasks and artifacts to collect every successful output.
4. Billing, holds, and refunds
The platform may place an estimated total balance hold before submission. Successful subtasks settle at their unit price; supplier failures, timeouts, or explicitly non-chargeable subtasks release the applicable hold. Membership discounts, modifiers, per-second, and token pricing are calculated by the backend at acceptance.
5. Tasks and artifacts
Async tasks return task_id and can be followed through task details, SSE, or callback_url. Artifact links may expire, and backups may be retained or removed under the published retention policy. Save artifacts you need for long-term use.
6. Inputs, callbacks, and third parties
You are responsible for lawful, secure, and available inputs, callback URLs, and receivers. Suppliers, networks, storage, and third-party callbacks can affect latency, results, and availability; we use retries, circuit breakers, and error classification within our control.
7. Availability and maintenance
Unless separately agreed in writing, we do not promise a fixed SLA, success rate, or generation time. We may perform maintenance, upgrades, supplier changes, and security actions and will provide reasonable notices or status signals.
8. Prohibited conduct and risk controls
Do not use the service for unlawful activity, rights violations, billing or rate-limit evasion, spam generation, attacks, malicious files, or interference with other users. We may reject requests, freeze tasks, limit quota, or suspend accounts to manage risk.
9. Liability boundary
We are responsible for our direct fault to the extent required by law, but not for indirect losses caused by suppliers, networks, devices, user inputs, or third-party systems. Production callers should implement timeouts, retries, idempotency, fallback, and output validation.
10. Contract effect
This agreement works together with the User Agreement, product pages, pricing rules, and API documentation. If terms conflict, the more specific rule that was active when the request was accepted controls.