GitHub profile scraper API
$0.001 / profile
$1.00 / 1K · pay per delivered profile
A GitHub profile scraper API: send usernames or profile URLs and get one row per user or organization with the name, bio, company, location, public email and website, the follower and repository counts and the join date. No GitHub token to create, up to 100 profiles per run, billed per profile delivered.
$0.001 per delivered profile · $2 free every month · Failed runs never billed
What it does
What a GitHub profile scraper returns
GitHub answers 60 requests an hour per IP address without a token, which is one short list of profiles before you need a token and your own retry code. The collector takes up to 100 usernames in one run and returns each as a flat row: user or organization, what the profile states about company, location, email and website, and the counts that show how followed and active the account is.
On 13 November 2026 Linus Torvalds’s profile showed 331,800 followers, 0 accounts followed and 12 public repositories, for an account created on 3 September 2011. Vercel came back as an Organization with 32,117 followers and 244 public repositories, created on 5 October 2015. The type field keeps people and companies apart in the same list.
Inputs
The whole request. Anything you leave out falls back to the default shown in the catalog.
| Input | Type | Required | What it does |
|---|---|---|---|
usernames | string[] | yes | GitHub usernames or profile URLs, one per line, up to 100. |
country | string | no | Two-letter country code (ISO 3166-1) the request is made from. Leave it out for the default. |
max_results | integer | no | How many profiles to deliver at most (1–100). You pay only for delivered profiles. |
Outputs — 20 fields, one row per profile
What one profile looks like
Every delivered profile carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.
| Field | Type | What it holds |
|---|---|---|
rank | integer | 1-based delivery order. |
username | string | Login. |
user_id | string · nullable | GitHub's numeric id of the account. |
name | string · nullable | Display name. |
type | string · nullable | User or Organization. |
bio | string · nullable | Profile bio. |
company | string · nullable | Company as the profile states it. |
location | string · nullable | Location as the profile states it. |
email | string · nullable | Public e-mail, when the account shows one. |
website | string · nullable | Website on the profile. |
twitter_username | string · nullable | Linked X (Twitter) handle. |
hireable | boolean · nullable | True when the account says it is open to job offers. |
followers | integer · nullable | Followers. |
following | integer · nullable | Accounts followed. |
public_repos | integer · nullable | Public repositories. |
public_gists | integer · nullable | Public gists. |
avatar | string · nullable | Avatar URL. |
created_at | string · nullable | Account creation time (ISO 8601). |
updated_at | string · nullable | Last profile update (ISO 8601). |
url | string | Profile URL. |
Integration
One POST, typed rows
Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/.
curl -X POST https://api.quanticdata.io/v1/scraper/collectors/github_profile/run \
-H "Authorization: Bearer $QD_API_KEY" \
-H "Content-Type: application/json" \
-d '{"usernames":["torvalds","vercel"],"max_results":2}'
Example response
$ curl $QD/github_profile/run \
-H "Authorization: Bearer $QD_API_KEY" \
-d '{"usernames": ["torvalds", "vercel"], "max_results": 2}'
{ "status": "done", "count": 2,
"results": [
{
"username": "…",
"type": "…",
"followers": "…",
"public_repos": "…" } ],
"cost": 0.002 }
# 2 profiles × $0.001 · nothing delivered, nothing charged
Try it
GitHub profiles, running now
Change the input and run it against the live collector — nothing to install, no sign-up.
Run it from your own code, on your own inputs
Same collector, same rows — $2 of free API credit every month, no card.
Pricing
GitHub Profile Scraper pricing
$0.001 per delivered profile. A run that delivers nothing costs nothing, and the $2 monthly allowance covers about 2,000 profiles before you spend anything.
Pay as you go
- $2 free credit / month
- 20 requests / min (300 on real balance)
- List unit prices
Starter
- $15 free credit / month
- 300 requests / min
- 10% off unit prices
Growth
- $50 free credit / month
- 600 requests / min
- 20% off unit prices
Scale
- $250 free credit / month
- 1,200 requests / min
- 30% off unit prices
Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.
What people build with the GitHub profile scraper
Three shapes of work this endpoint was designed around.
Technical recruiting
Candidates’ public profiles in one table: company, location, followers, repositories, hireable flag and the email they chose to make public, next to their LinkedIn profile.
Developer-tool go-to-market
Usernames from your project’s contributors or issue threads become rows with company and website, to see which organizations already use what you build.
Tracking organizations
Run the same organizations every week: public repositories, followers and profile changes, with their repositories from the GitHub user repos API.
GitHub Profile Scraper versus rolling your own
The differences that actually cost time when you build this in-house.
| DIY scraper | This collector | |
|---|---|---|
| Access | A personal access token, or 60 keyless requests an hour per IP | One API key, up to 100 profiles a run |
| Users and organizations | Two kinds of accounts to tell apart | One row shape, with type |
| Missing accounts | Your own handling of every 404 | A username with no account is simply not billed |
| Output | Nested JSON full of API URLs | Flat rows with the fields that matter |
| Join date | Read off the profile page | created_at and updated_at in ISO 8601 |
| Billing | Your servers and your time | Only delivered profiles |
Sources and standards
The platform documentation and standards this collector is built against — check any claim on this page against the primary source:
Can I get a GitHub user’s email from the profile?
When the account makes an email public, the row carries it in email; otherwise the field is null. The collector does not guess addresses.
Do I need a GitHub token?
No. Send usernames or profile URLs with your QuanticData key; there is no GitHub token to create and no hourly limit of your own to manage. Each delivered profile costs $0.001.
Does it work for organizations?
Yes. Organizations come back in the same row shape with type set to Organization, so a mixed list of people and companies needs no special handling.
Is scraping GitHub profiles allowed?
The collector reads only public profile data. GitHub’s Acceptable Use Policies set rules for how it may be used, including for personal information, so check them and the law where you work for your use case.
Is there a free GitHub profile scraper?
Every account gets $2 of credit every month with no card, which is about 2,000 delivered profiles on this endpoint at $0.001 each. It renews monthly, and a run that delivers nothing is never billed.
How much does one run cost?
Multiply the rows you actually receive by $0.001. A run capped at 100 profiles — the maximum for this collector — costs $0.10 if every row comes back, and less when the listing has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.
Run the GitHub profile scraper now
$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.
