What is Domain Link History?
Track a website's referring-domain count over time to see whether the number of sites linking to it is growing or shrinking. Count and inspect the separate websites linking to your target so that repeated links from one domain do not dominate the picture.
Settings Domain Link History takes
You describe the task in plain words and your AI assistant fills these in. In code you pass them yourself.
| Setting | What it controls | Tip |
|---|---|---|
| Target | Target | Required |
| Date from | Start date of the historical period in YYYY-MM-DD format. | Required |
| Mode | Scope of the target: exact (this URL only), prefix (URLs starting with the target), domain (the domain without subdomains), or subdomains (default, the domain and all its subdomains). | Optional · default subdomains · one of exact, prefix, domain, subdomains |
| Date to | End date of the historical period in YYYY-MM-DD format. Defaults to today. | Optional |
| Protocol | Protocol of the target: both (default), http, or https. | Optional · default both · one of both, http, https |
| History grouping | Time bucket size for history rows: daily, weekly, or monthly (default). Each bucket is one billed row. | Optional · default monthly · one of daily, weekly, monthly |
How to use Domain Link History with your AI assistant
Connect AI/ML API
Click Try it now, pick your client and add the MCP server. You sign in with your AI/ML API account once.
Describe the task
Say what you need in one sentence, including the target.
Get the result
Your assistant runs Domain Link History and shows what came back.
Keep going in the chat
Ask it to filter, compare or summarize the result, or to save it as a table.
Ways to use it
- For a website link-profile review: track a website's referring-domain count over time to see whether the number of sites linking to it is growing or shrinking.
Domain Link History in your code
In your code
REST · your AI/ML API key, JSON records back
The same tool runs over REST with your AI/ML API key, so a backend, a script or a scheduled job can call Domain Link History directly. Start with the Toolbox REST quickstart.
Pricing
Pay as you goBilled per run from your AI/ML API balance
- No subscription
- No seat fee
- One balance for every tool
Each run is billed from your AI/ML API balance, with no subscription or seat fee. Check the current price in your dashboard before large runs.
FAQ
Do I need a separate account for Domain Link History?
No. It runs on your AI/ML API account and balance, from your AI assistant over MCP or from your code over REST.
Which AI assistants can use it?
Claude, ChatGPT, Cursor, Hermes, OpenClaw and other MCP clients. Add the AI/ML API MCP server once with the MCP quickstart.
Run Domain Link History from your assistant
Connect once, then ask for it in plain words.