Data API

Monitor unemployment and labor-market data through one API

Meridian gives product teams and agent builders a normalized labor-market surface for unemployment, payrolls, claims, and related macro context.

Primary interface

GET /v1/snapshot plus MCP access for labor-market questions

Best first action

Ship labor-market context without manual series wrangling

Canonical URL

/data/unemployment-api

Example query

Ask a concrete question first

Each page is built around a real macro question so search visitors can immediately see how Meridian fits into an app or agent workflow.

Is the labor market cooling, stabilizing, or re-accelerating right now?
This page is static by design. The snippets below are illustrative and do not fetch live data during build.

API example

Call the underlying API

Use the same product surface behind the demo and MCP integration when you need direct HTTP access.

curl -H "Authorization: Bearer mrd_your_key_here" \
  "https://api.meridianapi.io/v1/snapshot?indicators=UNRATE,PAYEMS,ICSA,JTSJOL"

Response shape

Illustrative unemployment response shape

Labor-market consumers usually need both the latest level and enough context to tell whether conditions are tightening or easing.

{
  "snapshot_date": "2026-03-09",
  "indicators": [
    {
      "id": "UNRATE",
      "title": "Unemployment Rate",
      "latest": { "date": "2026-02-01", "value": 4.4, "units": "Percent" },
      "changes": { "mom": 0.1, "yoy": 4.76 },
      "context": { "direction": "rising", "z_score_10y": -0.1 }
    }
  ]
}

MCP snippet

Connect the same workflow over MCP

Use placeholder credentials only on public pages, then swap in your own API key after signup.

Ask your MCP client: "Summarize the labor market with unemployment, payrolls, and claims, then tell me what changed over the last quarter."

{
  "mcpServers": {
    "meridian": {
      "url": "https://api.meridianapi.io/sse",
      "headers": {
        "Authorization": "Bearer mrd_your_key_here"
      }
    }
  }
}

Why teams use this

What this page helps you ship

These are the most common implementation reasons teams land on this route from search and move into a product workflow.

Expose the labor market as structured data instead of stitching together several macro releases by hand.
Pair unemployment with payrolls, claims, and openings for better narrative context.
Share one labor-market data source across SEO pages, dashboards, and agent tooling.

FAQ

Questions search visitors usually ask next

Short answers keep these pages useful for humans while staying grounded in the product Meridian already exposes.

Is this limited to the headline unemployment rate?

No. Meridian's documented labor coverage also includes payrolls, jobless claims, openings, and wage-related indicators.

What is the simplest UI pattern for this data?

A compact card with the latest unemployment rate, direction, and one supporting metric such as claims or payroll growth is usually enough.

Can I compare labor conditions to another period?

Yes. Use the compare route or MCP tools when you want current labor conditions benchmarked against named regimes or prior dates.

Try the demo, then move to a key-backed workflow

Start with Ask Meridian on the homepage, then use your own API key for REST or MCP once you are ready to integrate.