What is gitBeacon?
gitBeacon is a pay-per-call GitHub trend intelligence API for AI agents and developers: a daily scan of trending new GitHub repos, LLM-analyzed into a structured digest — dominant categories, emerging tools, language trends, notable projects, and overall sentiment — plus the raw enriched trending-repo rows behind it. It is priced per call in USDC on Base over the x402 protocol, with no accounts and no API keys, so an autonomous agent can pull developer-ecosystem signals directly.
What you get
- $0.01
GET /v1/reposTop trending repos
- $0.05
GET /v1/digestsHistorical GitHub digests
Free digest feeds — /v1/index, /v1/brief, /v1/digests/latest, and a frozen /v1/sample — need no payment. Paid routes start at $0.01.
How agents pay
Call a paid endpoint with no payment and gitBeacon answers HTTP 402 with the exact price. Your agent signs an EIP-3009 USDC authorization on Base and retries the same request with the payment header; structured JSON comes back after settlement. Stock x402 clients do the round-trip automatically. You are never charged for an error.
$ curl https://api.gitbeacon.dev/v1/repos
HTTP/2 402 Payment Required
# agent signs a USDC payment on Base and retries
HTTP/2 200 OKAlternatives
GitHub’s trending page and REST/GraphQL API. GitHub’s own trending page and search API are free and authoritative for raw repo metadata. That is the right choice if you want to build your own scanning, enrichment, and ranking. gitBeacon differs by delivering the trend already digested: an LLM synthesizes the day into categories, emerging tools, and sentiment, and the raw rows are pre-enriched (stars, forks, topics, license, author, README excerpt).
Newsletter and digest products. Human-curated developer newsletters cover similar ground in prose for people to read. gitBeacon is built for machines instead: structured JSON, per-call payment, and provenance fields — so an agent can consume and reason over the trend rather than parse an email.
FAQ
- Does gitBeacon need an API key or account?
- No. gitBeacon has no signups, no API keys, and no dashboards. Free digest feeds are open reads; the paid repos and historical-digest routes answer with an x402 payment challenge that a wallet settles per call.
- How does an agent pay for a gitBeacon call?
- A paid endpoint returns an HTTP 402 challenge with the exact price. The agent signs an EIP-3009 USDC authorization on Base and retries with the payment header; the JSON comes back after settlement. Stock x402 clients automate this.
- How fresh is the trending data?
- gitBeacon runs a daily scan of trending new GitHub repos, and paid rows carry scanDate/digestDate provenance so you always know how fresh the data is. Poll the free /v1/index feed (24h cadence) to detect a new digest, then pull the current digest or raw repos.
- Can I try gitBeacon before paying?
- Yes. /v1/sample is a frozen sample digest that shows the exact response shape with no payment, and /v1/brief, /v1/index, and /v1/digests/latest are live free reads of the current digest.