# Strale Log Parse API

> Strale Log Parse API is a paid API for AI agents from api.strale.io, paid per call via x402, $0.054/call, status unknown (last checked 2026-09-13).

Parses and structures raw log data submitted as a query parameter, returning structured output with an audit record.

## Facts

- Endpoint: GET https://api.strale.io/x402/v2/log-parse
- Price: $0.054/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/strale-log-parse-api-ca139fc4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M6g8cynphULTfad5wvndZ

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 strale-log-parse-api-ca139fc4
```

Example prompt: Can you parse these raw server logs for me and extract the structured fields? Here are the logs: '2024-01-15T10:23:45Z ERROR [auth] Failed login attempt from 192.168.1.1 user=admin'

## When to prefer this

Choose this endpoint when you need both log parsing and a cryptographic audit trail proving the parsing occurred — particularly useful in compliance, security, or regulated environments where you need verifiable records of data processing. Prefer this over generic log parsers when operating in an AI agent context that requires trust infrastructure or when audit chain hashing is a requirement.

## Known failure modes

- Missing required 'logs' query parameter returns validation error
- Malformed or unparseable log format may return empty or partial extraction
- Invalid HTTP method (only GET, HEAD, DELETE supported) returns 405
- Network timeout if log string is extremely large
- Payment failure or insufficient USDC balance blocks the request

## How this service works

The trust layer for AI agents — 250+ independently tested data capabilities across 27 countries. Execute capabilities via REST, MCP, A2A, or x402 micropayments. Every call returns an audit record with cryptographic chain hashing.

## Output

Returns structured, parsed log data extracted from the raw log string input, along with a cryptographic audit record containing chain hashing that verifies the integrity and provenance of the parsing operation.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ]
    },
    "queryParams": {
     "type": "object",
     "required": [
      "logs"
     ],
     "properties": {
      "logs": {
       "type": "string"
      }
     }
    }
   },
   "required": [
    "type",
    "method"
   ],
   "additionalProperties": false
  }
 },
 "required": [
  "input"
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/strale-log-parse-api-ca139fc4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.strale.io](https://www.zero.xyz/host/api.strale.io/llms.txt)