GitLab Rate Limit Changes Impact LLM Usage
Problem
GitLab.com is adjusting request quotas for unauthenticated and free-tier users, imposing a limit of one request per minute. This creates a significant bottleneck for LLM interactions and data scraping that rely on frequent API calls, prompting user concerns about insufficient limits and calls for higher quotas or alternatives.
Pain points
- Unauthenticated requests limited to 60 per hour (about one per minute)
- Free tier's 5,000 requests per hour may still be insufficient for heavy LLM usage
- Rate limits make LLM interactions with GitLab inefficient
Questions to verify
- Do users primarily benefit from the current free quota?
- Do they need higher unauthenticated request quotas to support LLM usage?
- Are there alternative solutions (e.g., self‑hosting or GraphQL) that users are considering?
Evidence
quote · @匿名
If you are using LLMs to interact with sites like GitLab and GitHub, and you have the option to use a GraphQL API, you should jump on it immediately. GraphQL is absolutely terrible for human developers to interact with, but it's like Facebook could see into the future back in 2012. I cannot imagine a more perfect API surface for agents. With the REST API on GitHub, you can consume maybe 10 issue JSON blobs before your context window is blown out. With GraphQL constraining the results you can easily read hundreds in the same token budget. Additionally, the # of requests your agents need to make can be reduced in many cases since GraphQL can join across types whereas REST APIs cannot. You essentially get savings in two dimensions here. Quota and raw token volume per logical response.
quote · @匿名
60/hour unauthenticated, but 5,000/hour on the free plan.60/hour sucks. 5000/hour (a little more than one per second) is totally fine.I'm chalking this up alongside Docker's decision to restrict unauthenticated pulls. Unauthenticated anything went the way of the dodo some time ago. If you want unauthenticated access, go run your own mirror.
quote · @匿名
I assume this is because of LLM scraping.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.