Market / FDA device adverse events
External service · publisher supplied metadata

FDA device adverse events

Source and listing identity

Source: x402 Bazaar

Listing ID: x402:8398693e23fc47792b7f5b69db0f2e12eb26ac7a75f5c18d32c66e102ffc4cd2

Topic categories are inferred from listing text. Prices are source declarations; provider terms take precedence.

A registry entry or matching company name does not establish product authorship. Compare record IDs before treating similar titles as one product.

Summarize FDA medical device adverse event reports (openFDA MAUDE) for a device name, brand, product code or manufacturer: total matching reports, counts by event type (death, injury, malfunction), the most reported device problems, and the newest reports with date, event type, device, manufacturer, problems and a short excerpt of the event description. Counts cover every matching report; the report list is a capped sample and says so. Optional since date. Live FDA data, no key.

APIx402Indexed

Listing completeness · 80/100

Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.

Name and traceable source
10/10 · Present
Meaningful description
10/10 · Present
Connection or installation reference
20/20 · Present
Dedicated documentation or source repository
0/15 · Missing or insufficient
Explicit free access or numeric tariff
20/20 · Present
Declared integration protocol
10/10 · Present
Source updated within 90 days
10/10 · Present
Declared capability names
0/5 · Missing or insufficient

Evaluated 2026-11-03 · Method listing-completeness-1. Scoring rules

Connect & use

Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.

x402 resource

https://agent402.tools/api/device-adverse-events

Read the current payment requirements with a compatible client before authorizing a call.

Documentation ↗Open provider website ↗

Categories and declared capabilities

Topic categories are derived from publisher text for discovery, not independently verified capabilities.

The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.

Evidence, with its limits.

This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.

The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →