Skip to main content

Universe Service Agreement

Last Updated: June 5, 2025

Effective Date: June 5, 2025


Preamble

Welcome to the Universe API Service Agreement!

This "Universe API Service Agreement" (hereinafter referred to as "this Agreement") is a legal agreement entered into between the operator of the Universe API platform (hereinafter referred to as "we," "us," or "the Service Provider") and you (hereinafter referred to as "the User," "the Developer," or "the Customer") regarding the provision and use of Universe API technical services.

This Agreement, together with the "Universe API User Agreement" and the "Universe API Privacy Policy," constitutes the complete understanding between you and us regarding your use of the Service. In the event of any conflict among these documents, this Agreement shall prevail.

Please read and fully understand all terms of this Agreement before using the Service. By registering, logging in, or using the Service, you acknowledge that you have fully understood and agree to be bound by this Agreement.


1. Service Overview

1.1 Service Content

Universe API provides developers with large language model API services, which primarily include:

Service CategorySpecific Content
Model Inference ServiceProvides API access to multiple proprietary large language models, including Universe 3.0, Universe 3.0 Pro, Universe 4.5, and others
Development ToolsProvides development toolkits including Python SDK, Java SDK, OpenAI-compatible interface, and more
Management PlatformProvides a console for account management, API Key management, usage statistics, and billing inquiries
Technical SupportProvides technical support channels including online documentation, FAQ knowledge base, and ticket system

1.2 Service Features

  1. Pay-As-You-Go: Charges are based on actual Token consumption, with no upfront fees or monthly commitments.
  2. Elastic Invocation: Flexibly scale your usage based on business needs without applying for resource quotas in advance (subject to rate limits).
  3. Multi-Model Selection: Offers models at different capability tiers to meet the requirements of various business scenarios.
  4. Compatible Interfaces: Provides invocation methods compatible with mainstream interface protocols, lowering the barrier to entry for developers.

2. Service Level Agreement (SLA)

2.1 Availability Commitment

We commit that the monthly availability of Universe API services shall be no less than 99.5%.

Availability is calculated as follows:

Monthly Availability = (Total Minutes in Month - Unavailable Minutes in Month) / Total Minutes in Month x 100%

Definition of Unavailable: A minute is considered unavailable if all your API requests within the same minute return 5xx error codes or experience connection timeouts. Service unavailability caused by the following reasons shall not be counted as unavailable time:

  • Scheduled system maintenance (announced 24 hours in advance);
  • Force majeure events;
  • Causes attributable to the User (e.g., expired API Keys, insufficient balance, malformed request formats, etc.);
  • Requests exceeding rate limits.

2.2 Service Compensation

If the monthly service availability falls below the committed standard, you may apply for service compensation via a support ticket in the following month:

Monthly AvailabilityCompensation Plan
99.0% - 99.5%Credit 5% of the month's spending to your account balance
95.0% - 99.0%Credit 15% of the month's spending to your account balance
Below 95.0%Credit 30% of the month's spending to your account balance

Compensation is issued as account balance and is not withdrawable as cash. Compensation claims must be filed within 30 days of the incident.

2.3 Performance Metrics

MetricDescription
Time to First Token (TTFT)Under normal network conditions, the first Token is typically returned within hundreds of milliseconds, depending on the model version and system load
ThroughputStable Token generation speed is guaranteed within rate limits
Concurrency SupportConcurrent invocation quotas are provided based on account tier

The above performance metrics are reference values. Actual performance may be affected by network conditions, request parameters, system load, and other factors.


3. Service Access and Usage

3.1 Access Methods

Access MethodDescription
HTTP APIRESTful-style HTTP interface supporting both streaming and non-streaming responses
Python SDKOfficial Python client library that encapsulates API invocation details
Java SDKOfficial Java client library, suitable for developers in the Java ecosystem
OpenAI-Compatible InterfaceCompatible with the OpenAI API invocation format, enabling quick migration and integration

For detailed access methods and code examples, please refer to the Interface Documentation.

