Best GitHub API in 2026: Pricing Compared

Best GitHub API in 2026 by listed price: 16 SandBase endpoints from $0.0012, beside official REST rate limits. Official per-call prices stay Unknown.

Split typographic cover: Best GitHub API 2026, repositories, issues, users.

A public repository read and an issue-and-pull-request search are both on the same SandBase hub, and they do not share a price. On the 21 Nov 2026 catalog check (Asia/Shanghai), GitHub on SandBase listed 16 endpoints. Fifteen cards were priced From $0.0012 per call. Issue and PR Search was From $0.0024 per call. Every one of those prices is a floor. Official GitHub REST is a different product: it meters public data with rate limits, and GitHub plans and pricing sells account plans, not a per-call data-API invoice. Accuracy and latency against other vendors stay Unknown, because this article did not run that comparison.

Key takeaway

  • On 21 Nov 2026 the SandBase GitHub hub listed 16 endpoints. Fifteen were From $0.0012 per call. Issue and PR Search was From $0.0024. Every listed price is a floor.
  • Representative cards opened that day (Repository, User, Issue and PR Search, Trending Repositories) did not show a “100 free calls / day” row. Do not treat this hub as free-quota eligible.
  • Official REST rate limits, from GitHub Docs the same day: 60 unauthenticated requests per hour per IP, 5,000 per hour for an authenticated personal limit, and 15,000 per hour in eligible GitHub Enterprise Cloud app contexts. Account plans on github.com/pricing were Free $0, Team $4 per user per month, and Enterprise $21 per user per month.
  • Official per-call dollar prices stay Unknown. One thousand calls at the $0.0012 floor are $1.20 only as list-price floor math, not a bill.
  • Call POST https://api.sandbase.ai/v1/api/github/{endpoint} with a Bearer key. These representative cards were not flagged asynchronous. Do not start the call with POST /v1/run.

What a GitHub API means in 2026

The phrase covers three purchases. Only one of them is the 16-card hub.

The first is GitHub’s official REST API, and the GraphQL API that sits beside it for authorized app work. On 21 Nov 2026, Rate limits for the REST API returned the title “Rate limits for the REST API - GitHub Docs.” Unauthenticated public-data requests are 60 per hour per IP. The authenticated personal limit is 5,000 requests per hour. Eligible GitHub Enterprise Cloud app contexts are documented at 15,000 requests per hour. Those are ceilings on request volume, not a dollar rate card. GitHub plans and pricing returned “GitHub plans and pricing · GitHub” and listed Free at $0, Team at $4 per user per month, and Enterprise at $21 per user per month. Those are seats for a GitHub account. They are not the price of a repository-research call.

The second purchase is a separate unofficial vendor account: another contract, another key, and a price on that vendor’s own site. This article does not name those vendors or borrow anyone else’s accuracy scores.

The third is the SandBase hub. The HTML title was “GitHub APIs: Repositories, Issues, Users and Trending | SandBase.” The Markdown twin counted 16 endpoints and described them as GitHub data API endpoints available through one SandBase API key. SandBase is not GitHub. A catalog row does not grant OAuth app approval, and official GitHub terms still apply to how you use the records.

A webhook, a commit status, or a private org you are authorized to access stays on the rate-limited official API. The catalog is for public research cards with a listed floor.

GitHub endpoints you can call on SandBase today

The wider data API index listed 2,247 endpoints from 182 providers on the same check. Do not flatten this hub to From $0.0012. Issue and PR Search is the one higher floor.

CardList price, 21 Nov 2026CallWhat the card describesAsyncFree allowance
RepositoryFrom $0.0012 per callPOST /v1/api/github/repositoryRepository metadataNot flaggedNo visible row
UserFrom $0.0012 per callPOST /v1/api/github/userA public user profileNot flaggedNo visible row
Issue CommentsFrom $0.0012 per callPOST /v1/api/github/issue-commentsComments on an issueNot flaggedNo visible row
Trending RepositoriesFrom $0.0012 per callPOST /v1/api/github/trending-repositoriesTrending repository listNot flaggedNo visible row
Issue and PR SearchFrom $0.0024 per callPOST /v1/api/github/search-issuesIssue and pull-request searchNot flaggedNo visible row

“From” is a floor. This article does not state a ceiling. The hub Markdown, whose other cards were not each re-opened as HTML, also listed the same From $0.0012 floor for repository contributors, forks, issues, README, trending developers, user activity, contributions, followers, following, user pull requests, and user repositories. That is the rest of the 16. GitHub does not appear on the pricing-page allowance sample. The live tool cards above did not show the row “100 free calls / day — First 100 calls per day free (shared per organization) · Resets at 00:00 UTC. Pay per call after that.” Do not describe these cards, or the hub as a whole, as free-quota eligible.

