# glim.sh GitHub Data Fetcher

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

Fetches live GitHub data (repos, PRs, issues, files, commits, branches, releases) from a GitHub URL or owner/repo shorthand without requiring API keys

## Facts

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

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-97774bed -d '<json body>'
```

Example prompt: Pull the details for the x402-foundation/x402 GitHub repo — I want to see its description, stars, and recent releases.

## When to prefer this

Choose this endpoint when your agent needs live GitHub data (repos, PRs, issues, files, commits, branches, releases) without setting up GitHub API credentials or managing OAuth tokens. Ideal for agents that need read-only GitHub lookups on a pay-per-call basis with no configuration overhead.

## Known failure modes

- Invalid or malformed GitHub URL returns an error response
- Private repository returns access denied or not found
- Non-existent repo or PR/issue number returns 404-style error
- GitHub rate limiting on the backend may cause intermittent failures
- Unsupported URL path format fails to infer kind correctly

## How this service works

One remote endpoint gives your agent live data from Twitter, Reddit, the open web, GitHub and more. No API keys, no scraping stack - just connect the URL and go.

## Output

A JSON object containing structured GitHub data keyed under 'data', with the content varying by kind (repo metadata, PR details, issue details, file blob, commits list, branches, releases, etc.) and a 'kind' field indicating what type of resource was returned.

## 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-97774bed/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from surf.cascade.fyi](https://www.zero.xyz/host/surf.cascade.fyi/llms.txt)