Sonatype · Terms of Service
Sonatype terms of service
Read from Sonatype's own page on 2026-11-10. 10 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Effective date
2017 07 28
Permitted use
summary: Personal use of website
We are making the Service available to you for your information and personal use only.Read from Sonatype's own page on 2026-11-10
summary: Permission conditional on rules
You have our permission to use the Service, but only if:Read from Sonatype's own page on 2026-11-10
Prohibited use
summary: No other-purpose use or copying
You may not (and you agree not to) use, copy, distribute, transmit, broadcast, sell, or do anything else with the Service for any other purpose.Read from Sonatype's own page on 2026-11-10
summary: No illegal use
use our Service for any illegal purpose;Read from Sonatype's own page on 2026-11-10
Caching
The page states nothing on this.
Redistribution
stance: prohibited
You may not copy, frameset, enclose or otherwise distribute any part of the Service.Read from Sonatype's own page on 2026-11-10
Attribution
Governing law
jurisdiction: Maryland
These Terms of Service are governed by laws of the state of Maryland, without respect to its conflict of laws principles.Read from Sonatype's own page on 2026-11-10
Liability cap
IS LIMITED TO A MAXIMUM AMOUNT OF $100.Read from Sonatype's own page on 2026-11-10
Termination notice
we may terminate or suspend your permission to use the Service immediately and without notice upon any violation of these Terms of ServiceRead from Sonatype's own page on 2026-11-10
Change notice
We can change these Terms of Service at any time without any notice to you.Read from Sonatype's own page on 2026-11-10
Rate or usage limits referenced
enforcing the limits on the use of the Service or the Content on the Service.Read from Sonatype's own page on 2026-11-10
Document
Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page