# AgentWork CI/Error Log Triage

> AgentWork CI/Error Log Triage is a paid API for AI agents from api.agentwork.run, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-14).

Analyzes a failing CI build or runtime error log and returns an ordered diagnosis, likely root cause, and concrete fix steps.

## Facts

- Endpoint: POST https://api.agentwork.run/v1/jobs/code.fix_from_log
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentwork-ci-error-log-triage-121b5d29
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Z4pZABiI36bNo9HIVgu1u

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 agentwork-ci-error-log-triage-121b5d29 -d '<json body>'
```

Example prompt: Here's the log from my failing GitHub Actions build — can you triage it, tell me what the root cause is, and give me concrete steps to fix it? [paste log here]

## When to prefer this

Choose this endpoint when you have a raw CI, build, or runtime error log and need automated triage with a prioritized root cause and fix steps — especially useful in agent pipelines that monitor build systems and need to self-heal or notify engineers with actionable remediation. Prefer over general-purpose LLM chat when you need structured, rebuyable diagnosis tied to a payment trail and want deterministic per-failure billing.

## Known failure modes

- Log too large or truncated — may result in incomplete diagnosis
- Ambiguous or overly generic log output without clear error signals — diagnosis may be low-confidence
- Unsupported log format or language — may produce irrelevant suggestions
- Payment failure on USDC rails — call rejected before processing
- Rate limiting or service unavailability — 429 or 503 responses

## How this service works

CI/error log triage: paste a failing build or runtime log. Returns ordered diagnosis, likely root cause, and concrete fix steps. Rebuy on every new failure. Dual-rail USDC (Base + Algorand).

## Output

Returns an ordered diagnosis of the error log, identifying the most likely root cause and providing concrete, actionable fix steps in priority order. Response is structured and may be returned as JSON if json_only is set.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "log": {
   "type": "string",
   "description": "Raw CI/build/runtime error log"
  },
  "skill": {
   "type": "string"
  },
  "context": {
   "type": "string"
  },
  "json_only": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentwork-ci-error-log-triage-121b5d29/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.agentwork.run](https://www.zero.xyz/host/api.agentwork.run/llms.txt)