Terms of service for LinkIsFlow
Use of LinkIsFlow means you accept these terms. They are short and general. Last updated 29 October 2026.
The terms at a glance
| Topic | What it means |
|---|---|
| Account | Google sign-in. You are responsible for what happens under your key. |
| Payment | Prepaid credit; 1 credit is $0.0001. Top-ups in USDT (TRC-20). |
| Data | Informational, from our own index, refreshed roughly monthly. |
| Use | Lawful use only, and no attempts to disrupt the service. |
Accounts and keys
You sign in with Google. Keep your key private, because calls made with it are billed to your balance.
If you think a key has leaked, replace it from the account page.
One person may not use the free credit as a way to create many accounts.
Credit and billing
Calls draw down a prepaid balance at the credit prices published on the cost table. Every authenticated response shows the cost and the remaining balance, so you can check any charge yourself.
When credit runs out, requests return HTTP 402 until you top up.
Questions about a charge go through the account page. Please include the approximate time of the call.
The data and its limits
The data is provided as information. It is incomplete, because no link index is complete, and it can lag behind the web, because ours refreshes about once a month, so a link from last week may not be there.
Domain Rating is our own metric. Do not present it as a score from another company.
We do not promise any ranking, traffic or revenue result from using the data. Decisions you take on it are yours.
Acceptable use and changes
Do not use the service to break the law of the place where you live, to attack it, or to resell raw access without agreement.
We may limit or suspend access that harms the service or other users.
We may update these terms. The date at the top will change when we do. Continued use means you accept the updated terms. If you do not accept them, stop using the service and your keys.
Availability
We aim to keep the service running. Still, we cannot promise it will be uninterrupted or free of errors.
Plan for failures in your own code: retry sensibly, and treat HTTP 401 and 402 as final until you fix the key or the balance.