Token Pool

Help shieldcn serve more GitHub badges

GitHub's API has a rate limit of 5,000 requests per hour per token. shieldcn serves badge data from the GitHub API — stars, releases, CI status, licenses — and we need your help to scale.

How it works

Authorize the OAuth app

This shares a GitHub token with read-only access to public data. We request zero scopes — no access to your private repos, no ability to act on your behalf.

Token joins the pool

Your token is added to a pool shared by other users. When we need to call the GitHub API, we pick a random token from the pool.

Distributed rate limiting

We only make a few requests with each token before rotating to another. Most users don't notice any impact on their own rate limit.

Revoke anytime

You can revoke the OAuth app at github.com/settings/applications at any time. We'll remove your token from the pool automatically.

1 token in pool5,000 requests/hour capacity

Read-only access to public data only. Zero scopes requested. Revoke at github.com/settings/applications anytime.

This token pool system is inspired by how shields.io uses the GitHub API. We're grateful to the shields.io team for pioneering this approach and sharing it openly. If you use shields.io too, consider contributing a token there as well.