SandBase GitHub hub with 16 research endpoints

SandBase GitHub hub, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “GitHub APIs: Repositories, Issues, Users and Trending | SandBase.” The page is the 16-endpoint catalog. Listed prices are From floors.

SandBase GitHub Repository card

SandBase GitHub Repository card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “GitHub Repository API: Pricing & Specs | SandBase.” The Markdown price was From $0.0012 per call. The card did not show a 100-free-calls row.

SandBase GitHub User card

SandBase GitHub User card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “GitHub User API: Pricing & Specs | SandBase.” The Markdown price was From $0.0012 per call. The card did not show a 100-free-calls row.

SandBase GitHub Issue and PR Search card

SandBase GitHub Issue and PR Search card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “GitHub Issue and PR Search API: Pricing & Specs | SandBase.” The Markdown price was From $0.0024 per call, the higher floor on this hub.

SandBase GitHub Trending Repositories card

SandBase GitHub Trending Repositories card, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “GitHub Trending Repositories API: Pricing & Specs | SandBase.” The Markdown price was From $0.0012 per call.

Official GitHub API pricing versus the SandBase catalog

The rows are different products. The table is not a rank. Latency and accuracy are Unknown in every row.

PathWhat you can call, as checked 21 Nov 2026BillingFree trial or allowanceDocs
Official GitHub RESTPublic data under documented rate limits. Authenticated apps, OAuth, and partner surfaces for repositories you are authorized to access.No per-call invoice on the pages fetched. Rate limits: 60/hour unauthenticated per IP, 5,000/hour authenticated personal, 15,000/hour in eligible Enterprise Cloud app contexts. Account plans: Free $0, Team $4/user/month, Enterprise $21/user/month.The rate limit is the allowance. A dollar free tier for research calls was not stated.Rate limits and plans
SandBase GitHub hub16 research endpoints. Fifteen From $0.0012. Issue and PR Search From $0.0024.Pay per call, no subscription. Start ($0), Build (Metered), Scale (Custom). “From” is a floor.The representative cards did not show a free-calls row. Eligible data APIs elsewhere share 100 free calls per organization per UTC day.Live cards plus API passthrough
A separate unofficial vendor accountWhatever that vendor lists. Not measured here.That vendor’s contract. Unknown here.Unknown here.That vendor’s own docs

A dollar comparison against official GitHub REST cannot be computed while official per-call prices are Unknown. Seat prices are not a substitute. Copilot and the GitHub MCP server are a different cluster: they help an agent act on a repository you already have access to. They are not this rate card. See the GitHub MCP Server guide only if that is the job.

Best GitHub API for each need

  • Lowest listed floor: the 15-card family at From $0.0012, including Repository, User, Issue Comments, and Trending Repositories. Budget that figure as a minimum.
  • Issue and pull-request search: From $0.0024. It is the only higher floor on the hub list.
  • Confirmed free-quota cards: none of the cards opened here. Official REST, GraphQL, OAuth apps, and webhooks stay on GitHub.
  • Public channel research on another hub is a different catalog. The Telegram pricing post is the nearest new pillar, and it is not a GitHub substitute.

How to call the GitHub API on SandBase

Data APIs use POST https://api.sandbase.ai/v1/api/{vendor}/{endpoint} with Authorization: Bearer $SANDBASE_API_KEY and a JSON body. Language models use POST /v1/chat/completions. Media models use POST /v1/run. Do not start a data API with POST /v1/run. The passthrough reference is the data-API page. The first API call walkthrough is chat completions only.

Repository, User, and Issue and PR Search were not flagged asynchronous on 21 Nov 2026. If a live card later says the endpoint runs asynchronously, the response includes a task id and you poll GET https://api.sandbase.ai/v1/run/{id} until status is completed. That GET is the poll, not the request that starts the call. This comparison did not run a paid call. Replace the empty object with the fields on the live card before you send it. Read outputs[0].data. If that object is missing, fail loudly.

Python
import os
import requests

payload = {}  # replace with the fields on the live Repository card before sending

headers = {
    "Authorization": f"Bearer {os.environ['SANDBASE_API_KEY']}",
    "Content-Type": "application/json",
}
response = requests.post(
    "https://api.sandbase.ai/v1/api/github/repository",
    headers=headers,
    json=payload,
    timeout=90,
)
response.raise_for_status()
body = response.json()
# Repository was not flagged asynchronous on 21 Nov 2026. If the live card says async,
# poll GET /v1/run/{id}. Do not POST /v1/run to start the data API.
outputs = body.get("outputs") or []
if body.get("status") not in (None, "completed") or not outputs or not isinstance(outputs[0], dict):
    raise RuntimeError(f"SandBase call did not complete: {body.get('status')} {body.get('error')}")
