User Agreement

By registering an account, signing in, purchasing credits, generating API traffic, opening a support request, or otherwise using XVAPI, you agree to this User Agreement and the related public legal pages referenced by the service.

This agreement governs the customer-facing service only. Internal routing strategies, private provider relationships, incident handling techniques, and non-public operational tooling are not part of the public service contract unless expressly stated on the site.

XVAPI is not currently offered in mainland China. Before registering, accessing, or using the service, you must independently confirm that your location, actual place of use, and use of the service comply with applicable law, regulatory requirements, and the published service scope.

By continuing to register, access, or use XVAPI, you confirm that you have read, understood, and agreed to this section. XVAPI may adjust its service regions and service scope in response to operational arrangements, applicable law, or service capacity, with notice published on the website or by another reasonable means.

You are responsible for maintaining accurate registration details, safeguarding account credentials, protecting API keys, and controlling access to any two-factor authentication methods or linked sign-in providers tied to your account.

You must not share credentials with unauthorized users, embed private keys in public client code, sell or transfer access without authorization, or attempt to bypass package controls, billing protections, or access restrictions enforced by the platform.

XVAPI provides a public request layer and a customer account system published under https://api.xvapi.com/v1. The service may expose API access, a wallet-based billing model, account management features, and support channels depending on the current product scope.

Model availability, supported features, and request behavior may depend on upstream systems and platform routing rules. Those dependencies do not create a public promise that every internal upstream path, hidden route, or fallback method will remain visible or continuously available.

The platform may require sufficient prepaid balance before requests are accepted. Available balance may be reserved before processing and finalized after actual usage, completion status, or downstream cost has been determined.

Wallet changes, credit purchases, usage charges, releases, manual adjustments, and refunds where supported are recorded against the account ledger and related billing records. Public pricing pages, package rules, and billing surfaces describe the customer-visible settlement model that applies at the time of use.

You may not use XVAPI to attack the platform, automate abusive request patterns, interfere with other customers, scrape protected areas, evade billing, conceal fraudulent payment activity, probe unpublished internals, or violate applicable law or third-party rights.

You may not attempt to obtain internal provider credentials, hidden route identifiers, confidential infrastructure details, or other private operational information that is not part of the documented customer-facing service.

The service may evolve over time. Model coverage, pricing, quotas, package access, support processes, and security controls may be updated when reasonably necessary for maintenance, stability, product changes, operational safety, or commercial adjustments.

Where reasonably possible, customer-visible integration paths and published billing rules should remain stable. However, XVAPI may modify limits, plans, product scope, or operational policies without preserving undocumented assumptions.

Service issues, billing questions, and account concerns should be submitted through the official support channel, currently ops@xvapi.com, or through the built-in support workflow where available.

The operator may review request records, payment references, support history, and relevant security logs to investigate service incidents, suspected abuse, settlement disputes, and account recovery requests.

XVAPI may suspend, throttle, restrict, or terminate access where necessary to address unpaid balances, abnormal behavior, misuse, security threats, policy violations, platform abuse, legal demands, or operational risks affecting other users or the service as a whole.

Suspension decisions may be applied automatically or manually. Restoration of access may require further review, additional verification, payment resolution, or explicit operator approval.

The service is provided on an operational basis. Availability, latency, model quality, request success rate, and downstream behavior may be influenced by infrastructure dependencies, upstream providers, payment systems, maintenance work, or emergency controls.

Nothing in the public service should be interpreted as a guarantee that hidden infrastructure, unpublished model routing, or private continuity mechanisms will remain unchanged, exposed, or available indefinitely.

This agreement may be updated from time to time as the product, platform architecture, pricing model, legal obligations, or support processes evolve.

Continued use of XVAPI after an updated agreement becomes effective constitutes acceptance of the revised terms.