# Halowerk Intel Alerts Feed

> Halowerk Intel Alerts Feed is a paid API for AI agents from intel.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Retrieves up to 200 alerts for the authenticated payer's monitored watches, optionally filtered by a start timestamp

## Facts

- Endpoint: GET https://intel.halowerk.com/v1/intel/alerts
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-intel-alerts-feed-f1f1df74
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oEUKB8I31iXz0elbaeyJx

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 halowerk-intel-alerts-feed-f1f1df74
```

Example prompt: Pull the last 50 alerts from my Halowerk Intel feed since 2025-06-01T00:00:00Z and show me anything that fired on my watched addresses.

## When to prefer this

Use this endpoint when you need to poll or retrieve the alert history for your own set of monitored watches on Halowerk Intel. It is ideal for periodic polling, catch-up after downtime, or reviewing recent triggered events. Prefer this over the watch-check endpoint when you want a bulk read of past alert events rather than triggering a fresh check.

## Known failure modes

- Invalid or missing payment/payer address returns 402 or 401
- Malformed 'since' ISO timestamp returns 400 validation error
- Limit out of range (< 1 or > 200) returns 400
- No alerts available returns empty array
- Payer has no watches configured returns empty results

## How this service works

Liefert bis zu 200 Alarme seit einem optionalen ISO-Zeitpunkt. Die verifizierte Zahleradresse ist der Eigentümer; Ergebnisse und gespeicherte Daten sind strikt auf diesen Zahler begrenzt.

## Output

Returns a JSON array of up to 200 alert objects belonging exclusively to the authenticated payer, each representing a triggered watch event. Alerts may include watch identifiers, trigger timestamps, entity details, and alert metadata. Results are strictly scoped to the payer's own data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "limit": {
       "type": "integer",
       "default": 50,
       "maximum": 200,
       "minimum": 1
      },
      "since": {
       "type": "string",
       "maxLength": 40
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   },
   "additionalProperties": false
  }
 },
 "additionalProperties": false
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-intel-alerts-feed-f1f1df74/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from intel.halowerk.com](https://www.zero.xyz/host/intel.halowerk.com/llms.txt)
