Documentation Python quickstart Blog Free tools Enterprise solutions hello@quanticdata.ioLog in
All collectors

GitHub profile scraper API

Developers & tech · v1.0.0 · github_profile

$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.

InputTypeRequiredWhat it does
usernamesstring[]yesGitHub usernames or profile URLs, one per line, up to 100.
countrystringnoTwo-letter country code (ISO 3166-1) the request is made from. Leave it out for the default.
max_resultsintegernoHow 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.

FieldTypeWhat it holds
rankinteger1-based delivery order.
usernamestringLogin.
user_idstring · nullableGitHub's numeric id of the account.
namestring · nullableDisplay name.
typestring · nullableUser or Organization.
biostring · nullableProfile bio.
companystring · nullableCompany as the profile states it.
locationstring · nullableLocation as the profile states it.
emailstring · nullablePublic e-mail, when the account shows one.
websitestring · nullableWebsite on the profile.
twitter_usernamestring · nullableLinked X (Twitter) handle.
hireableboolean · nullableTrue when the account says it is open to job offers.
followersinteger · nullableFollowers.
followinginteger · nullableAccounts followed.
public_reposinteger · nullablePublic repositories.
public_gistsinteger · nullablePublic gists.
avatarstring · nullableAvatar URL.
created_atstring · nullableAccount creation time (ISO 8601).
updated_atstring · nullableLast profile update (ISO 8601).
urlstringProfile 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/scraper/collectors/github_profile/run.

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

POST /v1/scraper/collectors/github_profile/run
$ 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.

Get my free API key
GitHub profile scraper API: from usernames, QuanticData reads the GitHub profile and returns one row per profile with username, followers and public_repos, at $0.001 per delivered profile.
You send GitHub usernames; each comes back as one row with username, followers and public_repos — 20 fields on every row — and you are billed $0.001 for each profile actually delivered, nothing for a run that delivers none.
$0.001 / profile2,000 profiles on the free $2 every month
Semantic inputusernames, country, max_results — no URL lists
Up to 100profiles per run, pagination handled for you
20 fieldsone row per profile

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.

$0.001per delivered profile$1.00 per 1,000 delivered profiles
2,000 profileson the free allowance$2 every month, no card
Zero rowszero chargea run that delivers nothing is free
−30%on volume tiersthe catalog returns your key's price

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 scraperThis collector
AccessA personal access token, or 60 keyless requests an hour per IPOne API key, up to 100 profiles a run
Users and organizationsTwo kinds of accounts to tell apartOne row shape, with type
Missing accountsYour own handling of every 404A username with no account is simply not billed
OutputNested JSON full of API URLsFlat rows with the fields that matter
Join dateRead off the profile pagecreated_at and updated_at in ISO 8601
BillingYour servers and your timeOnly delivered profiles
GitHub profile scraper API: the POST to the github_profile collector, 2 profiles delivered and the bill, 2 × $0.001 = $0.002 in usage.cost_usd; zero profiles would cost $0.
The same call you would paste into a terminal: a Bearer key, the usernames in the body, and back the envelope every QuanticData endpoint returns — type, message, payload — where count is how many profiles arrived and usage.cost_usd is $0.002, which is 2 × $0.001. A run that delivers nothing costs nothing.

Sources and standards

The platform documentation and standards this collector is built against — check any claim on this page against the primary source:

FAQ

Questions we get about the GitHub profile scraper.

Something else? Ask us

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.

Get my free API key
Illustration: three coloured zones of the page that is read (GitHub profile) turn into clean JSON with the fields username, followers and public_repos; 20 fields on every row.