# CI Error Fingerprinter

> CI Error Fingerprinter is a paid API for AI agents from temporary-instant-tempest-4a1g1wu.vercel.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Generates a stable, normalized fingerprint from a CI/build/test failure log so that duplicate errors can be grouped across changing line numbers, timestamps, paths, and retry attempts.

## Facts

- Endpoint: POST https://temporary-instant-tempest-4a1g1wu.vercel.app/v1/fingerprint
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ci-error-fingerprinter-54b07a94
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-Qr7lzqH0pR4qTUEWeyUI

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 ci-error-fingerprinter-54b07a94 -d '<json body>'
```

Example prompt: I've got this raw CI log from a failed GitHub Actions step called 'Run tests' — can you generate a stable fingerprint for it so I can group it with other duplicate failures even if line numbers or timestamps change?

## When to prefer this

Use this endpoint when you need to deduplicate or cluster CI, build, or test failures across multiple runs where surface-level text differs (timestamps, line numbers, retry counts, temp paths). Prefer this over generic hashing when you need semantic normalization of error logs — raw hashing would treat every retry as a unique error. Ideal for alert deduplication pipelines, CI dashboards, and automated triage workflows.

## Known failure modes

- Log text too short or empty — validation error returned
- Log exceeds 1,000,000 character limit — payload too large error
- Step name too long (over 300 chars) — validation error
- Non-CI/log content submitted — fingerprint may be generated but semantically meaningless
- Network timeout if log is very large and processing takes too long
- Payment failure (x402 protocol) — 402 response if USDC payment not provided

## How this service works

Generate a stable, secret-free fingerprint from a build or test failure so agents can group duplicate CI errors across changing line numbers, timestamps, paths, identifiers, and retry attempts.

## Output

A stable, secret-free fingerprint string derived from the normalized error content of the log, stripping out volatile elements like timestamps, line numbers, paths, and identifiers so that semantically identical errors produce the same fingerprint across different runs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "log": {
   "type": "string",
   "maxLength": 1000000,
   "minLength": 1,
   "description": "Raw CI, build, test, compiler, or runtime log text."
  },
  "step_name": {
   "type": "string",
   "maxLength": 300,
   "description": "Optional CI step or job name that produced the log."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ci-error-fingerprinter-54b07a94/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from temporary-instant-tempest-4a1g1wu.vercel.app](https://www.zero.xyz/host/temporary-instant-tempest-4a1g1wu.vercel.app/llms.txt)