# glim.sh GitHub Data Fetcher

> glim.sh GitHub Data Fetcher is a paid API for AI agents from glim.sh, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Fetches live GitHub repository, pull request, issue, file, branch, commit, or release data from a given GitHub URL or owner/repo shorthand, with no API key required.

## Facts

- Endpoint: POST https://glim.sh/api/v1/github/get
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/glim-sh-github-data-fetcher-b00c9964
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_enwlr_ah-WYjHf2W1lxt8

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 glim-sh-github-data-fetcher-b00c9964 -d '<json body>'
```

Example prompt: Can you pull up the details for the GitHub repo x402-foundation/x402 — I want to see its description, stars, and any other metadata available?

## When to prefer this

Use this endpoint when your agent needs live, structured GitHub data (repos, PRs, issues, files, commits, branches, releases) without managing GitHub API keys or OAuth tokens. Ideal for agents that need to inspect open-source projects, check PR status, or read file contents on demand, paying only per call via x402.

## Known failure modes

- Invalid or malformed GitHub URL/shorthand returns an error
- Private repository returns access-denied error since no auth is passed
- Rate limiting on the underlying GitHub data source may cause intermittent failures
- Unsupported path type (e.g. GitHub Actions, Gists) may not be parsed correctly
- Pagination beyond available pages returns empty results

## How this service works

Fetch GitHub data from a ref (repo + README, files, commits, PRs, issues, discussions)

## Output

A JSON object containing structured GitHub data keyed by `kind` (e.g. 'repo', 'pull', 'issue', 'blob', 'tree', 'commits', 'branches', 'releases') and a `data` field with the relevant metadata — such as full_name, description, open issues count, stars, files, or commit messages, depending on the path inferred from the ref.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ref": {
   "type": "string",
   "maxLength": 2048,
   "minLength": 1,
   "description": "GitHub URL or 'owner/repo' shorthand. A repo URL or owner/repo returns metadata + README; /pull/N -> PR (with comments + changed files), /issues/N -> issue, /discussions/N -> discussion (with threaded replies), /blob/<ref>/<path> -> file (raw.githubusercontent.com URLs work too), /tree/<ref>[/<path>] -> file tree (optionally scoped to a subdirectory), /commit/<sha> -> one commit with diff, /commits[/<ref>/<path>] -> history (optionally for one file), /branches, /releases (or /releases/tag/<tag> | /releases/latest -> one release), /topics/<name> -> top repos with that topic (by stars)."
  },
  "page": {
   "type": "integer",
   "default": 1,
   "maximum": 100,
   "minimum": 1,
   "description": "Page number for paginated results"
  },
  "per_page": {
   "type": "integer",
   "default": 30,
   "maximum": 100,
   "minimum": 1,
   "description": "Results per page"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "full_name": "x402-foundation/x402",
   "description": "..."
  },
  "kind": "repo"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/glim-sh-github-data-fetcher-b00c9964/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from glim.sh](https://www.zero.xyz/host/glim.sh/llms.txt)