Nexus Terms of Service¶
Effective as of August 15, 2026
1. General Provisions and Acceptance¶
1.1. These Terms of Service (the “Terms”) govern the use of Nexus, including the API, Telegram bot, web interfaces, documentation, support and related functionality (collectively, the “Service”).
1.2. “Nexus Administration” or the “Administration” means the persons responsible for operating, maintaining and developing the Service. References to the Administration do not represent that Nexus is a legal entity or an incorporated organization in any particular jurisdiction.
1.3. A “User” is any person who uses the Service, accesses its functionality, creates or uses a profile or API key, adds funds to a balance or otherwise interacts with Nexus.
1.4. By starting or continuing to use the Service, including starting the Telegram bot, using the /start command, creating a profile or API key, adding funds or sending an API request, the User confirms that they have reviewed and accepted these Terms. If the User does not agree, the User must stop using the Service.
1.5. The User confirms that they have the legal capacity and authority required to accept these Terms. If the User acts on behalf of an organization or another person, the User confirms that they have authority to do so.
2. Service Description¶
2.1. Nexus provides technical infrastructure for access to supported AI models and related API functionality, together with tools for managing access, API keys, balances, payments, transaction history, support and other functionality available through the Service.
2.2. Nexus may provide compatibility with interfaces, formats and client applications of third parties. References to third-party names, APIs or trademarks describe technical compatibility or functionality and do not by themselves imply partnership, endorsement, ownership or an official relationship with the relevant rights holder.
2.3. The available models, endpoints, functionality, limits, payment methods and features may change. Current availability is determined by the Service interface, API, documentation and actual technical availability at the relevant time.
2.4. Unless expressly agreed otherwise, Nexus does not provide an SLA and does not guarantee continuous availability of any specific model, endpoint, provider, feature or performance level.
3. Profiles and API Keys¶
3.1. To use certain Nexus functionality, the User may receive a profile, Nexus ID, API keys or other access credentials.
3.2. An API key is a confidential access credential. The User must take reasonable steps to prevent disclosure, publication, unauthorized sharing or unauthorized use of the key.
3.3. The User is responsible for activity performed using an active API key or other credential belonging to the User unless the User has notified Nexus of suspected compromise and unless the activity resulted from a security failure attributable to Nexus.
3.4. The Administration may revoke, replace, restrict or temporarily suspend an API key where reasonably necessary for security, abuse prevention, mitigation of technical risk, enforcement of Service limits or protection of the User and the infrastructure.
3.5. Multiple API keys do not create separate monetary obligations of Nexus to the User for each key. Where the Service indicates that balance is maintained at profile level, the keys associated with that profile share the same balance.
4. User Content and AI Outputs¶
4.1. The User retains any rights the User has in data, prompts, instructions, files and other content submitted through the Service and grants Nexus only the rights to technically process and transmit that content as necessary to operate the Service and perform the request.
4.2. The User represents that the User has the right to submit the relevant content and that its use through Nexus does not violate third-party rights, confidentiality obligations or applicable mandatory requirements.
4.3. Responses and other outputs may be generated by third-party AI models. Such outputs may be inaccurate, incomplete, outdated, unpredictable or erroneous. Nexus does not verify their accuracy and does not guarantee any specific outcome.
4.4. The User is responsible for evaluating whether an output is suitable for the User’s purpose. The User should not rely on an AI output as the sole source of professional legal, medical, financial, technical, safety-critical or other materially important information without appropriate independent verification.
4.5. Nexus does not claim ownership of the User’s original content. The legal status of AI-generated outputs may depend on the nature of the output, applicable law and the terms of the relevant technologies or third parties.
5. Acceptable Use¶
5.1. The User must use the Service in good faith and in accordance with applicable mandatory requirements, third-party rights and Nexus technical limits.
5.2. In particular, the User must not:
- obtain unauthorized access to accounts, keys, systems or data;
- bypass or attempt to bypass authentication, billing, quotas, model restrictions, rate limits, security controls or technical restrictions;
- use the Service for attacks, malware, disruption of systems, bulk spam, fraud or other knowingly unlawful conduct;
- create excessive or artificial load that may disrupt Nexus or its providers;
- use stolen, unauthorized or otherwise compromised credentials;
- impersonate Nexus, the Administration or an official Nexus representative without permission;
- interfere with the Service, probe protected internal mechanisms, or attempt to extract secrets, keys, internal routes or other non-public information beyond ordinary authorized API use.
5.3. Commercial use of Nexus outputs is not prohibited by these Terms by itself. However, sharing, publishing or reselling API keys or access credentials without the Administration’s permission is prohibited.
5.4. The Administration may apply technical restrictions and protective measures to prevent abuse even where a particular pattern is not expressly listed above, where there are reasonable grounds to consider the User’s conduct harmful to the Service, users or third parties.
6. Balance, Pricing and Billing¶
6.1. A Nexus balance is an internal accounting unit used to pay for Service functionality. It is not a bank account, deposit, electronic wallet or financial product provided by Nexus.
6.2. Charges are determined by the pricing shown in the Service or documentation. Depending on the model and functionality, charges may be based on actual usage, token counts, separate usage categories, a fixed per-request amount or another clearly disclosed billing unit.
6.3. The Administration may change prices, calculation methods, available pricing plans and payment methods prospectively. Unless the Service states otherwise, a new price applies to operations and API requests started after the relevant change takes effect.
6.4. Billing depends on technical data available to the Service and the relevant API. If Nexus cannot reliably determine the information required for billing, an operation may remain uncharged. Nexus does not use hidden charges that are not disclosed to the User as part of the applicable billing model.
6.5. With multiple concurrent requests, final charges may be applied after processing begins. The displayed balance may therefore temporarily differ from amounts committed by already-started activity. Nexus may reject new requests where the balance is insufficient or a configured threshold has been reached.
6.6. Where prices are displayed in a currency other than the Service’s primary settlement currency, the display may be informational and may depend on an exchange rate or conversion source. The actual settlement unit is determined by the Nexus interface for the relevant operation.
7. Payments, Promotional Credits and Refunds¶
7.1. Payments may be processed by third-party payment providers. Their availability, processing times, fees, verification methods and separate restrictions may depend on the relevant provider and may be outside Nexus’s direct control.
7.2. The User must verify the payment amount and payment method before confirmation and must not use payment instruments belonging to another person or obtained without authorization.
7.3. Refund requests are reviewed by the Administration on a case-by-case basis, taking into account the reason for the request, actual use of the Service, payment status, technical error, duplicate transaction, fraud risk and applicable mandatory requirements.
7.4. Submitting a request does not automatically entitle the User to a refund. Properly delivered and correctly recorded Service usage is generally not refundable solely because the User changed their mind after using it, unless applicable mandatory law requires otherwise.
7.5. Unused paid balance may be refunded, transferred, adjusted or otherwise resolved at the Administration’s discretion or where required by applicable law. The Administration may request reasonable information to verify profile ownership, the payment and the circumstances of the request.
7.6. Promotional, bonus and goodwill credits may be subject to separate terms and, unless expressly stated otherwise, do not create a monetary obligation for Nexus to pay their nominal amount to the User. Credits obtained through error, abuse or fraud may be reversed or adjusted.
7.7. In the event of a payment dispute, the User is encouraged to contact Nexus support first. Initiating a chargeback or similar procedure may result in temporary restriction of payment functionality or Service access while the matter is reviewed, particularly where funds were already credited or related Service usage occurred.
7.8. Nexus may correct obvious accounting errors, duplicate transactions, amounts credited by mistake and consequences of payment reversals or cancellations. Such adjustments must relate to an actual transaction or confirmed technical error and are not intended to permit arbitrary changes to the User’s balance.
8. Availability, Changes and Technical Limits¶
8.1. The Service is provided on an “AS IS” and “AS AVAILABLE” basis unless expressly agreed otherwise.
8.2. The Administration does not guarantee uninterrupted, error-free or permanent operation, a particular speed, latency or throughput, availability of a particular provider, model or feature, or compatibility with every version of a third-party client.
8.3. Nexus may change internal infrastructure, routing, providers, compatibility methods, technical limits, endpoints, names and functionality without prior approval from the User, provided that such changes do not create retrospective charges for obligations that did not exist.
8.4. Availability may be limited due to maintenance, incidents, third-party provider actions, network restrictions, third-party API changes, blocking, force majeure events, security threats or other circumstances outside the Administration’s reasonable control.
8.5. Information shown on status pages, in notifications and in documentation is informational and does not by itself create a guaranteed SLA.
9. Suspension and Termination¶
9.1. The Administration may temporarily restrict, suspend or terminate access to an individual key, profile or the Service where reasonably necessary due to:
- violation of these Terms;
- a security threat or suspected compromise;
- fraud, a disputed payment or abuse of a payment system;
- an attempt to bypass billing, restrictions or security controls;
- excessive load or conduct affecting other users;
- a mandatory requirement, decision of a competent authority or a substantiated requirement of a payment or infrastructure provider;
- a need to prevent harm to Nexus, the User or third parties.
9.2. Where there is an urgent security threat, a restriction may be applied without prior notice.
9.3. Suspension does not by itself constitute automatic forfeiture of unused paid balance. The treatment of the balance depends on the reason for the restriction, actual charges and expenses, payment refunds or reversals, the outcome of any investigation, these Terms and applicable mandatory requirements.
9.4. The User may stop using the Service at any time. Stopping use does not cancel obligations and completed or pending operations that arose before termination.
9.5. The Administration may discontinue the Service or particular functionality. Any unused paid balance will be handled under the refund rules in effect at the time and applicable mandatory requirements.
10. Support¶
10.1. Nexus provides support through channels available in the Service. Unless a separate SLA is agreed, response and resolution times are not guaranteed.
10.2. The Administration may request technical information, a request ID, transaction data or other information reasonably necessary to diagnose and verify a support request. The User should not provide a full API key or other secret unless support expressly provides a secure method and explains why such disclosure is necessary.
10.3. Voluntary compensation, bonus credits, goodwill credits, exceptions to ordinary rules or other accommodations granted in a particular case do not create an obligation to provide the same accommodation in the future to other Users or to the same User.
11. Intellectual Property and Names¶
11.1. Rights in Nexus software, design, documentation, trade names, original text and other proprietary materials belong to their respective rights holders.
11.2. These Terms do not transfer ownership of Nexus, its infrastructure, internal tools, documentation or other protected elements to the User, except for the limited right to use available functionality in accordance with these Terms.
11.3. Third-party trademarks, model names and service names belong to their respective rights holders. Nexus references them for identification and compatibility unless expressly stated otherwise.
12. Disclaimer of Warranties¶
12.1. To the maximum extent permitted by applicable law, Nexus disclaims implied warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted availability and conformity with the User’s subjective expectations.
12.2. Nexus does not guarantee that use of the Service will result in profit, savings, a professional outcome, error-free results or compatibility with the requirements of a third-party product, provider or platform.
12.3. Any mandatory rights that cannot lawfully be excluded or limited remain unaffected by this section.
13. Limitation of Liability¶
13.1. To the maximum extent permitted by applicable law, the Administration and persons involved in operating Nexus are not liable for indirect, incidental, special, punitive or consequential losses, lost profits, lost anticipated savings, loss of data, loss of business opportunity or reputational harm arising from use of or inability to use the Service.
13.2. Nexus is not responsible for acts or omissions of third-party AI/API providers, payment systems, telecommunications operators, cloud or infrastructure providers, Telegram, third-party clients or other independent third parties where the relevant event is outside the Administration’s reasonable control.
13.3. To the maximum extent permitted by applicable law, the Administration’s aggregate liability for claims related to the Service is limited to the amount actually paid by the User to Nexus for use of the Service during the three months immediately preceding the event giving rise to the claim.
13.4. The limitations in this section do not apply to the extent that the relevant liability cannot be excluded or limited under applicable mandatory law.
14. User Responsibility¶
14.1. The User is responsible for the User’s requests, content, client configuration, handling of API keys, lawful use of outputs and compliance with these Terms.
14.2. To the maximum extent permitted by applicable law, the User agrees to reimburse the Administration for documented and reasonable losses and expenses arising from third-party claims directly caused by the User’s intentional unlawful use of the Service, infringement of third-party rights or material breach of these Terms.
15. Changes to the Terms¶
15.1. The Administration may update these Terms as the Service, technologies, pricing, risks and third-party conditions evolve.
15.2. The current version will be published through the Service or at a link made available to the User. Where reasonably practical, material changes may also be communicated through the Service.
15.3. Continued use of the Service after an updated version takes effect constitutes acceptance of the updated Terms. If the User does not agree with the changes, the User must stop using the Service.
16. Final Provisions¶
16.1. The Nexus Privacy Policy is related to these Terms and describes how information is processed within the Service.
16.2. If any provision of these Terms is found unenforceable or invalid, the remaining provisions continue in effect to the maximum extent permitted.
16.3. Failure by the Administration to exercise any right or remedy in a particular case does not waive that right or remedy in the future.
16.4. The Administration may transfer operation of the Service and related rights and obligations to a successor or another person in connection with a transfer, reorganization or continuation of Nexus, subject to reasonable preservation of Users’ basic rights in recorded balances and completed transactions. The User may not transfer access credentials or contractual position in a manner that violates these Terms or Service security.
16.5. Availability of Nexus in a particular country does not by itself mean that the Administration is established in that country, maintains a permanent establishment there or voluntarily submits to that country’s jurisdiction beyond the requirements of applicable law.
16.6. Before starting a formal dispute, the User is encouraged to contact support and give Nexus a reasonable opportunity to review the issue unless urgency or mandatory law requires another procedure.
17. Language Versions¶
17.1. These Terms may be published in Russian and English. Both versions are intended to convey the same meaning.
17.2. In the event of an inconsistency between language versions, the English version prevails to the extent permitted by applicable law.
18. Contact¶
18.1. Questions regarding use of the Service, payments, security and these Terms may be submitted to Nexus support through the communication methods available within the Service.