Normalize network logs API

Normalize caller-supplied network/syslog rows. Private addresses in caller data are retained but never contacted.

The Normalize network logs operation is part of the Telecom & Network Infrastructure Intelligence API on BRAINIAC.software. Normalize caller-supplied network/syslog rows. Private addresses in caller data are retained but never contacted. It is exposed as POST /api/v1/network-intelligence/log-normalize and priced at $0.03 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied logs, latency/packet-loss samples, DNS/BGP/cert/config/reputation/incident records Public DNS when publicDns is requested Public TLS port 443 when publicTls is requested Limitations: Private, loopback, link-local, and documentation addresses are never contacted. Private networks are not scanned. No intrusive security testing is performed and no paid reputation API is used. IP reputation uses only caller-supplied labels/observations. Missing reputation data is not invented. Optional public DNS and TLS inspection are limited to public hostnames on standard resolvers / port 443. Infrastructure health reports aggregate only sections for which records were supplied or optionally fetched. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Detect network latency anomalies, Analyze packet-loss patterns, Diagnose DNS resolution, Analyze BGP route changes. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.03 USDC
/api/v1/network-intelligence/log-normalize

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/network-intelligence/log-normalize" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "asOf": "2026-11-04T21:00:00.000Z",
  "logs": [
    {
      "id": "L1",
      "at": "2026-11-04T20:00:00.000Z",
      "host": "edge-1",
      "facility": "local0",
      "severity": "info",
      "message": "link up",
      "sourceIp": "203.0.113.10",
      "destinationIp": "198.51.100.20",
      "source": "Caller-supplied syslog"
    },
    {
      "id": "L2",
      "at": "2026-11-04T20:05:00.000Z",
      "host": "edge-1",
      "facility": "local0",
      "severity": "error",
      "message": "BGP session timeout",
      "source": "Caller-supplied syslog"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Telecom & Network Infrastructure Intelligence APIFull docsHow it works