Rodeo · Terms of Service
Rodeo terms of service
Read from Rodeo's own page on 2026-11-09. 8 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
16 January 2026
Permitted use
summary: Commercial use of results
use results from the Services for commercial purposes, provided your use complies with these Terms and applicable law.Read from Rodeo's own page on 2026-11-09
summary: Generate ideas and drafts for others
use the tools to generate ideas, drafts, and suggestions for your own use or for othersRead from Rodeo's own page on 2026-11-09
Prohibited use
summary: No scraping at scale
to scrape, crawl, or systematically extract data or results from the Website at scale (except where permitted by law);Read from Rodeo's own page on 2026-11-09
summary: No reverse engineering
to reverse engineer, decompile, or attempt to discover the source code or underlying systems of the Services except to the extent permitted by law;Read from Rodeo's own page on 2026-11-09
summary: No high-risk decisions without checks
to use the Services for high-risk decisions where errors could cause harm without appropriate independent checks (for example, legal, medical, or financial decisions).Read from Rodeo's own page on 2026-11-09
Caching
The page states nothing on this.
Redistribution
stance: allowed
copy, download, store, and share results from the ServicesRead from Rodeo's own page on 2026-11-09
Attribution
Governing law
jurisdiction: England and Wales
These terms are governed by English law.Read from Rodeo's own page on 2026-11-09
Liability cap
Subject to the above, and to the extent permitted by law, we are not liable for any loss or damage arising from or in connection with your use of (or inability to use) the Website or Services.Read from Rodeo's own page on 2026-11-09
Termination notice
Change notice
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