# NAKONETS CI Triage - GitHub Actions Log Analyzer

> NAKONETS CI Triage - GitHub Actions Log Analyzer is a paid API for AI agents from x402vercel.vercel.app, paid per call via x402, $0.5/call, status unknown (last checked 2026-10-02).

Analyzes GitHub Actions failure log text to identify root cause class and extract key error evidence snippets

## Facts

- Endpoint: POST https://x402vercel.vercel.app/api/ci/triage?utm_source=zero.xyz
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nakonets-ci-triage-github-actions-log-analyzer-a0cce097
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Saq1nr2DH8fByeI7Ismld

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 nakonets-ci-triage-github-actions-log-analyzer-a0cce097 -d '<json body>'
```

Example prompt: My GitHub Actions workflow just failed — can you triage this log and tell me what root cause class it falls under and what the key error evidence is? Here's the log: 'Error: Cannot find module @octokit/rest\n    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)'

## When to prefer this

Choose this endpoint when you have a raw GitHub Actions failure log and need a fast, deterministic classification of the root cause category along with extracted evidence lines — particularly useful in automated agent workflows where you want to branch logic based on failure type (e.g. retry on flaky test vs fix dependency vs fix syntax) without manual log reading.

## Known failure modes

- Empty or malformed log string returns unclear classification
- Very long logs may exceed input limits or produce lower-confidence results
- Ambiguous or multi-failure logs may yield a single rootCauseClass that doesn't cover all issues
- Non-GitHub-Actions log formats may produce incorrect evidence extraction
- Network or payment processing failures return HTTP 402 or 5xx errors

## How this service works

Pay-per-call deterministic utilities for CI diagnosis, data validation, JavaScript syntax checks, market snapshots and opportunity preflight.

## Output

Returns a JSON object with an 'evidence' array of extracted error strings from the log (e.g. specific failing lines or module names) and a 'rootCauseClass' string categorizing the failure type (e.g. 'dependency', 'syntax', 'configuration').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "log": {
   "type": "string",
   "description": "GitHub Actions failure log text"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "evidence": [
   "Error: Cannot find module foo"
  ],
  "rootCauseClass": "dependency"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nakonets-ci-triage-github-actions-log-analyzer-a0cce097/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402vercel.vercel.app](https://www.zero.xyz/host/x402vercel.vercel.app/llms.txt)