Public offer for the provision of access to the ApiMira service

1.1.This document is a public offer of the ApiMira service (hereinafter the Contractor) and contains all essential terms of the agreement for the provision of access to the ApiMira service (hereinafter the Agreement). The offer is addressed to any legally capable individual, sole proprietor or legal entity (hereinafter the Customer) in accordance with paragraph 2 of Article 437 of the Civil Code of the Russian Federation.

1.2.The offer is accepted by any of the following actions of the Customer: registering an account on the Site; activating a Top-up code or a Gift card; topping up the Balance by any other method available in the Dashboard. Acceptance means full and unconditional acceptance of all terms of the offer (paragraph 3 of Article 438 of the Civil Code of the Russian Federation). The Agreement is concluded at the moment of acceptance.

1.3.The current version of the offer is published at apimira.com/terms. Previous versions are provided by the Contractor on request.

Site

apimira.com with all its pages and subdomains.

Service

the ApiMira software complex: the application programming interface (API), the Dashboard and the related functions of the Site.

Dashboard

the section of the Site available to the Customer after signing in to the account.

API key

a unique string issued in the Dashboard that identifies the Customer when calling the API.

Model

a neural network model from the catalog on the “Models and prices” page.

Request

a call by the Customer to a Model through the API or the tools of the Site.

Token

the unit of data volume in which a Model counts incoming and outgoing text.

Generation

the billing unit of media models: an image, a second of video, a music track or a request.

Balance

the Customer’s account in the Service from which Requests are paid.

Top-up code

a unique single-use code of a certain face value which, when activated, credits that face value to the Balance.

Gift card

a Top-up code issued by the Customer in the Dashboard at the expense of their own Balance for transfer to another person.

Prices

the prices for using the Models, published on the “Models and prices” page.

3.1.For a fee, the Contractor provides the Customer with access to the Service: the ability to send Requests to Models through the API, receive Model responses and use the functions of the Dashboard.

3.2.The composition of the catalog, the capabilities of the Models and the Prices are published on the “Models and prices” page and may change in the manner set out in section 6.

3.3.The Models are created by their developers (for example, OpenAI, Anthropic, Google, DeepSeek). The Contractor is not a developer of the Models. The names of the Models and their developers are used on the Site only to designate the Models; trademarks belong to their owners.

3.4.The service for each Request is deemed rendered at the moment the Model’s response is formed and its cost is debited from the Balance. The volume of rendered services is confirmed by the operation history and statistics in the Dashboard. At the request of a Customer that is a legal entity or a sole proprietor, the Contractor issues closing documents for the reporting month.

4.1.To use the Service, the Customer registers an account with an email address and confirms it. The Customer provides accurate data and retains access to the specified email.

4.2.The Customer alone is responsible for keeping the password and API keys safe. All Requests made with the Customer’s API key are deemed made by the Customer and are paid from the Customer’s Balance.

4.3.If an API key leaks or is suspected to have leaked, the Customer pauses or revokes the key in the Dashboard. Charges for Requests made before the key was paused or revoked are not reimbursed.

4.4.Spending limits, access schedules and other restrictions of API keys are configured by the Customer. The Contractor may set technical limits on the frequency of Requests to protect the Service.

5.1.Services are provided on the basis of full prepayment. A Request is executed only if the Balance is sufficient; if funds are insufficient, the Request is declined without penalties or account blocking.

5.2.Prices and the Balance are denominated in US dollars. Payment is made in rubles at the exchange rate specified when purchasing a Top-up code (paragraph 2 of Article 317 of the Civil Code of the Russian Federation). Amounts in rubles and euros on the Site are shown for reference at the current rate.

5.3.The Balance is topped up with a Top-up code purchased in the official ApiMira store on the ggsel marketplace (the link is published on the Site), with a Gift card or by another method specified in the Dashboard. The face value is credited to the Balance immediately after the code is activated.

5.4.A Top-up code is activated once. If a code has an expiry date, it is specified at purchase. Gift cards do not expire.

5.5.The cost of a Request to a text Model is determined by the number of incoming and outgoing Tokens at the Price in effect at the moment of the Request. Outgoing Tokens also include reasoning Tokens if the Model uses them. A reduced rate applies to cached input if it is specified in the Price. The cost of a Request to a media model is determined by the price of a Generation.

5.6.Before executing a Request, the Contractor may temporarily reserve its estimated cost on the Balance. After the response, the actual cost is debited and the remainder of the reserve is returned to the Balance immediately.

5.7.If the Customer interrupts a Request before the response is complete, the volume actually processed and generated is paid for.

5.8.The remaining Balance does not expire and is not limited by a period of use.

5.9.The Contractor does not charge a fee for crediting funds. Fees of the marketplace and payment systems when purchasing a Top-up code are governed by their rules.

6.1.Prices are published on the “Models and prices” page per 1 million Tokens or per Generation.

6.2.The Contractor may unilaterally change the Prices, add Models to the catalog and remove them from the catalog. New Prices apply to Requests made after publication; amounts already debited are not recalculated.

6.3.A Model may be temporarily unavailable. Current availability is published on the “Server status” page. Only executed Requests are paid for.

7.1.The Contractor undertakes to:

• provide access to the Service on the terms of the offer;
• keep records of the Balance and show the Customer the operation history and Request statistics;
• consider the Customer’s requests to the support service;
• publish changes to the offer and the Prices on the Site.

7.2.The Contractor may:

• carry out maintenance, where possible announcing it in advance in the “Updates” section;
• suspend access to the Service or to an individual API key in case of a breach of the offer, signs of fraud, an attack on the Service or use that threatens the Service or third parties;
• decline a request to withdraw referral rewards in the cases set out in clause 10.3.

