# SALT19 GitHub Repo Preflight Check

> SALT19 GitHub Repo Preflight Check is a paid API for AI agents from salt19-agent-utility-grid.salt19-llc.workers.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-15).

Fetches key metadata and risk flags for a GitHub repository to support automated dependency and integration decisions.

## Facts

- Endpoint: POST https://salt19-agent-utility-grid.salt19-llc.workers.dev/v1/github-repo-preflight
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/salt19-github-repo-preflight-check-0723b0e1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MUPa6wDwis9AzIHYypy-6

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 salt19-github-repo-preflight-check-0723b0e1 -d '<json body>'
```

Example prompt: Before I add it as a dependency, can you run a preflight check on the cloudflare/workers-sdk GitHub repo and tell me its license, whether it's archived, how many open issues it has, and when it was last pushed to?

## When to prefer this

Use this endpoint when an autonomous agent needs to make a quick, structured decision about a GitHub repository — such as before adding a dependency, evaluating a vendor's open source library, or running compliance checks. It consolidates license, activity, and risk data into a single call with a flat fee, making it ideal for agent pipelines that need deterministic, machine-readable preflight signals without managing GitHub API credentials.

## Known failure modes

- Invalid or non-existent repo string returns an error or empty result
- Private repositories may not be accessible and could return an access error
- Rate limiting on the underlying GitHub API may cause transient failures
- Malformed repo string (missing owner prefix) may result in a parse or lookup error

## How this service works

Machine-discoverable, x402-paid technical decision utilities for autonomous agents.

## Output

A JSON object containing the repository's license identifier, archived status (boolean), open issues count, default branch name, days since last push, and an array of risk flags (which is empty if no issues are detected).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "repo": {
   "type": "string",
   "maxLength": 512
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "license": "Apache-2.0",
  "archived": false,
  "repository": "cloudflare/workers-sdk",
  "risk_flags": [],
  "open_issues": 123,
  "default_branch": "main",
  "days_since_push": 1
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/salt19-github-repo-preflight-check-0723b0e1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from salt19-agent-utility-grid.salt19-llc.workers.dev](https://www.zero.xyz/host/salt19-agent-utility-grid.salt19-llc.workers.dev/llms.txt)