Discover / safetyincidents.org

Safety Incidents — OSHA Severe-Injury API

□ No challenge detected

Federal OSHA severe-injury records, single incident lookups, and employer aggregate safety totals. Cleaned and entity-resolved. Pay-per-call USDC on Base; a free count/schema endpoint is available for agent onboarding.

x402
Base
USDC
Data

Challenge detected: 0 of the last check
Last checked: 15 Oct, 00:26 UTC
In our index since: 14 Oct 2026

Endpoint

curl -i https://safetyincidents.org
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/safetyincidents.org

Recent checks

15 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.15 Oct 2026

All 1 checks

When (UTC)	Result	HTTP	Response
15 Oct, 00:26 UTC	No challenge detected	200	600ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 15 Oct, 00:26 UTC, we detected no payment challenge.

What payment terms does Safety Incidents — OSHA Severe-Injury API advertise?

The listing advertises x402, Base and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is Safety Incidents — OSHA Severe-Injury API listed?

In x402-list.com. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.