Skip to main content
What changed across the ShieldLabs platform and these docs. Newest first.

​
September 2026

​
Minor improvements and bug fixes

Maintenance updates across the public SDKs, OpenAPI spec, and examples.

​
August 2026

​
Domain freeze after 10s at plan RPS

If a domain stays at its plan ingest cap (5 / 5 / 10 / 15 RPS) for 10 seconds in a row, ShieldLabs pauses processing for that domain: the same HTTP 429 as other rate limits, and it is not a disabled domain. See Rate limits.

​
History API soft rate limit

The account History API on account.shieldlabs.ai now allows 15 requests per second per site. A 429 is soft (no ban). This is independent of ingest per-IP / per-domain limits. See Rate limits.

​
Ingest limits and plan quotas documented

The Billing and Rate limits pages now match production:
  • Active domains per plan: Free 1, Starter 1, Growth 3, Scale 5. Existing domains over the cap keep running; only new creates are refused.
  • Per-domain REST ingest: 5 / 5 / 10 / 15 requests per second (soft 429, no domain ban).
  • Per-IP REST ingest: 15 requests per minute, then a 10-minute ban (not 20/minute and not a 1-hour ban).
  • Shared REST ingest cap: 40 requests per second, soft 429.

​
June 2026

​
Documentation improvements

Developer docs were updated to match the product: Risk Score 0 to 100, named signals, and decisions in your own code. There is no Trust Score, no in-product rules engine, and the only bands are Clean, Low, Medium, and High. See How it works.