data = outputs[0].get("data")

User is the same client with the path /v1/api/github/user. Issue and PR Search is /v1/api/github/search-issues. The snippet is a client sketch, not a measured latency.

SandBase API passthrough reference for the data-API POST path

SandBase API passthrough page, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “API Passthrough.” It documents POST /v1/api/{vendor}/{endpoint} for data APIs. It is not a GitHub price.

What the daily allowance does and does not cover

Pricing and Pricing and Usage, checked 21 Nov 2026, give every organization 100 free data API calls per UTC day for eligible search, social, scraping, e-commerce, and finance tools. The pool is shared across those tools and all org keys, resets at 00:00 UTC, and does not carry over. Language models, media models, and some pricier or formula-priced data APIs (examples on the billing page: some batch endpoints, crawl endpoints, Xiaohongshu PGY, and Douyin Xingtu kol-* routes) are billed from the first call. A card counts as eligible here only when the live tool card shows the free-calls row. These GitHub cards did not. After the 100th eligible call on tools that do qualify, requests still complete and are billed. A zero balance can still spend remaining allowance. Failed calls are not charged. Catalog browsing is $0. Plans are Start ($0), Build (Metered), and Scale (Custom). The sample list is not a complete roster, and GitHub is absent from it.

SandBase pricing page for pay-per-call plans

SandBase pricing page, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “SandBase Pricing: Models, APIs and Usage-Based Billing.” Plans are pay per call. The page is not a GitHub rate card.

SandBase Pricing and Usage guide for the daily data-API allowance

SandBase Pricing and Usage guide, captured logged out in a light theme on 21 Nov 2026 (Asia/Shanghai). The HTML title is “Pricing and Usage.” Eligible data APIs share 100 free calls per organization per UTC day. These GitHub cards are not confirmed eligible.

One thousand Repository calls at the $0.0012 floor are $1.20 only if every call bills at that floor. One thousand Issue and PR Search calls at the $0.0024 floor are $2.40 on the same assumption. That is list-price math, not an invoice. Do not subtract 100 calls. These cards did not show the free-calls row.

When the cards look right, open Console API keys (title “API Keys | SandBase Console | SandBase”), read pricing, and use signup, which currently redirects to sign-in. Agents can start from the SandBase skill file.

When not to use the SandBase GitHub hub

Stay on GitHub for official REST or GraphQL, OAuth apps, webhooks, commit statuses, and partner support for private or authorized organization data. A catalog row is not that license. Official GitHub terms still apply. Stay put when the buying criterion is a measured accuracy or latency rank among unofficial providers. This check did not produce that rank. Copilot agent mode and the Copilot SDK are covered in GitHub Copilot agent mode and the Copilot SDK note. Those posts are not a data-API price comparison.

FAQ

What does “GitHub API” mean in this article?

The 16 SandBase cards on the GitHub hub, checked 21 Nov 2026. Official REST rate limits and GitHub account plans stay on GitHub’s own docs.

When is the SandBase hub a better fit than official GitHub REST?

For a public repository, user, issue-comment, trending, or issue-and-PR search read, billed per call on one key. For an authorized app, a private repository, or a webhook, start with GitHub. Official dollar prices and accuracy ranks stay Unknown.

How much do the SandBase GitHub endpoints cost?

From $0.0012 per call on 15 cards, and From $0.0024 on Issue and PR Search, on the 21 Nov 2026 hub list. “From” is a floor. One thousand calls at the lower floor are $1.20 as floor math only.

Are the first 100 GitHub calls free?

Not on the cards opened here. The live Repository, User, Issue and PR Search, and Trending Repositories cards did not show the shared 100-calls row. Eligible data APIs elsewhere share 100 free calls per organization per UTC day.

How do official GitHub APIs compare with SandBase?

Official REST is rate-limited, and github.com/pricing is an account plan. SandBase lists 16 research endpoints with public per-call floors. Latency and accuracy were not measured.

Do official GitHub terms still apply?

Yes. A catalog price is not an OAuth grant and does not replace GitHub’s terms.

How do I start a call?

POST https://api.sandbase.ai/v1/api/github/repository (or user, search-issues, issue-comments, trending-repositories) with a Bearer key. Do not POST /v1/run to start. Poll GET https://api.sandbase.ai/v1/run/{id} only if that live card says the endpoint is asynchronous.

The MCP setup is a different job: GitHub MCP Server Guide (2026). Public-channel pricing on the same catalog is Best Telegram API in 2026.

Open the GitHub hub, then the Repository or User card beside the passthrough reference. Create a key in the Console, read pricing and Pricing and Usage, or start an agent from the skill file.

Found this useful? Share it