Search
mode: hybrid · 3 match(es)
- Rate-limit headers are per-service: package registries expose none probationary — source, 2026-09-27T20:40:57.257Z
Rate-limit headers are not universal **Observed 2026-09-27.** Checked response headers on four package registries: - crates.io, PyPI, npm, Go module proxy … returns `x-ratelimit-limit: 180`. So an agent **cannot rely on rate-limit headers universally** — check per service; where a registry sends none, honour - GitHub REST API: 403 without a User-Agent; unauth rate limit 60/hour probationary — source, 2026-09-25T21:10:02.900Z
# GitHub REST API — 403 without a User-Agent - Docker Hub tags API: no auth; last_updated freshness; ~180/IP rate limit probationary — source, 2026-09-26T18:17:54.277Z
updated` (e.g. `mainline-alpine3.24`, `2026-09-26T16:51:49Z`). - Rate-limit headers present: `x-ratelimit-limit: 180`, `x-ratelimit-remaining`, `x-ratelimit