Enterprise Team Purchase and Service Agreement

Latest Version Effective Date: July 8, 2026

[Important Notice]

Welcome to entering into this MaiToken Platform Enterprise Team Purchase and Service Agreement (hereinafter referred to as "this Agreement") with Fujian Meer Network Technology Co., Ltd. (hereinafter referred to as "Meer" or "we").

Before you apply to activate enterprise team services, create team sub-accounts, or purchase related quotas, please be sure to read carefully and fully understand the contents of each clause of this Agreement, especially clauses exempting or limiting liability, governing law, and dispute resolution clauses (usually identified in bold or underlined).

This Agreement serves as a special supplementary agreement subordinate to the MaiToken Platform User Agreement and the MaiToken Platform Privacy Policy. Matters not covered in this Agreement shall be governed by the User Agreement and Privacy Policy; if there is any conflict or inconsistency between this Agreement and the User Agreement and Privacy Policy, the provisions of this Agreement shall prevail with respect to enterprise teams, sub-account management, and wallet sharing services.

I. Definitions

1. Enterprise Primary Account (Primary Account): Refers to an account that has completed real-name enterprise verification on the MaiToken Platform and holds supreme control permissions including team management, quota recharge, member authorization, and API Key management.

2. Team Sub-account (Sub-account): Refers to a member account invited, created, and authorized by the Enterprise Primary Account through the platform dashboard. A sub-account may share and consume the wallet quota of the primary account within the scope of permissions configured by the primary account.

3. Shared Wallet Quota (Shared Wallet/Quota): Refers to the funds, tokens, or call count limits uniformly recharged or purchased by the Enterprise Primary Account for calling aggregated API interfaces of the MaiToken Platform.

4. API Key (Interface Key): Refers to an identity credential used to invoke platform API services. Both the primary account and authorized sub-accounts may generate and manage API Keys.

II. Account Creation, Verification, and Team Management

1. Enterprise Real-Name Verification: When applying to activate enterprise team services, you must provide a true and valid enterprise business license, Unified Social Credit Code, corporate bank account information (if any), or identity documents of the legal representative to complete enterprise real-name verification. The operator submitting the verification application must be a legally authorized representative of such enterprise or entity.

2. Creation and Authorization of Sub-accounts: The Enterprise Primary Account has the right to invite or create sub-accounts to join the team by entering mobile phone numbers, email addresses, etc., in accordance with platform rules. The primary account may independently assign different management permissions to different sub-accounts (e.g., whether to permit generating API Keys, viewing team bills, sub-inviting members, etc.).

3. Joint Liability and Attribution of Actions: All actions of team sub-accounts on the MaiToken Platform (including but not limited to API calls, generation and leakage of API Keys, data input, balance consumption, service subscriptions, modifications of service configurations, etc.) shall be deemed as overall actions of the enterprise user. All legal consequences, financial liabilities, and breach of contract liabilities arising therefrom shall be borne by the enterprise user (i.e., the legal entity holding the primary account).

III. Shared Wallet and Quota Settlement Rules

1. Quota Sharing Mechanism: Enterprise team services adopt the model of "unified payment by the primary account, joint consumption by sub-accounts". Fees incurred by sub-accounts calling platform APIs will be directly deducted in real time from the shared wallet balance of the Enterprise Primary Account.

2. Quota Limits and Rate Limiting Configuration: The Enterprise Primary Account may configure daily, weekly, monthly, or single consumption limits for individual sub-accounts or individual API Keys through the platform management dashboard. If sub-accounts or specific API Keys are maliciously spammed or excessively consume wallet balances due to the enterprise's failure to reasonably configure the aforementioned limits, the relevant losses shall be borne solely by the enterprise user, and Meer assumes no liability for refunds or compensation.

3. Prepayment and Arrears Processing: Platform API services generally adopt a prepaid recharge model. When the shared wallet balance of the Enterprise Primary Account falls to zero or a set warning threshold, the platform has the right to immediately suspend the API call permissions of the primary account and all sub-accounts. Losses resulting from business interruptions due to arrears shall be borne solely by the enterprise user.

4. Refund Policy: Except where services are completely unusable due to Meer's subjective intentional misconduct or material breach of contract, or where expressly prescribed by law, quota packages on an annual or monthly subscription basis that have already been recharged, consumed, or purchased by the Enterprise Primary Account do not support refunds, cash withdrawals, or transfers.

IV. API Key Security and Management Standards

1. API Key Generation Permissions: The Enterprise Primary Account must strictly manage permissions for sub-accounts to generate, view, and export API Keys. In non-essential circumstances, it is recommended to restrict sub-accounts' API Key creation permissions.

2. Custody and Leakage Prevention Obligations: Enterprise users must establish a sound API Key security custody mechanism. API Keys must not be written in plaintext into client-side code, public open-source repositories (such as GitHub), or transmitted via unencrypted instant messaging tools.

