Theme
Service-Specific Terms
Effective: August 14, 2026
These terms supplement the Terms of Service and Usage Policy for API aggregation, model calls, keys, balance, subscriptions, redemption codes, promotional credit, metering, and routing. The more specific provision here controls the same subject unless mandatory law provides otherwise.
1. Aggregation, routing, and upstreams
The platform provides technical access, request routing, usage records, and support for third-party models; it does not train, own, or control every model. Requests may be routed, limited, rejected, or charged according to account, group, balance, subscription, model, channel capacity, price, and risk controls.
The platform may add, remove, or suspend models; adjust aliases, protocols, context, output, rate, and concurrency limits; and switch among accounts, regions, or channels serving the same named model. Cross-model fallback is used only when enabled by the user or disclosed in advance, and must not silently misrepresent a different model or materially different version as the selected model.
2. API-key responsibility
Keys must not be disclosed, sold, rented, or shared with unauthorized parties. Requests and charges made with an account or key are generally the user's responsibility. Revoke or replace a key immediately after abnormal activity. The platform may limit, suspend, or delete a key involved in attacks, unusual concurrency, sharing, resale, or fraud.
3. Metering and billing
Billing units may include input, output, and cached tokens; images; audio or video duration; generation units; request count; compute time; model price; group multiplier; and plan rules. Records may contain timestamps, user/key/group IDs, model, protocol, tokens, cache, status, error, amount, latency, and upstream channel identifiers. Providers may count usage differently; absent a clear error, platform billing records control.
4. Failed and interrupted requests
| Event | General treatment |
|---|---|
| Authentication, insufficient balance, invalid parameters, or platform rejection before forwarding | No model-usage fee |
| Forwarded request returns a clear upstream system error with no usable output | Review upstream billing and logs; reverse an erroneous charge where appropriate |
| Partial or complete text, image, audio, or video was generated | Actual usage may be charged |
| User network failure, client cancellation, timeout, or misconfiguration after upstream usage | Usage may still be charged |
| Output was generated but did not meet subjective expectations | Not a platform error; generated usage is not refunded |
| Duplicate charge, billing error, or platform technical error | Reverse or correct without a refund fee |
5. Paid balance and promotional credit
Paid balance is actual payment credited as service prepayment. Promotional credit includes registration, referral, promotion, coupon, code, drawing, or non-cash compensation. The two may be recorded separately and follow different consumption order, model scope, expiration, and restrictions.
Promotional credit cannot be withdrawn, transferred, traded, invoiced, or refunded. Expired, mistakenly issued, improperly obtained, refund-linked, or abused promotional credit may be withdrawn.
6. Personal-reason refunds
An applicant must use an official channel, provide the account, order, payment time, and receipt, and pass checks for stolen payment, abusive chargeback, cash-out, bulk registration, promotion abuse, and false evidence.
Only unused, actually paid balance confirmed by the ledger is refundable. Consumed amounts, promotional credit, remaining subscription benefits, non-refundable third-party fees, and improperly obtained benefits are excluded.
text
Refund received = refundable principal × 95%For example, 100 units of refundable principal produces a 95-unit refund, and related promotional credit expires or is withdrawn. Each top-up is generally refunded once to the original payment method. Credit obtained by code or an irreversible method is non-refundable unless the platform agrees or law requires otherwise.
7. Platform errors and timing
No 5% fee applies to a verified duplicate charge, successful payment that cannot be credited or reissued, platform billing error, or platform failure that charged for service not delivered. The user should provide order number, request ID, time, model, and error details.
After approval, the platform initiates the refund within three business days. A payment provider, bank, or blockchain network may take longer to settle. Delay caused by incorrect user information, channel limits, bank review, or force majeure does not mean the platform failed to initiate on time.
8. Subscriptions
A subscription grants usage within a period, model, group, rate, or allowance and is not account balance. Except for duplicate or erroneous billing, confirmed inability to provide the purchased service without a reasonable alternative, or mandatory law, subscriptions are non-refundable regardless of use or remaining allowance.
Requests may pause after an allowance or protection-window limit until reset, renewal, upgrade, or service switching. Renewal and rollover follow the purchase page. Cancellation stops future renewals; it does not automatically refund the current period.
9. Codes, promotions, and rewards
A redeemed code binds its benefit to the account and is normally irrevocable, non-transferable, non-cashable, and non-refundable. Promotions may limit eligibility, quantity, scope, and expiration. Rewards linked to refunds, chargebacks, related accounts, bulk registration, abnormal transactions, or violations may be cancelled. Refund-linked promotional credit may be withdrawn, but cannot offset actual money owed back for a verified platform error.
10. Payment disputes and fraud
Use official support first for billing disputes. A payment dispute or chargeback does not prevent the platform from submitting transaction, login, usage, and communication records. Suspected theft, abusive chargebacks, cash-out, false refund claims, or third-party-payment disputes may pause service and refunds, freeze disputed balance, and require evidence. Consumed service may not be recovered through a chargeback.
11. Rate limits and fair use
Rate, concurrency, allowance, and risk limits may apply to an account, key, group, model, channel, or request source. Sufficient balance or an active subscription does not prevent limits caused by request frequency, upstream throttling, abnormal content, load, security, region, or maintenance.
12. Request data and logs
Users must have authority to process submitted content and must not submit unauthorized highly sensitive, confidential, regulated, or unlawful data. Necessary account, order, request metadata, usage, errors, and security logs may be processed for routing, billing, debugging, security, and abuse prevention.
The platform does not normally retain complete prompts or outputs solely for billing, but may temporarily process necessary content during debugging, safety, compliance, or a user support case. Requests may be sent to third parties providing models, cloud computing, networks, or monitoring; users should assess these arrangements before submission.
13. Changes, suspension, and termination
Endpoints, models, plans, prices, multipliers, allowances, routes, logs, and controls may change for technical, safety, compliance, regional, operational, or upstream reasons. Violations of law or platform and provider rules may cause limitation, suspension, termination, and cancellation of improperly obtained benefits. Remaining balance and subscriptions are handled according to the reason, these terms, and law.
14. Applications and review
Submit a refund, order issue, or abnormal charge through the public Contact page or console support, with the account, order, payment/charge time, receipt, request ID, model, and error. Submission does not guarantee a refund; review uses payment callbacks, orders, usage, logs, and actual delivery.
An adverse decision may be reviewed through official support. Fraudulent, abusive-chargeback, false-evidence, duplicate, billing-evasion, or refund-process abuse claims may be rejected, and the related account or key may be restricted.