# Medical Device Incident Trend Aggregator

> Medical Device Incident Trend Aggregator 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-15).

Aggregates FDA medical device adverse event reports by product code, device name, or manufacturer into annual trend statistics including outcome splits, top problem codes, and manufacturer evaluation rates.

## Facts

- Endpoint: POST https://med.halowerk.com/v1/device-incident-trend
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/medical-device-incident-trend-aggregator-45c05680
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cE62QD0yAVBZpzgmyE6yv

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 medical-device-incident-trend-aggregator-45c05680 -d '<json body>'
```

Example prompt: Can you pull the incident trend for insulin pumps — I want to see how many reports per year there have been, the breakdown between malfunctions, injuries, and deaths, and what the most common problem codes are?

## When to prefer this

Choose this endpoint when you need multi-year trend analysis of FDA medical device adverse events — not just a list of raw reports. It is purpose-built to surface year-over-year volume, outcome splits, and problem frequency in a single call, saving you from aggregating raw MAUDE records yourself. Prefer it over raw FDA API queries when you need a pre-computed, agent-ready summary with built-in caveats about statistical interpretation.

## Known failure modes

- Unknown or misspelled product code / device name returns empty results or an error
- Manufacturer name variation causes missed records if not matched exactly
- Very niche devices may return too few records to produce a meaningful trend
- Network or upstream FDA API timeout returns a service error
- Missing required input field returns a validation error

## How this service works

Aggregates medical device reports for a product code, device name or manufacturer into a trend: reports per year, the split between malfunction, injury and death outcomes, the most frequent problem codes, and the share of reports where the manufacturer conducted an evaluation. Two things the figures are not, and both are stated in the response rather than left to be inferred.

## Output

Returns a structured trend object containing: annual report counts, outcome breakdown (malfunction / injury / death percentages or counts), the most frequently occurring problem codes with labels, the share of reports where the manufacturer performed an evaluation, and explicit caveats about what the figures do and do not represent.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "years": {
   "type": "integer",
   "default": 5,
   "maximum": 15,
   "minimum": 1
  },
  "device": {
   "type": "string",
   "maxLength": 200,
   "description": "Device generic name."
  },
  "manufacturer": {
   "type": "string",
   "maxLength": 200
  },
  "product_code": {
   "type": "string",
   "maxLength": 10,
   "description": "FDA three-letter product code, the most precise selector."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/medical-device-incident-trend-aggregator-45c05680/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)