3.2 Authentication Mechanism

  1. All API requests must include a valid API Key for identity authentication.
  2. API Keys should be transmitted via HTTP Headers or request parameters and must not be hardcoded in front-end code or public repositories.
  3. You may create, manage, and revoke API Keys in the console, with support for multiple Keys in parallel.

3.3 Rate Limits

To ensure service quality and fair usage, we impose the following limits on API invocations:

Limit TypeDescription
Request Rate Limit (RPM)Maximum number of requests allowed per minute
Token Rate Limit (TPM)Maximum number of Tokens allowed to be consumed per minute
Concurrent Request LimitMaximum number of requests being processed simultaneously

Specific limit quotas are determined by account tier and model version, as displayed in the console. To request a higher quota, you may apply through the console or contact our business team.


4. Data Security and Compliance

4.1 Data Security Commitment

  1. We employ industry-standard security measures to protect your data, including encryption in transit (TLS 1.2+), encryption at rest, and access controls.
  2. We implement strict data access permission management to ensure that only authorized personnel can access relevant data when necessary.
  3. We conduct regular security assessments and vulnerability scans to continuously improve our security capabilities.

4.2 Compliance Obligations

  1. We comply with applicable laws and regulations including the Cybersecurity Law of the People's Republic of China, the Data Security Law, the Personal Information Protection Law, and the Interim Measures for the Management of Generative Artificial Intelligence Services.
  2. If you use the Service to process personal information, you shall ensure that you have obtained lawful authorization from the relevant individuals and comply with applicable data protection laws and regulations.

4.3 Content Safety

  1. We perform content safety reviews on API inputs and outputs, intercepting or filtering content that violates laws and regulations.
  2. Content safety reviews may affect the response time or results of certain requests. You understand and accept this necessary mechanism.
  3. If you discover any content generated through the Service that is unlawful or non-compliant, please contact us promptly.

5. Service Changes

5.1 Model Version Management

  1. We reserve the right to add, update, or retire model versions in accordance with business development.
  2. Model capability updates are generally backward-compatible; however, we do not rule out output differences resulting from technical upgrades.
  3. Prior to retiring a model, we will notify users via platform announcement at least 30 days in advance and recommend migration to a suggested alternative version.

5.2 Interface Changes

  1. Material changes to the interface (e.g., request/response format adjustments, parameter deprecations, etc.) will be communicated with at least 30 days advance notice.
  2. Compatibility fixes (bug fixes) and minor optimizations may be released at any time without prior notice.
  3. Developers are encouraged to subscribe to our changelog to stay informed of interface changes.

5.3 Price Adjustments

  1. Product prices may be adjusted in response to market and technological developments.
  2. Price changes will be communicated via platform announcement at least 15 days in advance.
  3. Continued use of the Service after a price adjustment constitutes your acceptance of the new pricing. For detailed pricing information, please refer to the Product Pricing page.

6. Incident Handling and Support

6.1 Incident Response

Incident LevelDefinitionResponse Time
P1 - CriticalService is completely unavailable, affecting all usersResponse within 15 minutes, with continuous progress updates
P2 - MajorCore functionality is impaired, affecting the majority of usersResponse within 30 minutes
P3 - MinorNon-core functionality is abnormal, affecting some usersResponse within 2 hours
P4 - TrivialMinor issues that do not affect core functionalityResponse within 24 hours

6.2 Support Channels

ChannelDescription
Online DocumentationComprehensive API documentation, SDK documentation, and best practice guides
FAQCompilation of common technical issues and solutions, see FAQ
Ticket SystemLog in to the console to submit a technical support ticket for assistance from professional engineers
Emergency ContactEnterprise customers can access emergency support through their dedicated service channel

6.3 Incident Notification

  1. When a service incident occurs, we will promptly notify affected users via console announcements, email, or SMS.
  2. After the incident is resolved, we will publish an incident report detailing the cause, scope of impact, and corrective measures.

7. Enterprise Customer Services

7.1 Enterprise-Exclusive Services

Enterprise customers may enjoy the following value-added services (subject to a separate enterprise service contract):

