Chirpie · Terms of Service

Chirpie terms of service

Read from Chirpie's own page on 2026-11-09. 9 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: September 18, 2026

Permitted use

The page states nothing on this.

Prohibited use

summary: Reselling or redistributing the Service
Resell or redistribute the Service without written authorization
Read from Chirpie's own page on 2026-11-09
summary: Circumventing limits or security
Circumvent rate limits, usage quotas, or security measures
Read from Chirpie's own page on 2026-11-09
summary: Benchmarking or reverse-engineering via API keys
API keys must not be used to benchmark or reverse-engineer the Service.
Read from Chirpie's own page on 2026-11-09

Caching

The page states nothing on this.

Redistribution

stance: conditional
Resell or redistribute the Service without written authorization
Read from Chirpie's own page on 2026-11-09

Attribution

Governing law

jurisdiction: Delaware, USA
These Terms are governed by the laws of the State of Delaware, USA, without regard to conflict of law provisions.
Read from Chirpie's own page on 2026-11-09

Liability cap

Our total liability for any claim arising from the Service shall not exceed the amount you paid us in the 12 months preceding the claim.
Read from Chirpie's own page on 2026-11-09

Termination notice

We may suspend or terminate your account for violation of these Terms with notice when possible.
Read from Chirpie's own page on 2026-11-09

Change notice

We will notify you of material changes via email or a prominent notice on the Service.
Read from Chirpie's own page on 2026-11-09

Rate or usage limits referenced

Plans have a hard monthly post limit. If you exceed it, requests receive a 429 response until the next billing cycle or until you upgrade.
Read from Chirpie'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