Developers

Sign in on the web app, then reuse the session access token as a bearer token. Every request is scoped to your own account — you can never read another user's data.

// 1. Get your access token in the browser console while signed in
const { data } = await supabase.auth.getSession();
const token = data.session.access_token;

// 2. Call the reports endpoint
curl -s "https://yzsjyuxhoamkdsxkxtyt.supabase.co/rest/v1/saved_reports?select=*&order=created_at.desc" \
  -H "apikey: sb_publishable_z9YvEP3HEqOxTSkRiuXaKg_yv3YbfmM" \
  -H "Authorization: Bearer $ACCESS_TOKEN"

The same pattern works for usage_events (your analysis history) and the usage_summary RPC, which returns your plan, daily limit and remaining runs:

curl -s -X POST "https://yzsjyuxhoamkdsxkxtyt.supabase.co/rest/v1/rpc/usage_summary" \
  -H "apikey: sb_publishable_z9YvEP3HEqOxTSkRiuXaKg_yv3YbfmM" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" -d '{}'
// => { "plan": "free", "limit": 10, "used": 3, "remaining": 7 }

Daily quotas: Free 10 analyses/day, Pro 500 analyses/day. See pricing.

Fair-use throttling applies; keep bursts under ~60 requests per minute.

Audits fetch the live target page, so expect 0.5–3 s latency on /api/public/seo-audit.

Runtime diagnostics live on the Health Check page.