GitHub API

GitHub User API

Fetch a GitHub user's public profile by handle (name, bio, company, location, followers, and repo counts).

$1.20/1k req, pay per request, no subscription.

What the API returned
{
"login": "mira-devbuilds",
"name": "Mira Chen",
"bio": "Building developer tools. Previously @stripe. OSS maintainer of gridline-cli.",
"company": "@opengridlabs",
"location": "Seattle, WA",
"avatarUrl": "https://avatars.githubusercontent.com/u/48213097?v=4",
"type": "User",
"publicRepos": 84,
... 8 more fields
}
Uptime
100.00%
30d · 8,600 calls
Requests
8,600
30d · weekly, last 12 wks
Response
1.1s
median · 30d

Pricing and providers

GitHub User API pricing: one API, 3 interchangeable providers

The cheapest provider serves first. If it fails, the next one takes over in the same call.

You pay
$12.00
$1.20/1k req, only for what you use. No monthly plan.
Your first 83 requests are free with the $0.10 starting balance.

Try it

Get GitHub user in one request

Open in
Get a free key
Sample response
Free runs return only the first 3 results. Fund a key to get the full response.

This sample shows 14 of 19 fields. See every field

{
  "found": true,
  "data": {
    "login": "mira-devbuilds",
    "name": "Mira Chen",
    "bio": "Building developer tools. Previously @stripe. OSS maintainer of gridline-cli.",
    "company": "@opengridlabs",
    "location": "Seattle, WA",
    "avatarUrl": "https://avatars.githubusercontent.com/u/48213097?v=4",
    "type": "User",
    "publicRepos": 84,
    "publicGists": 12,
    "followers": 3420,
    "following": 156,
    "createdUtc": 1394668800
  }
}

Full parameter and response reference - every field, type, and example for this endpoint.

Reference

One request, one response shape.

Every field you send and every field you get back, each with a real example.

Last verified 2026-10-31 · uptime and latency measured over 30d

Request body

JSON, posted to this endpoint.

  • handlestring

    mira-devbuilds

    GitHub username.

You send. A small JSON body. The values shown are examples to replace with your own.

Response

JSON, one example value per field.

datadata

The user profile record, or null when not found.

  • avatarUrlstring

    https://avatars.githubusercontent.com/u/48213097?v=4

    URL of the profile avatar image. Populated whenever the provider has data for the entity.

  • biostring

    Building developer tools. Previously @stripe. OSS maintainer of gridline-cli.

    Profile bio text.

  • blogstring

    Blog or website URL from the profile.

  • companystring

    @opengridlabs

    Company listed on the profile.

  • createdUtcnumber

    1394668800

    UTC epoch timestamp in seconds (Unix time). Multiply by 1000 for a JS Date in milliseconds. Populated whenever the provider has data for the entity.

  • followersinteger

    3420

    Number of followers.

  • followinginteger

    156

    Number of accounts the user follows.

  • idstring

    GitHub's numeric user id, as a string.

  • locationstring

    Seattle, WA

    Location listed on the profile.

  • loginstring

    mira-devbuilds

    GitHub username (handle). Populated whenever the provider has data for the entity.

  • namestring

    Mira Chen

    Display name, or empty string if unset. Populated whenever the provider has data for the entity.

  • profileUrlstring

    Canonical GitHub profile URL.

  • publicGistsinteger

    12

    Count of public gists.

  • publicReposinteger

    84

    Count of public repositories.

  • twitterUsernamestring

    Linked X/Twitter username.

  • typestring

    User

    "User" or "Organization".

top level
  • foundboolean

    true

    Whether a user was found for the requested handle.

  • reason"not_found"

    Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.

You get back. Named, typed fields in the same shape whichever source answers.

FAQ

About the GitHub User API

The AnyAPI GitHub User API returns GitHub user data as normalized JSON from one POST call to /v1/run/github.user. Fetch a GitHub user's public profile by handle (name, bio, company, location, followers, and repo counts). AnyAPI routes each request across 3 sources and falls back automatically when one fails. It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of GitHub user calls through AnyAPI succeeded, with a median response time of 1.1 seconds across 8,600 measured calls.

It costs from $1.20 per 1,000 requests, in US dollars with no subscription and no monthly minimum. You fund one USD wallet and each call draws it down. Some failed wallet-funded requests incur processing charges that we pass through at cost, with no markup; the error response shows the amount charged.

Fetch a GitHub user's public profile by handle (name, bio, company, location, followers, and repo counts). The response is normalized JSON with the same envelope every AnyAPI endpoint returns, so parsing a second endpoint is a change of URL and nothing else.

Over the last 30 days, 100.0% of GitHub user calls through AnyAPI succeeded, with a median response time of 1.1 seconds across 8,600 measured calls. These are AnyAPI's own measurements of traffic through the gateway, recomputed continuously, not a published service-level target.

Yes. A new AnyAPI account starts with $0.10 of free balance and no card required, which covers 83 GitHub User calls at $0.0012 each.

AnyAPI asks the next of its 3 sources in the same request, cheapest first, so one source going down does not fail your call.

Send a POST request to https://api.getanyapi.com/v1/run/github.user with your AnyAPI key in an "Authorization: Bearer" header and the input as a JSON body. The same key and the same wallet work on every AnyAPI endpoint.

No. You add US dollars to one prepaid AnyAPI balance and each request draws it down. There is no monthly plan and no minimum, and the same balance pays for every AnyAPI endpoint.

Yes. Install @getanyapi/sdk from npm for TypeScript or getanyapi from pip for Python. Both call every AnyAPI endpoint with the same key, and any HTTP client works too.

Yes. An agent can connect to the AnyAPI MCP server at https://api.getanyapi.com/mcp, or create its own free-trial key with one unauthenticated POST to https://api.getanyapi.com/agent/signup and call this endpoint over HTTP.