Terms of Service
Draft — not final terms
This page is a structured placeholder for legal review. It does not identify the final contracting entity, governing law, effective date, or complete commercial terms and must not be published as a binding agreement until those fields are approved.
1. Agreement and operator
These terms will govern access to NexoAI's dashboard, prepaid wallet, virtual keys, and API gateway. The final version must identify [Legal entity name], its registered address, an effective date, and the users or organizations eligible to accept the agreement.
2. Accounts and credentials
Users are responsible for accurate registration information, access to their dashboard account, and every virtual key created under that account. API keys must be stored as secrets. Activity authenticated by a key may be attributed to the account until the key is revoked.
The final terms should state the age or authority requirements for account creation and the process for reporting an unauthorized account or compromised key.
3. Prepaid wallet and payments
NexoAI operates a prepaid USD wallet with top-ups paid in MAD through supported local payment rails. There is no subscription. The final terms must explain:
- when a top-up becomes available as wallet credit;
- the quote or conversion information shown before a MAD payment;
- expiration, if any, of promotional and purchased credit;
- treatment of failed, duplicate, reversed, or disputed payments;
- refund eligibility for unused and consumed credit;
- applicable taxes, fees, invoices, and payment-provider terms.
The $10 sign-up credit is promotional value and should have separate eligibility and expiry language if those restrictions apply.
4. API access and limits
Users may create named virtual keys and optionally apply RPM, TPM, and budget caps. Those controls reduce risk but do not replace account security. NexoAI may also enforce platform limits needed for reliability, safety, legal compliance, or upstream availability.
Model availability, latency, output, context limits, and pricing can change. The dashboard catalog should be identified as the current source for model IDs and rates.
5. User content and outputs
The final terms must define user prompts, uploaded material, tool results, and model outputs; explain the permissions needed to process them; and allocate responsibility for reviewing model output before use. Users should not assume that generated output is accurate, unique, lawful, or suitable for high-impact decisions.
6. Acceptable use
Use of NexoAI is subject to the Acceptable Use Policy. The final terms should allow investigation, throttling, suspension, or termination when activity threatens users, the service, upstream providers, or applicable law, with notice and appeal language where appropriate.
7. Availability and changes
The gateway depends on software, networks, payment rails, and upstream model providers. The final agreement must describe service availability without promising uninterrupted access, the process for material changes, and any commitments that apply to paid enterprise arrangements.
8. Suspension and termination
The final version should cover user-initiated account closure, NexoAI-initiated suspension, access to records after closure, treatment of remaining wallet credit, and the provisions that survive termination.
9. Disclaimers and liability
Counsel must supply jurisdiction-appropriate warranty disclaimers, liability limits, exclusions, indemnity language, and exceptions that cannot legally be waived. Do not infer those provisions from this placeholder.
10. Disputes and contact
Before publication, add the governing law, venue or dispute process, required notices, legal contact, and support contact. Operational support should be reachable through the dashboard without asking users to disclose API keys.