7.3.The Customer undertakes to:

• comply with the legislation of the Russian Federation and the terms of the offer;
• not use the Service to create and distribute prohibited materials, malicious code, spam, fraud and materials that infringe the rights of third parties;
• comply with the usage rules of the Models set by their developers;
• not attempt to circumvent accounting and billing, not disrupt the operation of the Service, and not carry out load testing or vulnerability research without the Contractor’s written consent.

7.4.The Customer may issue API keys, export statistics and the operation history, contact the support service and withdraw from the Agreement at any time.

8.1.The Customer alone is responsible for the content of Requests and for how the Model responses are used.

8.2.Responses are generated by the Models automatically and may be inaccurate, incomplete or erroneous. The Contractor does not review or edit responses and does not guarantee their fitness for the Customer’s purposes.

8.3.The Contractor claims no rights to the Customer’s Requests or the responses received.

8.4.The Contractor does not store the text of Requests and responses in the database, in logs or in analytics systems. Only metadata is stored: the Model, the number of Tokens, the cost, the time and the API key. To generate a response, the content of a Request is transmitted to the computing infrastructure on which the selected Model runs.

8.5.The Customer’s personal data is processed in accordance with the Privacy policy published on the Site.

9.1.The Customer may issue Gift cards in the Dashboard with a face value from 1 to 500 US dollars. The total face value is debited from the Balance at the moment of issue.

9.2.When activated, a Gift card tops up the recipient’s Balance by its face value. A Customer cannot activate their own Gift card or return its face value to their own Balance.

9.3.The Customer alone is responsible for passing on Gift card codes. An activated code cannot be restored or replaced.

10.1.The Customer may invite new users with the referral link from the Dashboard. For every top-up of the Balance by an invited user, the Customer is credited a reward of 5% of the top-up amount.

10.2.The reward is credited to the Balance. Accrued rewards can be withdrawn after the email address is confirmed: from 10 US dollars, in USDT on the TRC20 or BEP20 network. The network fee is deducted from the transfer amount. Payment is made within 7 days after the request is submitted.

10.3.The Contractor may decline a withdrawal request and cancel the reward in case of signs of abuse: self-invitations, fake accounts, top-ups followed by refunds. If a request is declined, the amount is returned to the Balance.

10.4.The Customer independently fulfils the tax obligations related to receiving the reward.

10.5.The Contractor may change the terms of the program or end it by publishing a notice on the Site. Rewards accrued before the change are retained.

11.1.The Customer may receive a refund of the full top-up amount within 10 days from the moment it was credited to the Balance, provided that during that time no charges for Requests were debited from the Balance. If the Balance has already been used, in full or in part, or 10 days have passed, no refund is made.

11.2.The following are non-refundable: referral rewards (they can be withdrawn under section 10); the face value of issued Gift cards; funds credited by activating a Gift card received from another person.

11.3.To receive a refund, the Customer sends a request to the support service from the account’s email address and specifies the order number on the ggsel marketplace or other payment details. The Contractor considers the request and refunds the money within 10 business days of receiving it.

11.4.The refund is made in rubles in the amount paid for the top-up, by the same method the payment was made or to the details specified by the Customer. An unactivated Top-up code is refunded under the rules of the marketplace where it was purchased.

11.5.If funds were debited by mistake due to a failure of the Service, the Contractor returns them to the Balance after verification.

12.1.The Service is provided in the form in which it is available at the time of access. The Contractor makes reasonable efforts to ensure uninterrupted operation but does not guarantee the absence of interruptions and errors.

12.2.The Contractor is not liable for the unavailability of Models for reasons beyond the Contractor’s control; for the content of Model responses and the consequences of their use; for Requests made by third parties with the Customer’s API key; for communication and equipment failures on the Customer’s side.

12.3.The Contractor’s liability under the Agreement is limited to the amount paid by the Customer over the last three months, unless the law provides otherwise.

12.4.The parties are released from liability for non-performance of obligations caused by force majeure (paragraph 3 of Article 401 of the Civil Code of the Russian Federation), including decisions of public authorities, failures of backbone communication networks and restrictions imposed by the developers of the Models.

13.1.Requests are accepted by email at support@apimira.com and in the support chat on the Site. The Contractor replies within 1 business day.

13.2.The Contractor sends notices to the account’s email address and publishes them in the “Updates” section. A notice is deemed received on the day it is sent.

14.1.The Agreement is valid indefinitely from the moment of acceptance.

14.2.The Contractor may amend the offer. A new version takes effect from the moment of publication on the Site unless it specifies a different date. The Contractor notifies the Customer of material changes by email no later than 7 days before they take effect. Continued use of the Service after that constitutes consent to the changes.

14.3.The Customer may terminate the Agreement by requesting account deletion through the support service. Upon deletion, API keys are revoked, personal data is anonymised, and operation records are kept for the periods established by law. The remaining Balance is refunded on request if the conditions of section 11 are met. While the Customer has a reward withdrawal request under consideration, the account is not deleted.

14.4.The Contractor may terminate the Agreement unilaterally if the Customer breaches clause 7.3, notifying the Customer by email. In that case, funds are refunded under the rules of section 11; in case of fraud, funds are not refunded.

15.1.The Agreement is governed by the law of the Russian Federation.

15.2.The parties resolve disputes through negotiations. The period for responding to a written claim is 30 days.

15.3.If a dispute is not settled, it is considered by a court in the manner established by the legislation of the Russian Federation.

Email

support@apimira.com

Chat

support chat on the Site

Site

apimira.com