# fitze-x402-seller Repository Diligence

> fitze-x402-seller Repository Diligence is a paid API for AI agents from fitze-x402-seller.app.workbuddy.host, paid per call via x402, $0.25/call, status unknown (last checked 2026-10-02).

Analyzes a GitHub repository and returns health metrics including stars, activity, security policy, contributor count, and recent commits for due diligence purposes.

## Facts

- Endpoint: POST https://fitze-x402-seller.app.workbuddy.host/tools/repo_diligence?utm_source=zero.xyz
- Price: $0.25/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fitze-x402-seller-repository-diligence-d2682908
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eB8bj8EaYS6W3nVUwN88s

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 fitze-x402-seller-repository-diligence-d2682908 -d '<json body>'
```

Example prompt: Can you run a due diligence check on the vercel/next.js GitHub repo — I want to know if it's actively maintained, how many stars and contributors it has, whether there's a security policy, and its overall health score?

## When to prefer this

Choose this endpoint when you need a quick, structured health snapshot of a GitHub repository without writing custom GitHub API integration code. It is particularly valuable in automated due diligence pipelines, dependency vetting workflows, or vendor assessments where you want stars, commit activity, security policy, and contributor estimates in one call. Since it requires no API key — just a USDC micropayment — it suits ephemeral agent workflows that cannot manage long-lived credentials.

## Known failure modes

- Invalid or non-existent repo returns an error or empty response
- Private repositories may not be accessible and return no data
- Payment failure (402 not settled) blocks the response
- Malformed owner/name string causes validation error
- Rate limits on the underlying GitHub data source may delay or fail responses

## How this service works

Pay-per-call AI/data tools settled in USDC on Base via x402. No account, no API key — pay the 402 and receive the result. All endpoints also accept a bare hostname without the https:// prefix.

## Output

Returns a JSON object with the repository name, star count, archived boolean, an array of latest commits, whether a security policy exists, a numeric health percentage, and an estimated contributor count — giving a comprehensive snapshot of the repo's maintenance and security posture.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "repo"
 ],
 "properties": {
  "repo": {
   "type": "string",
   "description": "owner/name, URL also accepted"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [],
 "properties": {
  "repo": {
   "type": "string"
  },
  "stars": {
   "type": "number"
  },
  "archived": {
   "type": "boolean"
  },
  "latest_commits": {
   "type": "array",
   "items": {
    "type": "object"
   }
  },
  "security_policy": {
   "type": "boolean"
  },
  "health_percentage": {
   "type": "number"
  },
  "contributors_estimate": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fitze-x402-seller-repository-diligence-d2682908/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fitze-x402-seller.app.workbuddy.host](https://www.zero.xyz/host/fitze-x402-seller.app.workbuddy.host/llms.txt)