# PennyRail GitHub Repository Lookup

> PennyRail GitHub Repository Lookup is a paid API for AI agents from pennyrail.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Fetches machine-readable data about a GitHub repository given its owner/repo identifier

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/f/github.repo
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-github-repository-lookup-8ce09238
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IJWvZtSSQfoEJSetqZvYl

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 pennyrail-github-repository-lookup-8ce09238 -d '<json body>'
```

Example prompt: Can you pull up the repository info for coinbase/agentkit on GitHub and give me the details in a readable format?

## When to prefer this

Use this endpoint when you need quick, pay-per-call access to GitHub repository metadata without managing your own GitHub API credentials or OAuth tokens. It is well-suited for agent pipelines that need on-demand, per-repo lookups at low cost ($0.001 USDC) and want a simple owner/repo string as the only input. Prefer alternatives if you need bulk repository queries, advanced search across GitHub, or access to GitHub features beyond basic repo metadata.

## Known failure modes

- Invalid owner/repo format returns an error result
- Private or non-existent repositories return a not-found or access-denied response
- Malformed input string (missing slash separator) may cause a parse error
- GitHub API rate limiting downstream may cause intermittent failures
- Payment failure (insufficient USDC balance) blocks the call entirely

## How this service works

Machine-readable settlement service

## Output

A JSON object containing an 'operation' string describing what was performed and a 'result' field with the repository data returned from GitHub (e.g. description, stars, language, forks, and other repository metadata). The schema is open-ended and may include additional fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "string",
   "description": "owner/repo"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "operation",
  "result"
 ],
 "properties": {
  "result": {},
  "operation": {
   "type": "string"
  }
 },
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyrail-github-repository-lookup-8ce09238/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pennyrail.vercel.app](https://www.zero.xyz/host/pennyrail.vercel.app/llms.txt)
