Cloud API Terms of Service
Last updated: September 29, 2026
Applies to: partners using Cloud API on the AdaptGroup platform.
1. General
Cloud API is provided by AdaptGroup LLC, registered in Wyoming, USA (the "Company"), as part of the AdaptGroup platform (the "Platform").
The service enables a partner to order and manage server resources from its own application, website, or another system. Available resources, plans, and operations are determined by the catalog, integration settings, and API technical documentation.
The partner develops and maintains its interface and arranges payments and support for its customers. The Company provides infrastructure and Cloud API. Administration of the customer's operating system and applications is not included unless separately agreed.
2. Related Documents
Connection to and use of Cloud API are subject to the Platform terms and this document. Ordered resources are also subject to:
- Infrastructure Terms — resource provision, payment, renewal, and termination of rental.
- AUP — acceptable use, complaints, and restrictions.
- SLA — server availability and compensation.
- DPA — processing personal data on the customer's behalf, where applicable.
- Copyright Complaints / DMCA Policy.
General account and organization rules are set out in the Platform Public Offer and Organization Terms. Processing for the Platform's own purposes is described in the Privacy Policy.
These terms govern Cloud API orders and payments; the Infrastructure Terms govern rental. The partner must not promise terms on the Company's behalf that have not been agreed with it. Mandatory rights under applicable law remain unaffected.
3. Integration and Access Credentials
The partner creates an integration in the dashboard and uses the provided authorization credentials. The integration key must be stored in a trusted server-side system; it must not be placed in public code or a browser application or given to customers as a personal key.
The partner is responsible for permissions of its organization members and its own system users, safeguarding credentials, and promptly replacing compromised keys. Upon detecting unauthorized access, it must restrict that access and notify support.
A customer identifier in a request does not, by itself, establish entitlement to a resource. The partner must check user permissions in its own system and prevent one customer from accessing another customer's servers, IP addresses, or order information.
4. Catalog, Prices, and Availability
The partner's operation costs are determined by current prices and integration settings. The partner must obtain current pricing before a paid operation and account for it when setting its own customer price.
The partner independently sets payment terms for its customers in compliance with the law and applicable Infrastructure Terms. Cloud API does not replace its payment collection system or confirm receipt of payment from the end customer.
Availability figures are calculated estimates as of their update time and do not reserve resources. Several plans may draw on the same equipment and address stock; their quantities must not be treated as independent inventories. Final fulfilment is checked during order processing.
Before payment, the customer must have access to resource specifications, location, rental term, renewal terms, IP addresses, traffic, additional charges, and material restrictions. CPU share must not be described as dedicated physical cores unless that service is actually provided.
Infrastructure price changes and renewal prices are governed by the Infrastructure Terms. The Company announces price increases at least seven days in advance in the Telegram channel @adapt_cloud_alert. A new price does not alter the cost of an already paid period. The partner must take account of these notices and communicate applicable changes to customers.
5. Integration Balance and Paid Operations
Paid Cloud API operations are funded from the relevant integration's balance. This is accounted for separately from the organization balance; funds in the organization do not, by themselves, mean those funds are available to pay for an API order.
When a paid order is accepted, its amount is deducted from the integration balance. The charge may precede completion of the technical operation. If funds are insufficient, the paid operation is not performed unless otherwise agreed with the Company.
A balance top-up is not an order, rental renewal, or equipment reservation. The partner must monitor available funds and payment deadlines for its resources.
Settlement between the Company and the integration and settlement between the partner and its customer are distinct operations. Refunding an integration balance does not automatically refund the customer in the partner's system.
6. Orders and Asynchronous Processing
An order acceptance response means processing has started, not that a server is ready or another action completed. The partner must retain order identifiers and check final status through available API methods and notifications.
A dedicated server may require manual preparation. The start of the paid period is governed by the Infrastructure Terms; waiting for preparation must not be presented to the customer as completed delivery.
When retrying a request, the partner must follow the idempotency rules in the technical documentation. If no response is received, it should check the earlier order rather than create a new paid order without establishing the outcome.
Resource changes, reinstallation, deletion, IP address operations, and other actions are performed within available functionality. The partner must obtain any necessary customer confirmation and explain material consequences: possible restarts, network configuration changes, and data loss. Acknowledgement of a request does not replace confirmation that it was carried out.
7. Errors, Outcome Verification, and Refunds
If it is confirmed that a paid order was not fulfilled and the resource or additional service was not provided, the corresponding charge must be refunded to the integration balance. Confirmed erroneous and duplicate charges must also be corrected.
An order with an uncertain outcome, partial completion, or a need for verification may be referred for review. An error or timeout is insufficient to conclude that no resource exists: for example, an IP address may already be allocated even though subsequent configuration failed. The partner must account for review status and must not treat every unsuccessful response as confirmation of a refund.
For review, the partner supplies support with the order or resource identifier and the circumstances of the error without disclosing unnecessary secrets. Once the actual outcome is established, the Company corrects confirmed errors in the order or billing.
Voluntary cancellation of a properly provided service after use does not entitle the customer to a refund for the remaining period, except where required by law. Unavailability compensation is governed by the SLA, and consequences of violations by the AUP. Additional commitments independently made by the partner to a customer do not automatically become Company obligations.
8. Renewal and Notifications
The partner manages renewal using available API methods. Automatic renewal applies only when the relevant feature is enabled. It requires a sufficient balance and a successful operation at the current price; enabling the setting alone does not guarantee payment.
Separately billed IP addresses may have their own expiry dates, different from the server's. The partner must account for them in billing and customer notifications. Non-payment and resource release consequences are governed by the Infrastructure Terms.
To receive webhooks, the partner supplies an accessible endpoint and verifies notification authenticity according to the technical documentation. The handler must account for possible duplicates, delays, and out-of-order delivery.
A webhook does not replace the ability to query the current order or resource status. The partner must verify uncertain outcomes and must not make expiry of the paid period depend solely on receipt of a reminder. Unavailability of the partner's handler does not, by itself, extend rental.
9. Data and Customer Relations
The partner ensures lawful transmission of data to Cloud API, informs customers about processing and transfers, and restricts staff access. Only information needed to fulfil the order and service the resource should be submitted through the API.
Passwords, SSH keys, and console links are provided only to authorized users. API access does not give the partner or the Company an unrestricted right to inspect the customer's files or operating system contents. Access is governed by the Infrastructure Terms and DPA.
The partner supports customers using its system and refers infrastructure technical questions to Company support. It must promptly forward resource-related violation notices and assist with complaints under the AUP and Copyright Complaints Policy.
10. Restriction and Termination of an Integration
The partner complies with authorization requirements, request limits, and other technical documentation rules. Circumventing restrictions, unauthorized access, and activities that disrupt the Platform or other parties' resources are prohibited.
If a key is compromised or activities pose a threat, the Company may restrict integration access to protect resources. Restricting API access, suspending an individual server, and permanently ending a rental are distinct measures; grounds for and consequences of resource restrictions are governed by the common documents.
Disabling an integration or replacing its key does not cancel accepted orders, existing obligations, or resource payment deadlines. Before ending operations, the partner must resolve incomplete transactions and continued customer service through support. Resources are not assumed to transfer automatically to another integration.
The server SLA does not provide a separate availability guarantee for the API or the partner's application. Interface unavailability does not, by itself, cancel the Company's obligations for infrastructure already provided.
11. Changes to Terms and Contacts
Changes to these terms are published in Platform documentation. Price changes follow the notification requirements and protection of paid periods specified in the Infrastructure Terms.
- Support: [email protected], @adapt_support.
- Abuse complaints: [email protected].
- Partnership and business proposals: [email protected].
AdaptGroup LLC
30 N Gould St Ste R, Sheridan, WY 82801, USA.