Log Parser

Parse log files in JSON, syslog, ISO, logfmt or Laravel format into timestamps, levels and messages, with a summary of errors and warnings.

Pay by wallet (x402) log-parse

Example

Input
{
  "logs": "test_value"
}
Answer
{
  "errors": [],
  "warnings": [],
  "time_range": {
    "last": null,
    "first": null
  },
  "error_count": 0,
  "total_lines": 1,
  "level_counts": {},
  "parsed_sample": [
    {
      "raw": "test_value",
      "format": "unknown",
      "message": "test_value",
      "line_number": 1
    }
  ],
  "warning_count": 0,
  "detected_format": "unknown"
}

Inputs

FieldTypeRequiredWhat it is
logsstringYes—

Output fields

How reliably each field appears in a successful answer.

FieldTypeAppears
errorsarrayAlways (present in every successful answer)
error_countintegerAlways (present in every successful answer)
total_linesintegerAlways (present in every successful answer)
level_countsobjectAlways (present in every successful answer)
detected_formatstringAlways (present in every successful answer)

How to call it

The same tool through each route. MCP clients reach it through Strale’s server at https://api.strale.io/mcp; the call below is what the agent sends.

# Needs an API key. max_price_cents caps what this call may cost.
curl -X POST https://api.strale.io/v1/do \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "capability_slug": "log-parse",
    "inputs": {
      "logs": "test_value"
    },
    "max_price_cents": 5
  }'

Limitations

  • Custom log formats can require explicit hints

    AI-powered log parsing — custom or proprietary log formats may require specific format hints for accurate parsing

    What to do instead: Include a sample log line description or format string in the input for non-standard log formats