Read the fine print with code.
Programmatic access to AIgree's daily-refreshed catalog of Terms-of-Service and Privacy-Policy summaries — bullet-pointed, severity-scored, and shipped as clean JSON.
Full catalog
Every service we track, with category, website, tagline, logo, and overall rating.
Summaries & bullets
Per-document bullet summaries, service-level synthesis, points of interest with source quotes.
Daily change feed
Severity-shifted records of every meaningful ToS update — per service or across the whole catalog.
OpenAPI spec
Auto-generate clients in any language. Bearer-token auth. Stable, versioned URLs.
A small taste.
A single bearer-token-authenticated GET returns a service's full summary.
curl -sS https://aigr.ee/api/v1/services/netflix/summary \
-H "Authorization: Bearer aigr_live_…"
- ✓All endpoints (catalog, summaries, change feed, search)
- ✓Up to 10 active keys per account
- ✓Daily quota resets at 00:00 UTC
- ✓OpenAPI 3 spec at
/api/v1/openapi.json - ✓Stripe billing portal — one-click cancel, no lock-in
Common questions
How fresh is the data?
Every service is re-fetched daily; summaries and change records regenerate whenever a source document changes. Timestamps on each response reflect the last refresh.
How does authentication work?
Pass your key as Authorization: Bearer aigr_live_… on every request. Keys are issued in the account dashboard, shown once, and revocable at any time. We store only hashes — we can't email you a forgotten key.
What about rate limits?
50,000 requests per key per UTC day. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers. Over-quota requests get a 429 with Retry-After.
Can I trust these summaries in production?
The summaries are AI-generated and a starting point — they may be incomplete or wrong. Every point of interest carries a short quote from the source document and every record links back to the canonical URL. See our methodology for caveats.