GitHub Profile Scraper

GitHub Profile Scraper exports public GitHub profile data from usernames, profile URLs, or GitHub user-search queries. Get profile and contact fields, follower counts, stable account IDs, and optional repository summaries in a dataset you can download as CSV, Excel, or JSON.

Use it to enrich a list of handles, research open-source communities, or shortlist profiles for manual review. Public contact information is not guaranteed, and GitHub access limits can prevent collection.

Quick start

1. Enter usernames or a GitHub user-search query. At least one of these is needed.
2. Start with one profile and leave repository summaries off unless you need them.
3. Run the Actor, check each row's status, and export the dataset.

{
  "usernames": ["octocat"],
  "includeRepositories": false
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Scrape GitHub profiles with repository enrichment
• Find Python developers on GitHub in Berlin
• Scrape GitHub profile data for specific usernames

What you get

• Public profile records: usernames, stable account IDs, available bios, public account counts and source links.
• Available contact fields: public email, website and social links when the profile exposes them. Contact information is not guaranteed.
• Optional repository summaries: sample-based stars, forks, languages and a most-starred repository from the documented public repository sample.
• Per-profile outcomes: successful or error rows, with unavailable profiles explained in the run summary.

Who is it for?

• Data teams: enrich a supplied list of GitHub handles with public profile fields and stable account IDs.
• Open-source community researchers: explore public profiles through GitHub's supported user-search qualifiers.
• People reviewing accounts manually: collect public bios, links and optional repository summaries in one place.

How you can use the data

Enrich a list of handles

Keep a reliable link between your input list and the returned profiles. Supply the usernames or profile URLs you already have, then use successful rows with status: "ok" and githubId when joining the results to your own records. Keep error rows and run-summary unavailable-profile reasons for follow-up rather than treating them as complete profiles. Public contact fields can be absent.

Research an open-source community

Start with a small search you can review yourself. The Berlin/Python example below collects a bounded set of matching public profiles. Read their bios and source links before drawing conclusions. A search match or the Actor's simple developerTier grouping is not a measure of someone's skills or suitability.

Review a repository sample

Add repository summaries when they help answer your question. For a known profile, you can collect a sample of recently updated public repositories and review its reported stars, forks and languages. These are sample-based summaries, not complete contribution histories or all-time account totals.

Input settings

Setting	JSON key	Behavior
Usernames or profile URLs	usernames	Exact handles or GitHub profile URLs. No API default list.
User-search queries	searchQueries	GitHub search syntax. No API default query.
Profiles per query	maxResultsPerQuery	1–1,000. Default 5. Does not limit direct usernames.
Repository summary	includeRepositories	Default false. Enables sampled repository metrics.
Repository sample size	maxRepositoriesPerUser	1–100. Form default 20, runtime omission fallback 30.
Optional GitHub token	githubToken	Secret field for higher authorized GitHub API capacity.

The form's sample usernames and query are prefills, not inputs automatically added to API calls. Clear any samples you do not want. Invalid entries are rejected by platform validation where supported. Inputs that reach runtime validation receive an explicit INVALID_INPUT warning in RUN_SUMMARY, with no extraction or Actor fees; correct the recipe before retrying. Direct usernames and search results are combined and deduplicated by login.

Example inputs

Search by GitHub's supported qualifiers:

{
  "searchQueries": ["location:Berlin language:Python followers:>50"],
  "maxResultsPerQuery": 5,
  "includeRepositories": false
}

Request repository summaries for a known profile:

{
  "usernames": ["octocat"],
  "includeRepositories": true,
  "maxRepositoriesPerUser": 10
}

Output data

Each resolved profile produces a row with status: "ok". GitHub HTTP 404 responses add no dataset row; RUN_SUMMARY.warnings explains the unavailable profile without assuming it was deleted or private. Other failed lookups produce error rows. A successful run status alone does not mean every lookup worked. Search queries with no matches add no profile rows.

Shape-only example of selected fields for an unsuccessful lookup, not a live observation or a complete row:

{
  "login": "example-profile",
  "githubId": null,
  "name": null,
  "email": null,
  "profileUrl": "https://github.com/example-profile",
  "status": "error",
  "error": "GitHub API access error",
  "totalStars": null,
  "topLanguages": [],
  "sourceType": "username",
  "sourceQuery": "example-profile"
}

Fields	Meaning
login, githubId, name, type	Username, stable numeric account ID, display name, account type.
bio, company, location, hireable	Available public profile details. Nullable.
email, blog, twitterUsername, bestContact	Public contact fields. bestContact prefers email, website, X URL, then profile URL.
avatarUrl, profileUrl, apiUrl	Profile image and source links.
publicRepos, publicGists, followers, following	Public account counts.
createdAt, updatedAt, accountAgeYears, accountAgeTier	Account dates and derived age classification.
developerTier	Simple follower/star-based grouping, not a measure of ability or suitability.
totalStars, totalForks, topLanguages	Aggregates over sampled non-fork repositories only.
mostStarredRepoName, mostStarredRepoUrl, mostStarredRepoStars	Most-starred non-fork repository within the sample.
repositoriesScanned	Number of repositories examined, including forks omitted from aggregate totals.
sourceType, sourceQuery	First source that introduced the login: username or search.
status, error, scrapedAt	Per-profile outcome, nullable error, collection timestamp.

Repository summaries sample the most recently updated owned public repositories, not all-time contributions or all repositories. Languages are ranked by repository count, not code volume. With summaries disabled, successful rows contain zero totals, an empty language list, and null most-starred fields: those values mean enrichment was not collected, not that the account has no stars. A repository lookup failure can yield an error row instead of a usable profile. Unresolved extraction errors mark the run failed after preserving collected rows and an INCOMPLETE summary; they are not reported as no matches.

The key-value store's RUN_SUMMARY records processed, successful, and unsuccessful counts, unavailable-profile warnings, API requests and bounded recovery attempts on normal completion. PENDING_WORK is a diagnostic checkpoint, not an automatic resume feature or an input for another run.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

The start event is charged once when valid work begins. The result event is charged for each successfully saved profile. Unavailable profiles and error rows are not charged as profile results.

Keep queries narrow, limit profiles per query and enable repository summaries only when you need them. Apify platform usage may apply separately.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Clear prefills you do not want. Sample handles and queries in the form are examples, not a fallback list automatically added to API requests.
• Check status before joining rows. Use ok profiles for enrichment and keep error rows and unavailable-profile summary warnings for follow-up.
• Decide whether you need repository summaries. Leave them off for basic profile lookups. With summaries disabled, zero totals and empty language lists mean that enrichment was not collected.

Limits and caveats

GitHub controls result availability and access limits. A token may improve authorized capacity but cannot guarantee completion. Automatic recovery for confirmed anonymous primary-quota exhaustion can use Apify datacenter proxy traffic. Its session budget scales with the requested workload (at most eight sessions); it does not rotate token requests or secondary-limit/access errors. There is no user-selectable connection setting.

For bounded resource use, a run accepts at most 1,000 direct entries and 20 search queries (512 characters per profile entry and 256 per query). Direct-entry count plus query count × profiles per query must be at most 1,000; split larger workloads into separate runs. The Actor uses and supports at most 256 MiB, with an 80 MiB old-generation heap ceiling, 2 MiB semi-spaces and 16-profile batches. Decoded API responses are limited to 1 MiB and retained public text fields to 8,192 characters. Unexpected oversized or malformed responses are reported as extraction failures, never as no matches.

Restarting or resurrecting a run does not repeat extraction, billing or saved rows: the Actor claims its storage before the first fee/request and refuses reentry, preserving existing output. Start a new run when more extraction is needed. The independent 270-second original-start deadline and request/session ceilings are not renewed by a restart. Recovery is not guaranteed: shared proxy quotas can also be exhausted. Collection processes up to 16 profiles concurrently and saves completed profiles in bounded batches, with an independent 270-second processing budget and a 2,048-request ceiling; saved results remain available when a bound is reached.

Only public information is collected. Private emails, private repositories, contribution graphs, stargazer lists, organization member discovery and built-in change monitoring are not provided by this Actor.

Missing contact fields are not proof that no contact information exists elsewhere. Repository summaries cover the documented sample, and a successful run does not mean every profile lookup worked. Check the per-profile status and error fields.

This is an independent tool, not an official GitHub product.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~github-profile-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "usernames": [
    "octocat"
  ],
  "includeRepositories": false
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/github-profile-scraper').call({
  "usernames": [
    "octocat"
  ],
  "includeRepositories": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/github-profile-scraper').call(run_input={'usernames': ['octocat'], 'includeRepositories': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

The cURL call starts a run asynchronously. Wait for that run to finish, then retrieve items from its defaultDatasetId. Do not start another run just to fetch results. Use dataset exports or Apify integrations to pass results to a spreadsheet or CRM. Sorting and comparing exports happen in your downstream tools, not inside this Actor.

MCP and AI agents

You can ask your AI assistant to collect data with GitHub Profile Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's GitHub Profile Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/github-profile-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use GitHub Profile Scraper by Fetch Cat, or give it the identifier fetch_cat/github-profile-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

Try asking your assistant for the data you need:

• “Get the public GitHub profiles for octocat and torvalds. Show their available bios, profile links and follower counts, and flag any lookup that did not succeed.”

• “Find up to five public GitHub profiles matching the Berlin and Python search example, with more than 50 followers. Return their bios and profile links for manual review.”

• “Get octocat’s public profile with a sample of ten repositories. Show the available repository summary and make clear that it covers a sample.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Can I export GitHub profiles to CSV or JSON?

Yes. Download the run's dataset as CSV, Excel, or JSON, or retrieve it through the Apify API. Review status before importing rows into another system.

Is this a GitHub profile API alternative?

It provides an Apify-hosted batch workflow for public profiles and search, not a replacement for every GitHub API capability. It does not grant extra permissions or unlimited GitHub access.

Does it need login or expose private emails?

No GitHub login is required for small public lookups. The optional secret token can improve authorized request capacity. Only public email fields are returned. Use bestContact for an available website, X URL, or profile link when email is absent.

Why did I receive fewer profiles or error rows?

Queries may have fewer matches, overlap other inputs, or encounter GitHub access limits. Inspect each row's status and error. Retry unavailable profiles after access recovers. Already saved results remain available. A not-found response does not independently establish whether an account was deleted, renamed, or otherwise unavailable.

Does it rank developers or monitor changes?

No. Derived tiers summarize limited public signals, not professional qualifications. Export and review data yourself. Comparisons across runs are your integration's responsibility.

Related Actors

• GitHub Repositories Search Scraper — Discover public repositories.
• GitHub Issues & Pull Requests Scraper — Research project discussions and changes.
• GitHub Contributor Email Scraper — Explore available contributor contact data.
• GitHub Trending Scraper — Discover trending projects.
• DEV.to Articles Scraper — Research developer articles.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