Skip to content

terms

Public Offer

The agreement on access to the API service. Anyone who accepts this offer concludes the agreement on the terms below.

Version 2026-10-01

In force from October 1, 2026

This text is published in Uzbek, English and Russian. If the versions differ, the Uzbek text prevails.

Operator details

Operator details will be published here.

01General provisions

This document is a public offer (Articles 367 and 369 of the Civil Code of the Republic of Uzbekistan). The Operator named in the “Operator details” block on this page offers to conclude an agreement on the terms below with anyone who accepts it (the Customer). The agreement is concluded electronically, in accordance with the law “On electronic commerce”.

The Customer may be an individual, an individual entrepreneur or a legal entity. For an individual who uses the service for personal needs not related to business, the law “On the protection of consumer rights” also applies; nothing in this offer limits the rights that law gives a consumer.

Persons under 18 use the service with the consent of a parent or legal representative.

Terms used here: the Service — the paid HTTP API and the web panel at app.qobilbek.dev; the Panel — the part of the site available after signing in; an Organization — the account unit to which credits, API keys, request logs and payments belong; a Credit — the unit in which the price of a request is expressed.

02Acceptance and conclusion of the agreement

The offer is accepted (Article 370 of the Civil Code) by ticking the box “I have read and accept the Public Offer and the Privacy Policy” when creating an account. A person who signs in with Google for the first time accepts the offer the same way before using the service. The agreement is concluded from the moment of acceptance.

We record the date and time of acceptance and the version of the text that was accepted. The version and the date it takes effect are shown at the top of this page.

A person who accepts the offer on behalf of a company or an individual entrepreneur confirms that they are authorised to do so.

03Subject of the agreement

The Operator gives the Customer access to the Service, and the Customer pays for its use with credits. The Service is a paid HTTP API: you send a request and receive a JSON response. The products cover media extraction for TikTok, Instagram, Facebook, Pinterest, Likee and X (individually, or through one endpoint that accepts a link from any of them), YouTube search, metadata, audio and video download, music recognition, image moderation and text translation.

The current list of products, the price of each and whether each is available are shown on the Products, Pricing and Status pages. A product may be switched off for maintenance or when a source platform changes; requests to a product that is off receive an error response with an error code and are not charged.

04Accounts, organizations and API keys

An account belongs to a person. Credits, API keys, request logs and payments belong to an organization. One person can belong to several organizations, and an organization can have several members; each member's role determines what they can do.

An API key is shown in full only once, when it is created. We keep it only in hashed form and cannot show it again: a lost key must be revoked and replaced.

Keep your API keys confidential and use them only in server-side code — never in front-end code, mobile apps or public repositories. You are responsible for every request made with your keys, and for the credits those requests consume, until the key is revoked. If you suspect that a key has leaked, revoke it in the Panel at once.

Send the API key in the X-Api-Key header. A request that carries a key in the api_key query parameter is rejected and that key is revoked immediately, because URLs are routinely recorded in logs and browser history.

05Prices and payment

Each product has one fixed price in credits per successful request; prices are listed on the Pricing page. The same price applies whether or not the answer comes from a short-term cache. A request that ends in an error is not charged.

Credits are bought in packs. The price of each pack, in Uzbek soums or US dollars, is shown on the Pricing page and in the Panel before you pay; you pay the price shown at the moment of payment.

A credit is a unit of account of the Service. It is not money, and it cannot be exchanged for money except through a refund under the section “Refunds”.

A new account receives a one-time grant of free credits once the email address is confirmed; the amount and the validity period are shown on the Pricing page. Free credits not used within that period expire. Purchased credits currently have no expiry date.

The number of requests per second an organization may send depends on how many credits it has purchased in total; the tiers are on the Pricing page.

Payments are processed by payment service providers: Click, Payme and Paynet for payments in Uzbek soums, and Lemon Squeezy for payments in US dollars. The Panel shows which of them are available. Card details are entered on the provider's side, not on this site.

The Operator may change prices. A new price applies to requests made after it is published on the Pricing page; the number of credits already bought does not change.

06Refunds

Within 14 days of a payment you may ask for a refund of the credits from that payment that have not been spent. Send the request to support@qobilbek.dev from the email address of the account, stating the date and amount of the payment.

Credits from each payment are kept as a separate lot, and the Panel shows how much of it is left. The refund is the unspent part of that lot, in proportion to the price paid, and is returned to the original payment method through the same payment provider. Credits that have already been spent are not refunded; free credits are not refunded.

For individual consumers, refunds are made within the time limits set by the law “On the protection of consumer rights”, and a delay gives the consumer the rights provided by that law. The time a bank or payment provider takes to credit the money depends on them.

