Juro · Terms of Service
Juro terms of service
Read from Juro's own page on 2026-11-09. 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
Not stated on the page.
Permitted use
summary: Interface use
Our API is intended to be used as an interface between the Juro platform and applications or services provided by you.Read from Juro's own page on 2026-11-09
summary: Limited licence to use API
We grant you a non-exclusive, revocable and non-transferable licence, without a right to sublicense to end users, solely to use the API to interface between the Juro platform and applications or services provided by youRead from Juro's own page on 2026-11-09
Prohibited use
summary: Spam or service interference
You must not use our API to send spam or to interfere with or degrade our services in any way.Read from Juro's own page on 2026-11-09
summary: Unlawful purpose
You must not use our API for any unlawful purposeRead from Juro's own page on 2026-11-09
Caching
Redistribution
stance: conditional
without our prior written consent, make derivative works of, or commercially distribute or otherwise exploit the API dataRead from Juro's own page on 2026-11-09
Attribution
Governing law
jurisdiction: England and Wales
governed by, and construed in accordance with, the laws of England and WalesRead from Juro's own page on 2026-11-09
Liability cap
we exclude and limit our liability to the maximum extent that we are permitted to under applicable lawRead from Juro's own page on 2026-11-09
Termination notice
period: without notice
which we may do at any time for any reason and without noticeRead from Juro's own page on 2026-11-09
Change notice
period: 10 days
Updates will take effect 10 days after we post them or earlier if we notify you directly about the update.Read from Juro's own page on 2026-11-09
Rate or usage limits referenced
Document
Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page