4 APIs from 1 credit per call.
The APIs
Prices are in credits, per call, and the same on every plan. A call that fails costs nothing.
2 more planned. Trending developers and user activity.
More platforms. Same key, same credits.
The official API
GitHub’s REST and GraphQL APIs let you build scripts and apps that automate work, integrate with GitHub and extend it, from triaging issues to managing releases. Any GitHub account can create a personal access token, and GitHub’s docs set hourly rate limits rather than a price per request.
Unauthenticated REST requests are limited to 60 per hour per IP address, while requests made with a personal access token count toward a limit of 5,000 per hour.
Read on Rate limits for the REST API (docs.github.com) (opens in a new tab)GitHub App installations start at 5,000 requests per hour, gain 50 more per hour for each repository above 20, and cannot go beyond 12,500 per hour (15,000 on GitHub Enterprise Cloud).
Read on Rate limits for the REST API (docs.github.com) (opens in a new tab)Secondary limits allow no more than 100 concurrent requests and 900 points per minute for REST endpoints, where most GET requests cost 1 point and most writes cost 5.
Read on Rate limits for the REST API (docs.github.com) (opens in a new tab)Search endpoints allow 30 authenticated requests per minute (10 for code search), and each search returns at most 1,000 results.
Read on REST API endpoints for search (docs.github.com) (opens in a new tab)The GraphQL API allows 5,000 points per hour per user.
Read on Rate limits and query limits for the GraphQL API (docs.github.com) (opens in a new tab)GitHub recommends fine-grained personal access tokens over classic tokens, and an account can create up to 50 fine-grained tokens.
Read on Managing your personal access tokens (docs.github.com) (opens in a new tab)Checked against GitHub’s developer docs (opens in a new tab).
GitHub’s docs set rate limits for the REST and GraphQL APIs rather than a price per request, and a personal access token raises the REST limit well above the unauthenticated one. If GitHub’s limits fit your workload, its own API is the simplest choice.
GitHub caps unauthenticated REST requests per IP address each hour and gives a much higher hourly limit to requests made with a personal access token or a GitHub App. Search endpoints have a separate per-minute limit, and GitHub’s rate limit docs list the current numbers.
GitHub calls it a personal access token: open Settings, then Developer settings, then Personal access tokens, and generate a fine-grained token, which GitHub recommends. With PrimaryAPI you use your PrimaryAPI key instead, and it works for every API in the catalog.
PrimaryAPI’s Trending Repositories API returns the repositories on GitHub Trending for a language and time window, with rank, stars, stars gained and description, as JSON.
When GitHub is one of several platforms you read, or when an agent needs public profiles and repositories under one key and one balance. For private repositories, writes, webhooks and steady volume inside GitHub’s limits, use GitHub’s own API.
Yes. Agents can call PrimaryAPI’s GitHub APIs through its MCP server or SKILL.md, and an agent can start on a capped trial key that a person then approves.
Create an account, buy credits when you need them, and call every GitHub API with the same key.