# Security Alert Email Triage

> Security Alert Email Triage is a paid API for AI agents from x402-hono-api.inraby.workers.dev, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-16).

Triages security alert emails by assessing urgency, severity, likely cause, and evidence collection steps without storing message bodies.

## Facts

- Endpoint: POST https://x402-hono-api.inraby.workers.dev/api/v1/security-alert-triage
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/security-alert-email-triage-0d90e60d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oBL5omERKVfqcM49EzB5h

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 security-alert-email-triage-0d90e60d -d '<json body>'
```

Example prompt: I just got this security alert email from AWS with subject 'Unusual API activity detected in us-east-1' — can you triage it for urgency and severity, figure out the likely cause, and tell me what evidence I should collect? Here's the body: 'We detected unusual API calls from IP 198.51.100.42 at 03:14 UTC involving iam:ListUsers and s3:ListBuckets across multiple accounts.'

## When to prefer this

Choose this endpoint when you need rapid, structured triage of security alert emails from major cloud providers (AWS, Cloudflare, GitHub, Google, Microsoft) and want urgency/severity classification plus actionable evidence steps without any risk of server-side message retention. Prefer over generic LLM prompting when you need consistent structured output and auditability of triage decisions.

## Known failure modes

- Missing required fields (body or subject) returns a 400 validation error
- Unsupported source enum value returns a 400 error
- Ambiguous or extremely short email bodies may produce low-confidence triage with generic recommendations
- Payment not attached or insufficient USDC balance returns a 402 Payment Required
- Server-side LLM timeout or overload returns a 500 error

## How this service works

Triage security alert emails for urgency, severity, likely cause, and evidence collection steps without storing message bodies.

## Output

Returns a structured triage report including urgency level, severity classification, most likely root cause or attack vector, and a prioritized list of evidence collection steps the analyst should take — without storing any of the submitted email content server-side.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Email body text (not stored server-side)"
  },
  "from": {
   "type": "string",
   "description": "Sender address or display name"
  },
  "source": {
   "enum": [
    "cloudflare",
    "aws",
    "github",
    "google",
    "microsoft",
    "other"
   ],
   "type": "string"
  },
  "subject": {
   "type": "string",
   "description": "Email subject line"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/security-alert-email-triage-0d90e60d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-hono-api.inraby.workers.dev](https://www.zero.xyz/host/x402-hono-api.inraby.workers.dev/llms.txt)