MERCURY · Terms of Service
MERCURY terms of service
Read from MERCURY'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
Effective 2026-06-04
Permitted use
summary: Per-call URL fetch
A single per-call web fetch (or a related Cited service). You give a URL, we return clean page text/structured data plus a signed provenance receipt.Read from MERCURY's own page on 2026-11-10
Prohibited use
summary: Unauthorised access or unlawful use
Do not use it to access content you are not authorised to read, or for unlawful purposes.Read from MERCURY's own page on 2026-11-10
summary: Non-public targets
The service is SSRF-guarded (no private/loopback/metadata targets)Read from MERCURY'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: Queensland, Australia
These terms are governed by the laws of Queensland, Australia, and you submit to its courts for any dispute.Read from MERCURY's own page on 2026-11-10
Liability cap
Total liability for any claim is capped at the amount you paid for the call(s) at issue.Read from MERCURY's own page on 2026-11-10
Termination notice
Change notice
We may change pricing, routes, or availability.Read from MERCURY's own page on 2026-11-10
Rate or usage limits referenced
honours target robots/rate limits on a best-effort basis.Read from MERCURY'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