Diagnose a CI failure and generate a repair plan
Turn one failing build, test, compiler, dependency, lint, or container log into an ordered diagnosis with likely root cause, redacted evidence, a focused rerun command, concrete repair steps, and a stable failure fingerprint.
$0.02 USDC POST /v1/diagnose-and-fix
developer-tools · ci-cd · logs
Use it for
- analyze build log root cause
- fix CI failure
- generate CI repair plan
- diagnose test failure
Example input
{
"log": "FAILED tests/test_math.py::test_total - AssertionError: assert 1 == 2",
"step_name": "pytest"
}Example output
{
"success": true,
"diagnosis": {
"failure_type": "pytest",
"error_message": "AssertionError: assert 1 == 2",
"stack_trace": [
"tests/test_math.py:8: AssertionError"
],
"suggested_fix_category": "test_failure",
"confidence": 0.96
},
"likely_root_cause": "A test assertion did not match the observed value.",
"rerun_command": "pytest -q tests/test_math.py::test_total",
"repair_steps": [
"Reproduce the single failing test.",
"Compare expected and actual values."
],
"fingerprint": "ci1:0123456789abcdef01234567"
}Call it
Use an x402 v2 payment-aware client from the quickstart. An unpaid request safely returns the exact payment challenge before any work runs.