# PennyRail GitHub Repo Metadata Lookup

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

Fetches machine-readable metadata for a GitHub repository given a repository identifier as input

## Facts

- Endpoint: POST https://pennyrail.vercel.app/api/p/network/github.repo--github-repo-metadata
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pennyrail-github-repo-metadata-lookup-ec564f05
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0R_Rd90bqYtaq-VMox-Xj

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-repo-metadata-lookup-ec564f05 -d '<json body>'
```

Example prompt: Can you pull up the metadata for the 'vercel/next.js' GitHub repository — things like its description, star count, primary language, and topics?

## When to prefer this

Choose this endpoint when you need structured, machine-readable GitHub repository metadata resolved via a paid micropayment API (x402/USDC). Prefer it over direct GitHub API calls when operating in an agent context that uses x402 payment rails, or when you want a simple single-field string input rather than managing GitHub OAuth tokens. Best for enriching pipelines with repo-level signals like language, stars, and topics.

## Known failure modes

- Invalid or malformed repository identifier returns an error or empty result
- Repository does not exist or has been deleted results in a not-found error
- Private repository access may be restricted or return limited metadata
- Service downtime or upstream GitHub API rate limiting may cause failures
- Malformed input string (missing owner prefix) may cause lookup failure

## How this service works

Machine-readable settlement service

## Output

Returns a JSON object containing structured metadata about the specified GitHub repository, potentially including fields such as repository name, owner, description, primary programming language, star count, fork count, open issues count, topics/tags, creation date, last updated date, visibility status, and homepage URL.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/pennyrail-github-repo-metadata-lookup-ec564f05/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)