# NAKONETS CI Diagnosis Endpoint

> NAKONETS CI Diagnosis Endpoint is a paid API for AI agents from x402vercel.vercel.app, paid per call via x402, $2/call, status unknown (last checked 2026-10-02).

Analyzes GitHub Actions failure logs to identify the root cause, classify the error category, and recommend actionable remediation steps

## Facts

- Endpoint: POST https://x402vercel.vercel.app/api/ci/diagnose?utm_source=zero.xyz
- Price: $2/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-diagnosis-endpoint-6f385d69
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Tk4WR0pjiOUgmyGMEM_qn

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-diagnosis-endpoint-6f385d69 -d '<json body>'
```

Example prompt: My GitHub Actions build just failed — can you diagnose this log and tell me what the root cause is and how to fix it? Here's the log: 'Error: Cannot find module foo\n    at Function.Module._resolveFilename...'

## When to prefer this

Choose this endpoint when you need a deterministic, structured diagnosis of a GitHub Actions CI failure log — especially when you want a machine-readable rootCauseClass and a concrete action list for automated remediation workflows. Prefer this over LLM free-form analysis when you need consistent, reproducible categorization of build errors that can be used in downstream automation.

## Known failure modes

- Empty or malformed log text may yield a generic or low-confidence diagnosis
- Logs from non-standard CI systems may not be correctly parsed
- Very long logs may be truncated or processed partially
- If the error is ambiguous, the rootCauseClass may be overly broad
- Payment failure ($2 USDC) will prevent the call from being processed

## 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: a 'status' field ('diagnosed'), a 'rootCauseClass' string categorizing the error type (e.g. 'dependency'), the 'primaryError' string extracted from the log, an 'evidence' array of log snippets supporting the diagnosis, and an 'actions' array of recommended remediation steps.

## 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": {
  "status": "diagnosed",
  "actions": [
   "Verify dependency declarations and lockfile consistency."
  ],
  "evidence": [
   "Error: Cannot find module foo"
  ],
  "primaryError": "Error: Cannot find module foo",
  "rootCauseClass": "dependency"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nakonets-ci-diagnosis-endpoint-6f385d69/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)