CourtlyGo · Terms of Service

CourtlyGo terms of service

Read from CourtlyGo's own page on 2026-11-09. 7 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

Last updated: 2026-10-26

Permitted use

summary: Free use of MCP server and data files
You may use the MCP server and the city data files free of charge, including from AI assistants, agents and apps, as long as you follow these terms and keep the attribution above.
Read from CourtlyGo's own page on 2026-11-09

Prohibited use

summary: Unlawful, abusive or overloading automated traffic
Please do not break the law, send abusive or automated traffic that overloads the service, try to bypass limits or security, or use the service to harass or locate individuals.
Read from CourtlyGo's own page on 2026-11-09

Caching

The page states nothing on this.

Redistribution

stance: conditional
If you use or share it, credit OpenStreetMap contributors, keep the license and share derived databases under the same terms.
Read from CourtlyGo's own page on 2026-11-09

Attribution

required: true
If you use or share it, credit OpenStreetMap contributors, keep the license and share derived databases under the same terms.
Read from CourtlyGo's own page on 2026-11-09

Governing law

Liability cap

To the extent the law allows, we are not liable for indirect or consequential loss, or for decisions made using the service. Nothing in these terms limits liability that cannot be limited by law.
Read from CourtlyGo's own page on 2026-11-09

Termination notice

Change notice

We may update these terms. The date above shows the current version.
Read from CourtlyGo's own page on 2026-11-09

Rate or usage limits referenced

The limit is 60 requests per minute per IP address , and a short burst of up to 20 requests at once is fine.
Read from CourtlyGo's own page on 2026-11-09

Document

Download YAML · schema: API Commons Terms of Service 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page