# Repo Radar — GitHub Repository Readiness Audit

> Repo Radar — GitHub Repository Readiness Audit is a paid API for AI agents from repo-radar-audit-5.sebasvega55371.chatgpt.site, paid per call via x402, $5/call, status unknown (last checked 2026-09-16).

Audits a public GitHub repository for readiness signals including documentation, test coverage, language detection, and potential credential exposure.

## Facts

- Endpoint: POST https://repo-radar-audit-5.sebasvega55371.chatgpt.site/api/repo-readiness
- Price: $5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/repo-radar-github-repository-readiness-audit-1771a335
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zHal5U1mMSmZrQPyMXl5H

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 repo-radar-github-repository-readiness-audit-1771a335 -d '<json body>'
```

Example prompt: Can you run a readiness audit on the GitHub repo at https://github.com/expressjs/express and tell me if it has tests, documentation, and any potential credential exposures?

## When to prefer this

Choose this endpoint when you need a quick, structured readiness snapshot of a public GitHub repository — particularly when you want a single call that combines documentation, testing, and credential-exposure signals without scraping GitHub manually. It is especially useful for automated due-diligence pipelines, dependency vetting, or pre-adoption security reviews.

## Known failure modes

- Invalid or non-public GitHub repository URL returns an error
- Repository not found or private returns a 404-equivalent response
- Malformed repo URL query parameter causes a validation error
- Payment not received results in a 402 Payment Required response
- Rate limiting or upstream GitHub API unavailability may cause transient failures

## How this service works

Inspect a public GitHub repository with a US$1 Quick Scan or US$5 full release-readiness audit. Pay per call with x402 USDC on Base.

## Output

Returns a JSON object with the repository identifier, a summary object (including whether the repo has tests, its detected programming languages, and documentation status), and a security object listing potential credential exposure locations.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "summary": {
   "tests": true,
   "languages": [
    "TypeScript"
   ],
   "documentation": true
  },
  "security": {
   "potentialCredentialLocations": []
  },
  "repository": "owner/repository"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/repo-radar-github-repository-readiness-audit-1771a335/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from repo-radar-audit-5.sebasvega55371.chatgpt.site](https://www.zero.xyz/host/repo-radar-audit-5.sebasvega55371.chatgpt.site/llms.txt)