# x402 Repo Health Checker

> x402 Repo Health Checker is a paid API for AI agents from x402-repohealth-poc.theliminalguy.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-14).

Returns a computed maintenance/abandonment verdict with score and reasoning for any GitHub repository, fetched live from GitHub data

## Facts

- Endpoint: GET https://x402-repohealth-poc.theliminalguy.workers.dev/repo-health/facebook/react?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-repo-health-checker-36bb7a68
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fxNTguTL7TFZGBZE7Y49N

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 x402-repo-health-checker-36bb7a68
```

Example prompt: Can you check the repo health of facebook/react on GitHub and tell me whether it's actively maintained, along with its health score and the reasoning?

## When to prefer this

Choose this endpoint when you need a quick, pre-computed verdict on whether a specific GitHub repository is actively maintained or abandoned, especially before adding a dependency or evaluating an open source project. It is ideal for agents that need a single health score with reasoning rather than raw GitHub metrics, and when you want to avoid building your own GitHub data aggregation logic. Prefer this over manually inspecting GitHub REST API endpoints when a synthesized, scored verdict is needed.

## Known failure modes

- Repository not found (invalid owner or repo name) — likely returns 404 or error JSON
- GitHub API rate limiting or downtime causing upstream failures
- Private repositories that cannot be accessed publicly
- Payment not processed correctly via x402 protocol — request blocked
- Ambiguous or misspelled repo path returns no data

## How this service works

Computed repo maintenance/abandonment verdict (score + reasoning) from live GitHub data

## Output

A JSON response containing a numerical health/maintenance score, a categorical verdict (e.g. active, at-risk, abandoned), and human-readable reasoning based on live GitHub signals such as commit frequency, issue activity, PR activity, and last update timestamps.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-repo-health-checker-36bb7a68/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-repohealth-poc.theliminalguy.workers.dev](https://www.zero.xyz/host/x402-repohealth-poc.theliminalguy.workers.dev/llms.txt)