GitHub Search API for repositories
Search GitHub repositories over HTTP and receive the primary language and star count alongside each result, without handling GitHub tokens or rate limits yourself.
Endpoint
Results arrive in the same JSON shape as every other engine, so existing parsing continues to work.
The title is the repository path, such as redis/redis.
The snippet begins with the primary language and the star count.
The rest of the snippet is the repository summary.
Useful for
Coding agents / Tech scouting / Dependency research
Repository popularity without a GitHub token
Set `search_service` to `github` and the results come from GitHub repositories. The endpoint, the authentication, and the response shape are the same as every other engine, and no GitHub credential is involved.
Ranking signals in the snippet
The `snippet` field follows the pattern `Language | N stars | description`, so language and popularity are parseable without a second call.
Repository path as the title
The `title` field is `owner/repo`, which maps directly onto package and dependency identifiers.
No GitHub rate limit to manage
Requests are billed against Search1API credits rather than a GitHub token, so there is no per-token hourly ceiling to work around.
Standard Search parameters
`max_results` up to 50, plus `include_sites`, `exclude_sites`, and `time_range`.
What is a GitHub search API?
A GitHub search API is an HTTP interface that returns GitHub repositories as structured results. GitHub publishes its own search endpoint, but it requires a personal access token, applies a low per-token rate limit to search specifically, and returns a large payload that has to be reduced before it is useful to a model. Search1API exposes GitHub as one of the search services on its Search endpoint, returning the repository path as the title and the primary language, star count, and description in the snippet, in the same JSON shape it returns for its other engines. That makes it practical for coding agents that need to identify a library and judge its traction inside a single tool call.
Typical workflow
Search GitHub repositories over HTTP and receive the primary language and star count alongside each result, without handling GitHub tokens or rate limits yourself.
Send a query with `search_service` set to `github`.
Read the repository path from `title` and split `snippet` on the pipe to get language and stars.
Set `crawl_results` when the workflow needs README text rather than repository metadata.
One request, repositories ranked by traction
A single call searches GitHub repositories and returns the language and star count with each result, which is usually enough to pick a library without a follow-up request.
bash
Best for
Coding agents that need to find and compare libraries before writing an import.
Technology scouting that tracks which projects are gaining traction.
Dependency research that needs a language and popularity signal per candidate.
Documentation tools that resolve a package name to its source repository.
FAQ
How is this different from the GitHub search API?
GitHub’s own search endpoint requires a personal access token and applies a low rate limit to search requests specifically. Search1API bills against its own credits, so there is no GitHub token to provision or rotate, and it returns a compact result with the language and star count already in the snippet rather than a large JSON object to reduce.
Do I need a GitHub token?
No. Authentication is your Search1API key. The request is a POST to https://api.search1api.com/search with `search_service` set to `github`.
Can I get the README of a repository?
Yes. Set `crawl_results` to the number of top results you want fetched, and each page retrieved successfully includes a `content` field with the page text as markdown. Results that cannot be retrieved are returned without `content` and are not charged.
What does a GitHub search cost?
One credit per search, and one additional credit for each page retrieved successfully through `crawl_results`. At the base top-up rate of $1 for 1,000 credits, that is $1 per 1,000 searches. Signup includes 100 free credits with no credit card.
Which other developer sources are supported?
The same Search endpoint accepts `arxiv` for papers, `reddit` for community discussion, and `x` for posts, alongside general web engines and the Chinese-language engines, for 17 engines in total on one contract.
Can I use it with Python, JavaScript, or cURL?
Yes. Search1API is a REST API that works with any HTTP client, and GitHub is a parameter value rather than a separate integration. The official TypeScript and Python SDKs, the CLI, and the MCP server all accept the same `search_service` value.