# Supplement Adverse Events Lookup

> Supplement Adverse Events Lookup is a paid API for AI agents from x402-agent-api-production.up.railway.app, paid per call via x402, $0.006/call, status unknown (last checked 2026-11-13).

Returns FDA adverse event report data for a dietary supplement ingredient, including top reactions, total reports, yearly breakdown, and serious outcome counts.

## Facts

- Endpoint: GET https://x402-agent-api-production.up.railway.app/supplements/adverse-events/%7Bingredient%7D?utm_source=zero.xyz
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/supplement-adverse-events-lookup-94065961
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sAeI5w9qx60xAPhdT3pWz

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 supplement-adverse-events-lookup-94065961
```

Example prompt: Can you pull the FDA adverse event data for ashwagandha? I want to know the top reported reactions, how many total reports there are, and whether there are any serious outcomes on record.

## When to prefer this

Use this endpoint when you need structured FDA adverse event data specifically for dietary supplement ingredients and want granular output including per-reaction counts, yearly trends, and serious outcome tallies — all in a single call. Prefer this over general web searches when you need authoritative, quantitative safety data sourced from FAERS. It is especially well suited for health-focused AI agents, supplement recommendation tools, or safety research workflows that need programmatic access to adverse event statistics for specific ingredients.

## Known failure modes

- Ingredient not found in FAERS data — may return empty results or zero counts for obscure or misspelled ingredient names
- Misspelled or non-standard ingredient name causes no match — agents should normalize ingredient names before querying
- API unavailable or Railway hosting downtime returns a 5xx error
- Payment failure (insufficient USDC balance or x402 protocol misconfiguration) blocks the request
- Rate limiting if too many calls are made in quick succession

## How this service works

SEC and supplement safety data, pay per call in USDC via x402.

## Output

A JSON object containing the queried ingredient name, a list of top adverse reactions with report counts (e.g. nausea: 14 reports), total number of adverse event reports, a year-by-year breakdown of report counts, and total count of reports mentioning a serious outcome.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ingredient": "ashwagandha",
  "top_reactions": [
   {
    "reports": 14,
    "reaction": "NAUSEA"
   }
  ],
  "total_reports": 120,
  "reports_by_year": {
   "2024": 30,
   "2025": 41
  },
  "serious_outcome_mentions": 31
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/supplement-adverse-events-lookup-94065961/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent-api-production.up.railway.app](https://www.zero.xyz/host/x402-agent-api-production.up.railway.app/llms.txt)
