# StableSocial GitHub Followers Scraper

> StableSocial GitHub Followers Scraper is a paid API for AI agents from stablesocial.dev, paid per call via x402, $0.06/call, status unknown (last checked 2026-09-13).

Retrieves the list of followers for a given GitHub user account

## Facts

- Endpoint: POST https://stablesocial.dev/api/sc/github/user/followers
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stablesocial-github-followers-scraper-dadd4028
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uBb65mOcyDGPlw0S69PI_

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability stablesocial-github-followers-scraper-dadd4028 -d '<json body>'
```

Example prompt: Can you scrape the followers list for the GitHub user 'torvalds' and tell me how many people follow them?

## When to prefer this

Use this endpoint when you need programmatic, pay-per-request access to GitHub follower data without managing GitHub API keys or OAuth tokens. Prefer this over the GitHub REST API when you want a simple HTTP POST with per-call micropayment billing (x402/USDC), or when GitHub API rate limits are a concern. Best suited for ad-hoc agent workflows that need follower data for specific users on demand.

## Known failure modes

- GitHub username not found — returns error or empty result
- Private or suspended GitHub account — data unavailable
- Rate limiting or scraping restrictions on GitHub's side causing partial results
- Invalid or missing username parameter in the request body
- Payment failure via x402 protocol preventing the request from completing

## How this service works

Scrape Creators · GitHub — Followers

## Output

Returns a list of GitHub users who follow the specified account, likely including profile details such as username, display name, avatar URL, and follower metadata for each follower entry.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "GitHub user URL, e.g. https://github.com/torvalds."
  },
  "cursor": {
   "type": "number",
   "description": "Cursor from the previous response. Defaults to 1."
  },
  "handle": {
   "type": "string",
   "description": "GitHub username/handle of the user you want the followers for"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stablesocial-github-followers-scraper-dadd4028/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stablesocial.dev](https://www.zero.xyz/host/stablesocial.dev/llms.txt)