GitHub API

GitHub users and organizations with their repositories, pull requests, activity, followers and contribution graphs, plus trending repositories and developers.

When To Use This APICopy Anchor Link

The GitHub API is for agent workflows that need public, platform-native data without writing a custom collector for every task. Use it when a prompt needs evidence from live public records, when a Skill needs repeatable enrichment, or when product code needs the same contract an agent discovered through MCP.

This section lists 10 live GitHub operations from the canonical OpenAPI spec. Each operation page documents the route, method, parameters, response envelope, pagination behavior when available, and the error vocabulary shared across UnifAPI.

• Source engineers from public profiles, repositories, pull requests and contribution activity.
• Track trending repositories and developers by language to spot new tools and communities.
• Compare open-source projects by stars, forks, open issues, license and recent pushes.

Agent Contract NotesCopy Anchor Link

Agents usually discover these endpoints with the hosted UnifAPI MCP server, inspect the operation schema, then call only the records needed for the current task. Developers can call the same endpoints over HTTP with an API key, which makes the path from exploratory agent run to production integration direct.

Every successful response uses a stable envelope with a request id, data payload, optional pagination cursor, and billing metadata. Errors use the same closed vocabulary across platforms, so retry logic, user-facing explanations, and cost reporting can stay consistent even when a workflow spans multiple public-data sources.

When you are choosing an operation, start from the public identifier the user already has: a profile username, post id, channel id, subreddit name, search term, or URL-derived slug. Prefer the narrowest endpoint that answers the question, then expand only when the agent needs more evidence. This keeps record usage predictable, makes citations easier to explain, and avoids turning a focused research task into an expensive crawl.

OperationsCopy Anchor Link

ReposCopy Anchor Link

• GET /github/repos/{owner}/{repo} — Get a GitHub repository — Returns a public GitHub repository: description, topics, license, default branch, languages, stars, forks, watchers and open issues.

TrendsCopy Anchor Link

• GET /github/trending/developers — List trending GitHub developers — Returns GitHub's trending developers for a time window, optionally for one programming language, with each developer's popular repository.
• GET /github/trending/repos — List trending GitHub repositories — Returns GitHub's trending repositories for a time window (daily, weekly, monthly), optionally for one programming or spoken language, with stars gained in the window.

UsersCopy Anchor Link

• GET /github/users/{username}/activity — List a GitHub user's public activity — Returns a GitHub user's public activity one month at a time (commits, pull requests, issues, reviews).
• GET /github/users/{username}/contributions — Get a GitHub user's contribution graph — Returns a GitHub user's daily contribution counts and total for one calendar year (default: the current year).
• GET /github/users/{username}/followers — List a GitHub account's followers — Returns the accounts that follow a GitHub user or organization.
• GET /github/users/{username}/following — List accounts a GitHub user follows — Returns the accounts a GitHub user follows.
• GET /github/users/{username}/pull-requests — List pull requests by a GitHub user — Returns public pull requests authored by a GitHub user, optionally between since and until, with repository, state and timestamps.
• GET /github/users/{username}/repos — List a GitHub account's repositories — Returns the public repositories of a GitHub user or organization with language, stars, forks and update times.
• GET /github/users/{username} — Get a GitHub user or organization — Returns a public GitHub user or organization profile: name, bio, company, location, blog, follower and repository counts.