health.mortality-stats

US mortality statistics from CDC NCHS. dataset=leading-causes (default): annual deaths + age-adjusted death rate per 100k by state and top-10 cause of death, 1999-2017 — filter by state (full name, e.g. "California", or "United States"), year, cause (e.g. "Heart disease", "Cancer", "Suicide"). dataset=weekly-counts: provisional weekly death counts by jurisdiction with per-cause columns (all-cause, natural, COVID-19, heart disease, cancer, etc.), 2020-2023 — filter by state and mmwrYear. Rows returned raw from CDC with documented column names. Public-domain federal data.

price
$0.0024 USDC per call
method
GET/api/health/mortality-stats
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The mortality stats API is a pay-per-call health endpoint built for AI agents and autonomous software. US mortality statistics from CDC NCHS.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in mortality stats data source for an agent tool-use loop, an MCP host, or a backend that needs health data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
datasetstring
one of: leading-causes | weekly-counts
statestring
min 2 chars · max 40 chars
yearinteger
min 1999 · max 2023
causestring
min 2 chars · max 80 chars
limitinteger
min 1 · max 200
offsetinteger
min 0

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/health/mortality-stats?dataset=leading-causes&state=xx&year=1999&cause=xx&limit=25&offset=0'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/health/mortality-stats?dataset=leading-causes&state=xx&year=1999&cause=xx&limit=25&offset=0' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/health/mortality-stats?dataset=leading-causes&state=xx&year=1999&cause=xx&limit=25&offset=0'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.health.mortalityStats({
  "dataset": "leading-causes",
  "state": "xx",
  "year": 1999,
  "cause": "xx",
  "limit": 25,
  "offset": 0
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.health.mortality_stats(dataset="leading-causes", state="xx", year=1999, cause="xx", limit=25, offset=0)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "health.mortality-stats",
    "arguments": {
      "dataset": "leading-causes",
      "state": "xx",
      "year": 1999,
      "cause": "xx",
      "limit": 25,
      "offset": 0
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
metaobject
Example response datajson
{
  "ok": true,
  "items": [
    {}
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "meta": {
    "dataset": "leading-causes"
  }
}

FAQ

Do I need an API key to use the mortality stats API?
No. health.mortality-stats is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the mortality stats API cost?
$0.0024 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the mortality stats API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call health.mortality-stats from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: mortality stats api · health mortality stats api · mortality stats api for ai agents · x402 health api · mortality stats api no api key · pay per call mortality stats api · health api