When a payment is refunded, its unspent credits are removed from the balance. If a payment is reversed by the payment provider (for example, as a chargeback) after some of its credits were spent, the spent part becomes a debt of the organization; while the debt is outstanding, API requests are refused and the organization cannot be closed.

Records of payments and of credit and balance movements are not deleted; they are kept for accounting.

07Acceptable use

Use the API only for content you have the right to access and use. You are responsible for how you use content retrieved through the Service, including respecting the copyright and other rights of its authors and the terms of the platform that hosts it. Returning a link does not grant you a licence: the rights to the content belong to its authors and rights holders.

You must not use the Service to get around restrictions that a source platform has placed on you, to collect personal data about people at scale, to build a product whose purpose is redistributing other people's media, or for any unlawful purpose.

Do not try to exceed your rate limit by spreading requests across several accounts or organizations, attempt to access another organization's data, or interfere with the operation of the Service. If you find a way to access another organization's data, report it as described in the security section of the Support page.

08Third-party platforms

The Service is not affiliated with, endorsed by or under any agreement with TikTok, Meta (Instagram, Facebook), Google (YouTube), Pinterest, Likee, X or Apple (Shazam). It retrieves content that is publicly available on those platforms.

These platforms change without notice. When one of them changes, a product may return errors until it is adapted. Such errors are treated as faults to be fixed, and requests that end in an error are not charged.

The Service returns what the source provides. The Operator does not check the content, its licence or its accuracy.

09Media links and temporary download links

Most products return links to files on the source platform's servers. Those links are issued by the source platform and usually stop working after a short time. Download the file soon after you receive the link; do not store the link and expect it to work later. The Operator does not host these files.

YouTube download (audio or video) works differently: the file is prepared on our servers and you receive a temporary download link to it. No API key is required to use that link — the temporary token in the URL grants access to the file to anyone who has the link, until the link expires (currently one hour after it is issued) or its download allowance is used up. Keep the link confidential: you may pass it to your own end user for their download, but you must not publish it. Prepared files are deleted from our servers automatically: video files after about 24 hours, audio files after about 7 days.

Responses may be served from a short-term cache — at most one hour, and never longer than the media links inside them remain valid. A cached response costs the same as any other request.

10Availability and liability

The Service is provided without a service-level agreement (SLA). The Status page shows the measured availability of each product. The Service may be interrupted for maintenance or because of faults.

The parties are liable for failing to perform this agreement in accordance with the legislation of the Republic of Uzbekistan. The Operator is not responsible for content returned from source platforms or for how the Customer uses it.

11Suspension, closing and account deletion

The Operator may suspend an organization that is used to attack or overload the Service or that breaks the acceptable-use rules. While an organization is suspended, its API requests are refused; its credits and balance are kept.

The owner of an organization can close it from the Panel. API requests are refused from that moment. For 30 days the closing can be cancelled and the organization's data can still be exported. After 30 days the organization is closed permanently: unused credits and any balance are forfeited, API keys are revoked, and the organization's name and pending invitations are anonymised. The Panel states this before you confirm. An organization with an outstanding debt cannot be closed. If you are entitled to a refund, ask for it before closing.

You can delete your account in the Panel (Profile → My data → Delete account). The deletion takes effect after 30 days; signing in during that period cancels it. Deletion is refused while you are the only owner of a team that has other members. Deleting the account ends this agreement; what happens to personal data is described in the Privacy Policy.

If the Operator decides to discontinue the Service, it will announce this on this site before the API stops working.

12Changes to the offer

The Operator may change this offer. The new version is published on this page with a new version date before it takes effect. Signed-in users are asked in the Panel to accept the new version; until they do, the Panel cannot be used. A Customer who does not accept the new version may stop using the Service and delete the account.

Incompatible changes to the API are released under a new version prefix. Within a version, new fields may be added to responses — your code should ignore fields it does not recognise — but existing fields are not removed and their meaning is not changed.

13Claims and disputes

This agreement is governed by the law of the Republic of Uzbekistan.

Before going to court, send a written claim to support@qobilbek.dev from the email address of the account, describing what happened and what you ask for. The Operator answers within 15 days of receiving it.

If the dispute is not settled, it is decided by the court at the Operator's location. This does not limit a consumer's right to bring a claim at their place of residence or at another place provided by law.

14Language and operator details

This offer is published in Uzbek, English and Russian. If the versions differ, the Uzbek text prevails.

The Operator's name, legal form, taxpayer identification number, postal address, phone and email are given in the “Operator details” block at the top of this page. Email: support@qobilbek.dev.

Questions, claims and requests about personal data are accepted at the support address.

support@qobilbek.dev

Public offerPrivacy PolicySupport