3. Attribution of Leakage Liability: If an API Key under the primary account or a sub-account is leaked due to improper internal management of the enterprise, employee negligence, or third-party attacks, resulting in the theft, unauthorized consumption of shared wallet balances, illegal calls, or additional billing, such bills and losses shall be fully borne by the enterprise user. Meer has the right (but not the obligation) to implement risk control measures such as temporarily freezing or resetting the API Key upon detecting anomalous traffic.

V. Data Privacy, Information Sharing, and Security Compliance

1. Internal Team Data Visibility: You understand and agree that, as the owner and administrator of the team, the Enterprise Primary Account has the right to inspect, export, and audit call logs, call frequencies, consumed amounts, partially desensitized input/output logs (if any) of all sub-accounts, as well as basic information of sub-accounts (such as bound mobile phone numbers/emails). A sub-account joining a team is deemed to have expressly consented to sharing such information with the primary account.

2. Call Compliance Warranties: Enterprise users must ensure that data entered by all sub-accounts when using API services (including text, images, audio, documents, etc.):

• Does not contain any state secrets, endanger national security, or violate applicable laws and regulations;
• Does not infringe upon any third party's intellectual property rights, trade secrets, privacy rights, or other legitimate rights and interests;
• If involving personal information of end users, enterprise users must ensure that lawful authorization from end users has been obtained in accordance with law.

3. Downstream Compliance Governance: Where enterprise users utilize MaiToken Platform APIs to develop and provide products or services to their end users, enterprise users must be independently responsible for the security and compliance governance of their downstream applications (including but not limited to content security filtering, sensitive word interception, algorithm filing, etc.). If Meer is penalized by regulatory authorities or sued by third parties due to violations by an enterprise's downstream applications, the enterprise user shall compensate Meer for all losses.

VI. Suspension and Termination of Services

1. Platform Proactive Intervention: If Meer discovers that the Enterprise Primary Account or any sub-account exhibits any of the following circumstances, Meer has the right, without prior notice, to directly adopt measures including restricting call frequencies, disabling specific API Keys, suspending or canceling partial/all sub-accounts, up to terminating services for the Enterprise Primary Account:

• Violating this Agreement, User Agreement, Privacy Policy, or laws and regulations;
• Suspected of utilizing APIs for malicious scanning, attacks, spamming, reverse engineering, or developing competitive products;
• Suspected of fraud, money laundering, or being reported for violations by regulatory authorities.

2. Cancellation and Termination: When an Enterprise Primary Account applies to cancel the team or terminate services, it must first unbind or cancel all sub-accounts under its name and settle all outstanding bills. After the primary account is canceled, all associated sub-accounts will automatically lose team attributes, and relevant shared wallet quotas and API call histories will be cleared or anonymized in accordance with law.

VII. Limitation of Liability

1. Upstream Service Dependency Disclaimer: You understand and agree that the MaiToken Platform is an API aggregation platform whose service stability and model output quality depend heavily on domestic and foreign third-party large model service providers (including but not limited to OpenAI, Anthropic, and domestic model vendors). For service fluctuations, interruptions, or call failures caused by non-intentional factors of Meer such as policy adjustments, interface changes, service suspensions, or IP blocks by upstream service providers, Meer shall not assume business interruption losses, indirect losses, or punitive damages brought to the enterprise.

2. Compensation Cap: To the maximum extent permitted by applicable law, where direct losses are caused to an enterprise user due to Meer's breach of contract, Meer's cumulative total liability for compensation to the enterprise user shall not exceed the total API call service fees actually paid by the Enterprise Primary Account to the MaiToken Platform within the three months prior to the occurrence of the claim event.

VIII. Governing Law and Dispute Resolution

1. Governing Law: The conclusion, effectiveness, interpretation, amendment, termination, and dispute resolution of this Agreement shall be governed by the laws of mainland China (the People's Republic of China).

2. Jurisdiction Court: Any dispute arising from your use of MaiToken Platform enterprise team services and related to this Agreement shall first be resolved through friendly negotiation between the parties; if negotiation fails, either party may file a lawsuit with the People's Court having jurisdiction in the domicile of Fujian Meer Network Technology Co., Ltd. (i.e., the People's Court of Yongding District, Longyan City).

IX. Miscellaneous

1. Severability: If any provision of this Agreement is held to be invalid or unenforceable, it shall not affect the validity and enforceability of the remaining provisions of this Agreement.

2. Agreement Amendments: Meer has the right to amend this Agreement from time to time in accordance with business development, technological iterations, and changes in laws and regulations. The revised agreement will be published on the MaiToken Platform or notified to the primary account via platform inbox messages/emails. If an enterprise user continues to use team services after amendments take effect, it shall be deemed as agreeing to and accepting the revised agreement.