Legal
Terms of use, written plainly
By signing in or calling the API you agree to the points below. They are short on purpose, and they are general, not a replacement for advice on your own situation.
The gist
Use it fairly, keep your key private, expect monthly data
The service gives you link data and a Domain Rating from our own index. It does not give you promises about search rankings or traffic.
- Credits are prepaid
- Free actions need no key
- Questions go through the account page
Credits and payment
One credit equals $0.0001. Each call is billed once, whatever the number of rows returned, and new accounts receive a starting credit, while further credit is added by USDT (TRC-20) top-up from the account page.
If a request cannot be paid for, the API answers with HTTP 402, and a bad or missing key gives HTTP 401. Build your scripts to read those codes and stop cleanly, rather than retrying in a loop. Please do.
Acceptable use
Use the API for lawful analysis of public web data. Do not try to break, overload or reverse the service, and do not share one key among people who should hold their own, since that makes abuse hard to trace. Simple rules.
We may limit or suspend access when use harms the service or other users. Where we can, we will say why through the account page, and we will tell you how to put things right. That is the aim.
About the data
The index is refreshed roughly once a month. A link from last week may not be there yet, and some links will be missing altogether, so treat results as a well-sourced estimate and cross-check anything important in Search Console. Be careful.
Domain Rating is our own 0 to 100 metric. It is not an Ahrefs or Moz number, and it is not a Google signal, so keep it in its own column and never average it with figures from other tools. Different scales.
No promises about rankings
Nothing on this site guarantees a ranking, a traffic level or a result from any link. You decide what to do with the data, and you are responsible for those decisions, including the ones that turn out to be wrong. Plain enough.
Your key and your account
Your API key is yours. Treat it like a password. Anyone who holds it can spend your credits, and we cannot tell the difference between you and them, which is why it must stay out of shared files.
If you think a key has leaked, stop using it and use the account page to deal with it. Sharing screenshots of sheets or scripts is the usual way keys escape, so check every image before you post one. Act fast.
You are responsible for activity under your account. That includes calls made by scripts you wrote, scripts you installed, and scripts a colleague ran with your key, even if you never saw them run. No exceptions.
When things go wrong
The service is provided as it is. We work to keep it available but cannot promise it will always be up, and we may change or retire an action. Plan your scripts so that one failed call does not wreck a client report. Expect hiccups.
Our responsibility to you is limited to what the law permits, and nothing here removes rights you hold under rules that cannot be waived. Short, but it matters.
Changes and questions
We may update these terms. The date on the page shows the latest version, and continued use after a change means you accept it. Questions go through the account page, while the privacy notice covers how information is handled and who can see it. Nothing hidden.