Acceptable Use Policy

Last updated: 2026-04-14

1. What you can do

• Browse the site.
• Query the public JSON API for research, internal tooling, dashboards, and automation that supports your own decisions.
• Quote small excerpts with a link back to the source page.
• Link to anything. Permalinks will not change without reason.

2. What you should not do

• Do not hammer the API. Respect rate limits. If your workload needs more, cache aggressively on your side. Bulk cloning of the dataset through brute-force API calls is not acceptable — the data files are small and a reasonable archive of the full dataset is fine to produce with a handful of requests.
• Do not republish or resell the data as if it were your own product or your own research. Aggregating it into an internal tool is fine. Wrapping it into a competing public service without attribution is not.
• Do not attempt to overload, probe, or otherwise mess with the site. No vulnerability scanning without permission. No denial-of-service testing. No credential stuffing — there are no credentials to stuff, but still.
• Do not misrepresent the data as authoritative. This site is a derivative of vendor publications. It is not a vendor.
• Do not use the site for anything illegal under the law of your jurisdiction or the operator's jurisdiction.

3. Attribution

If you use the data in a report, a tool, a presentation, or any published artifact, cite eol.network as the source and note that the underlying authority is the vendor's own publication. A plain-text link is enough.

4. Rate limits

There are per-address rate limits on both the site and the API. They exist to keep the service responsive for everyone. If you get rate limited, back off. If your legitimate use case does not fit within the default limits, open an issue on the project repository and describe what you need. Do not try to work around the limits by rotating addresses or user agents.

5. Automation and scraping

Prefer the JSON API over scraping HTML. The JSON is cheaper to serve, easier to parse, and less likely to break when the UI changes. Identify your automation with a user agent that includes a contact address. That way, if something is going wrong, someone can reach you before the traffic gets blocked.

6. Enforcement

Access can be rate-limited, blocked, or terminated at any time, for any reason, without notice, if the operator believes use is abusive, disruptive, or inconsistent with this policy. No obligation to warn first, no appeals process.

7. Changes

This policy can change without notice. Continued use after a change means you accept the change.