ServiceDescription
Dedicated Technical SupportAssigned a dedicated technical manager providing one-on-one technical support
Customized SLANegotiate higher availability commitments and more favorable compensation plans based on business needs
Priority ResponsePriority ticket handling with rapid response for urgent issues
Custom BillingNegotiated preferential pricing for high-volume usage, with support for corporate bank transfers and periodic settlement
Compliance SupportProvision of data security assessment reports, compliance certification materials, and more

7.2 Corporate Services

  1. Enterprise users requiring VAT invoices should submit an invoicing request through the console or contact our business team.
  2. Corporate payment methods such as bank transfers and bank acceptance are supported. Specific settlement terms are subject to the enterprise service contract.

8. Disclaimers and Limitation of Liability

8.1 Service Disclaimer

  1. Model outputs provided by Universe API are automatically generated by artificial intelligence. We do not guarantee the accuracy, completeness, applicability, or non-infringement of the output content.
  2. You should independently evaluate and verify model outputs. Any decisions made based on the outputs are at your own risk.
  3. We do not commit that the Service will be uninterrupted or error-free. Please refer to the Service Level Agreement (SLA) section for details.

8.2 Limitation of Liability

  1. To the maximum extent permitted by applicable law, we shall not be liable for any indirect, incidental, special, or consequential damages arising from the use of or inability to use the Service.
  2. Our total liability to you shall not exceed the total fees you have actually paid for the relevant service in the 12 months preceding the claim.
  3. The above limitations do not apply to direct losses caused by our intentional misconduct or gross negligence.

9. Breach and Termination

9.1 Breach Handling

If you violate any provision of this Agreement, we reserve the right to:

  1. Issue a warning notice requiring corrective action within a specified period;
  2. Suspend or restrict certain service features;
  3. Suspend or terminate your account;
  4. Pursue legal remedies and claim compensation.

9.2 Service Termination

  1. Termination by User: You may stop using the Service and deregister your account at any time. Termination takes effect immediately.
  2. Termination by Service Provider: We may suspend or terminate the Service to you under the following circumstances:
    • You violate the terms of this Agreement;
    • Your account poses security risks or exhibits abnormal behavior;
    • As required by laws, regulations, or regulatory authorities;
    • The Service is discontinued entirely.

9.3 Consequences of Termination

  1. Upon termination of the Service, API Keys become immediately invalid and the API service ceases to respond.
  2. You should back up any relevant data in your account in a timely manner.
  3. We reserve the right to delete your account data 30 days after termination (unless otherwise required by applicable laws and regulations).
  4. Account balance shall be handled in accordance with this Agreement and the platform's refund policy.

10. Governing Law and Dispute Resolution

  1. The formation, validity, interpretation, performance, and dispute resolution of this Agreement shall be governed by the laws of the People's Republic of China (excluding the laws of Hong Kong, Macau, and Taiwan).
  2. Any disputes arising from or in connection with this Agreement shall first be resolved through amicable negotiation between the parties.
  3. If no resolution is reached through negotiation, either party shall have the right to file a lawsuit with the competent People's Court in our jurisdiction.

11. Miscellaneous

  1. Entire Agreement: This Agreement, together with the "User Agreement" and "Privacy Policy," constitutes the entire agreement between the parties regarding the use of the Service.
  2. Severability: If any provision of this Agreement is found to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.
  3. Assignment: We reserve the right to assign our rights and obligations under this Agreement to affiliated companies or third parties. You may not assign your rights and obligations under this Agreement without our prior written consent.
  4. Waiver: Our failure or delay in exercising any right under this Agreement shall not constitute a waiver of such right.
  5. Force Majeure: If a party is unable to perform its obligations under this Agreement due to force majeure, the affected party shall not be held liable for breach, provided that it promptly notifies the other party and takes reasonable measures to mitigate losses.

Contact Us

If you have any questions or suggestions regarding this Service Agreement, please contact us through the following channels:

  • Platform Console: Log in to the console and submit a support ticket
  • Technical Support: Refer to the FAQ for assistance

Thank you for choosing Universe API. We look forward to building the future of AI applications together with you!