# Crypto Shark Fleet – Log Triage Worker

> Crypto Shark Fleet – Log Triage Worker is a paid API for AI agents from cryptoshark-fleet.duckdns.org, paid per call via x402, $0.06/call, status unknown (last checked 2026-10-11).

AI-powered log triage: analyzes raw log text and returns a structured diagnosis or summary using a GPT model, paid per-call via x402 on Base mainnet

## Facts

- Endpoint: POST https://cryptoshark-fleet.duckdns.org/worker/log-triage?utm_source=zero.xyz
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/crypto-shark-fleet-log-triage-worker-bef02e66
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Y-bh4N1op5qKRfEPM8UbX

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 crypto-shark-fleet-log-triage-worker-bef02e66 -d '<json body>'
```

Example prompt: Can you triage these server logs and tell me what's going wrong? Here's the output: [ERROR] 2024-06-01 03:12:44 Connection timeout on db-primary after 30s retries=5, [WARN] disk usage 94% on /var/log, [FATAL] OOMKilled pid 8821.

## When to prefer this

Choose this endpoint when you need a quick, cheap ($0.06/call), AI-powered triage of raw log text without setting up your own LLM pipeline. It's especially suitable for agents that handle incident response, CI/CD failure diagnosis, or periodic log health checks and need a pay-per-use model with no subscription. Not ideal for very large log files (>16KB) or highly sensitive logs you can't send to a third-party service.

## Known failure modes

- Payment not included or invalid x402 payment header → 402 Payment Required
- Input log text exceeds 16,000 character limit → validation error or truncation
- Malformed JSON body or missing 'input' field → 400 Bad Request
- Upstream LLM unavailable → 500 or timeout
- DuckDNS dynamic hostname unreachable → DNS resolution failure or connection timeout

## How this service works

x402-paid AI utility workers on Base mainnet

## Output

A JSON object with a 'model' field (e.g. 'gpt-5.6-luna') and a 'result' field containing the AI-generated triage output — typically a structured summary of errors, warnings, root causes, and recommended actions extracted from the submitted log text.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 16000
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "model": "gpt-5.6-luna",
  "result": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/crypto-shark-fleet-log-triage-worker-bef02e66/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cryptoshark-fleet.duckdns.org](https://www.zero.xyz/host/cryptoshark-fleet.duckdns.org/llms.txt)