Using our data
Checking a wallet is free and always will be. Showing what you found to other people is free as well, on one condition: a credit line and a link. Customers on a paid API or MCP plan show no credit at all.
In effect from 3 September 2026. Version 1.
Checking a wallet is free
Look up any address, as often as you need, and act on what you find. No account, no card, no credit line, no permission.
That covers a person checking a wallet before they send to it, and it covers a program doing the same for one address at a time. It is the whole point of the site.
Showing our data to other people is free, with credit
Put our figures on your website, in a post, in a paper, in a newsletter, in a deck, in a dashboard. Quote a record. Republish a number. You do not need to ask us first.
The permission comes with one condition: a credit line and a link, so the person reading you can get to the record and check it themselves. That is the whole price, and it is the same for everyone using the free site.
The credit line
Use these words:
Data from Eagle Virtual
Make "Eagle Virtual" a link. Any of these work just as well, if they fit your page better: "Source: Eagle Virtual", "Freeze and seize record from Eagle Virtual", or "Powered by Eagle Virtual" for a product.
Three things make a credit line count:
| Item | Detail |
|---|---|
| A reader can see it | Without clicking, hovering, or opening anything. Readable, in the same care you give the rest of your text. |
| It sits with the number | Next to the figure or the record it belongs to — not only in a footer three screens away. |
| It is a real link | In your page’s HTML, so a search engine sees it too. Not added by JavaScript alone, and not marked "nofollow". |
Where the link should point
Point it at the page the record is on, not at our home page. If you are quoting one wallet, link that wallet’s page. If you are quoting a coin’s total, link that coin’s page. If you are quoting the whole record, link eaglevirtual.com.
Carry the date with the figure. Every number here moves as new events are recorded, so a figure without its date is a different claim. We print the date on every page for exactly this reason.
Two examples
On a web page, under a figure:
Tether froze this wallet on 17 August 2026.
<a href="https://eaglevirtual.com/address/0x9b2328055872e7470e9cfdafa0186c1c72c3bac4">Data from Eagle Virtual</a>, as of 2 September 2026.In a paper or a report
Cite it like any other online source, with the date you read it:
Eagle Virtual (2026). Stablecoin Freeze & Seize Tracker.
https://eaglevirtual.com/address/0x9b2328055872e7470e9cfdafa0186c1c72c3bac4
(accessed 2 September 2026).Researchers and journalists
The same rules, and the same welcome. Cite us as above, carry the date, and link the page you took the figure from.
If you need a figure we do not publish — a cut of the record we have not put on a page, a longer history, a shape that suits your method — write and ask. We would rather compute it for you than have it estimated. Say what you are working on, what figure you need, and when you need it.
Paid API and MCP customers show no credit
If you are on a paid plan and reading the record through our API or the MCP server, you owe us no credit line at all. Show the data as your own. That is part of what the plan buys.
The credit line above is the condition on the free site, and only there.
Bulk use is a conversation, not a no
Some uses go past quoting and into taking the record itself. Those need a written agreement with us:
| Item | Detail |
|---|---|
| Reselling it | Selling the record, or access to it, to someone else. |
| Bundling it | Building it into another product or data feed you supply. |
| Republishing it in bulk | Putting up a copy of the record, or a large part of it, as a dataset of its own. |
| Building a dataset from it | Deriving a new dataset out of ours. |
| Training a model on it | Using the record as training data. |
How to ask
Write to us and say what you want to do, which part of the record you need, how often you need it, and who will see it. We answer with a price or a plain no, and we answer quickly.
The line between quoting and taking is simpler than it sounds: showing your readers what you found is quoting; accumulating the record so that other people come to you for it instead of us is taking.
Daily limits, and why they exist
The free check is fast because no one is allowed to take all of it at once. The limits below are what keep it that way. A person will never meet them.
| Item | Detail |
|---|---|
| Checking wallets on the site | 1,000 a day from one network address. A person checking wallets will not reach this. |
| The data files behind the pages | 60 requests a minute from one network address. |
| The MCP server without signing in | 100 calls a day, then sign in. |
| The API, Business plan | 100,000 calls a day for each key, 30 a second. Five keys. |
| The API, Enterprise plan | Set by agreement. The ceiling in the code today is 1,000,000 calls a day for each key, 30 a second. |
Copying the whole record is not allowed
Search engines and AI assistants are welcome to crawl our pages, read them, index them and cite them. That is how people find us.
What is not allowed is using automatic tools to work through the site and collect the record itself — walking every address page, pulling the data files in a loop, or otherwise assembling a copy of the record. We watch for it and we limit it, and an address that does it gets slowed down or blocked.
If what you want is the record in bulk, the answer is not a faster script. Write to us. The API exists for exactly this, it is quicker than scraping, and it comes with support.
If a credit line is missing
We write and ask. That is the first step and almost always the last one.
Most missing credit is an oversight, and a short email fixes it. Because credit is the condition, the permission to show our records ends while it is missing — and it starts again by itself the moment you add the credit line, with nothing to sign and nothing to pay. If you add it within 30 days of hearing from us, we treat the permission as never having lapsed.
We would much rather have the credit than the argument.
What this replaced
Until 3 September 2026 our terms offered the records under the Creative Commons Attribution 4.0 license. They no longer do, and this page is the license now.
That change works from 3 September 2026 forward. If you took records from us under the old terms, what you took stays yours on those terms — a Creative Commons license cannot be withdrawn, and we are not pretending otherwise. Anything you take from today follows this page.
The facts themselves are not ours and we claim no ownership of them: every event here happened on a public blockchain and anyone can read it there. What we built is the collection — finding the events, decoding them, measuring the amounts, and keeping the history in one place since 2018. That is what this page is about.
Some countries protect that work directly. In the United Kingdom, the European Union and the European Economic Area, the law gives the maker of a database its own right, separate from copyright, when they have put substantial effort into obtaining and checking the contents. That describes what we do — we do not create these events, we find them and verify them — and we claim that right where it applies. It changes nothing on this page: the permissions above are the same everywhere, and so is the credit line.
For programs
The machine-readable version of this page is at /license.xml, in the RSL format, and robots.txt points at it. Every record the MCP server returns carries that address in its metadata.
It says the same three things this page says, in the form a program reads: searching, indexing and answering from our pages are permitted with credit; training a model on the record is not permitted without a written agreement. An assistant that answers someone using our record owes the same credit line a website does — name us, and link the page the record is on.
These terms are part of our terms of use.
Questions people ask
Do I need to ask permission to quote a figure?
No. Quote it, credit it with a link, and carry its date. Permission is only for bulk use — reselling, bundling, republishing the record as a dataset, or training a model on it.
I am on a paid plan. Do I still need the credit line?
No. Paid API and MCP customers show no credit. That is part of what the plan buys.
Can I put your data in a free app?
Yes, with the credit line and a link to the page each record is on. If the app is redistributing the record rather than showing a person their own lookups, write to sales@eaglevirtual.com first.
Can I train a model on the record?
Not without a written agreement. Write to sales@eaglevirtual.com. Answering someone’s question from our pages is a different thing and is welcome — credit it the same way, by naming us and linking the page the record is on. /license.xml says the same in machine-readable form: search, AI indexing and AI input are permitted with credit; training is not.