SerpKite · Terms of Service
SerpKite terms of service
Read from SerpKite's own page on 2026-11-10. 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
28 October 2026
Permitted use
summary: Use of search results API for logged-out public results
SerpKite returns publicly available search engine results pages, parsed into structured data (JSON) or text (Markdown), and related features such as fetching public web pages.Read from SerpKite's own page on 2026-11-10
Prohibited use
summary: No resale of raw Service
In short: no resale of the raw Service, no multi-accounting, no unlawful use, and no attempts to use SerpKite to access content behind a login.Read from SerpKite's own page on 2026-11-10
summary: Multiple accounts for free credits
Creating multiple accounts to obtain additional free credits is prohibited.Read from SerpKite's own page on 2026-11-10
Caching
The page states nothing on this.
Redistribution
The page states nothing on this.
Attribution
Governing law
jurisdiction: Ontario, Canada
These Terms are governed by the laws of the Province of Ontario and the federal laws of Canada that apply there, and the courts of Ontario have jurisdiction.Read from SerpKite's own page on 2026-11-10
Liability cap
Our total liability arising out of these Terms in any 12-month period is limited to the amount you paid us in that period.Read from SerpKite's own page on 2026-11-10
Termination notice
Change notice
period: 30 days
Material changes take effect 30 days after notice by email; continued use after that means you accept them.Read from SerpKite's own page on 2026-11-10
Rate or usage limits referenced
We may apply rate limits described in the documentation, and may ask high-volume accounts to verify their identity and use case as described in the Acceptable Use Policy.Read from SerpKite'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