# Halowerk Med Adverse Events Summarizer

> Halowerk Med Adverse Events Summarizer is a paid API for AI agents from med.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-14).

Summarizes FDA adverse event reports for a drug, including top reactions, serious outcome distribution, reporter type split, and temporal trend — with explicit causation limitations.

## Facts

- Endpoint: POST https://med.halowerk.com/v1/adverse-events
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/halowerk-med-adverse-events-summarizer-58a0b81f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Flxs_lbod2HNFgV2CJmLz

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-med-adverse-events-summarizer-58a0b81f -d '<json body>'
```

Example prompt: Can you pull the adverse event summary for semaglutide — I want to see the most common reported reactions, how serious the outcomes are, the health professional vs consumer reporter split, and how the trend has changed over time?

## When to prefer this

Use this endpoint when you need a synthesized, multi-dimensional safety overview of a specific drug from FDA adverse event data — combining reaction frequency, outcome severity, reporter demographics, and temporal trend in a single call. Prefer this over raw FAERS queries when you want pre-aggregated, agent-ready output with built-in causation disclaimers. It complements the drug label endpoint (which returns official prescribing information) and the boxed warning endpoint (which flags the most serious FDA-mandated warnings).

## Known failure modes

- Drug name not recognized or not found in FAERS — returns empty or error response
- Ambiguous drug name matching multiple RxNorm concepts — may require disambiguation
- Insufficient report volume for a drug yields statistically sparse trend data
- Newly approved drugs may have minimal historical adverse event data
- Network or upstream FAERS API unavailability causing timeout

## How this service works

Summarises adverse event reports for a drug: the most frequently reported reactions, the distribution of serious outcomes, the split between reports from health professionals and consumers, and the trend over time. Three limitations are returned with every response and are not footnotes. A report establishes that somebody suspected a connection, not that one exists — the system records suspicion, not causation.

## Output

Returns a structured summary including: the most frequently reported adverse reactions for the drug, a distribution of outcome severity (e.g. serious vs non-serious), the proportion of reports filed by healthcare professionals versus consumers, a temporal trend showing report volume over time, and exactly three stated limitations clarifying that reports represent suspicion of a connection, not confirmed causation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "drug": {
   "type": "string",
   "maxLength": 200,
   "minLength": 2
  },
  "months": {
   "type": "integer",
   "default": 36,
   "maximum": 120,
   "minimum": 3
  },
  "top_reactions": {
   "type": "integer",
   "default": 20,
   "maximum": 50,
   "minimum": 5
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/halowerk-med-adverse-events-summarizer-58a0b81f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from med.halowerk.com](https://www.zero.xyz/host/med.halowerk.com/llms.txt)