Data API

Track inflation data with one API for CPI, core, and PCE context

Meridian packages headline inflation indicators into a consistent response format so your app or agent can explain what changed without hand-joining multiple macro sources.

Primary interface

GET /v1/snapshot and POST /v1/query for inflation workflows

Best first action

Use a dedicated inflation data surface

Canonical URL

/data/inflation-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.

What happened to CPI and core inflation over the last 6 months?
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=CPIAUCSL,CPILFESL,PCEPI,PCEPILFE"

Response shape

Illustrative inflation response shape

The inflation API can return multiple related series in one normalized snapshot so you do not have to reconcile field names across upstream sources.

{
  "snapshot_date": "2026-03-09",
  "indicators": [
    {
      "id": "CPIAUCSL",
      "title": "Consumer Price Index for All Urban Consumers",
      "latest": { "date": "2026-02-01", "value": 319.1, "units": "Index 1982-1984=100" },
      "changes": { "mom": 0.3, "yoy": 2.7 },
      "context": { "direction": "rising", "percentile_10y": 54.2 }
    }
  ]
}

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: "Explain whether inflation is cooling or re-accelerating and cite CPI, core CPI, and PCE."

{
  "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.

Bundle headline and core inflation measures into one consistent integration point.
Use the same route for user-facing dashboards and internal analyst tooling.
Route inflation questions from the public demo to an authenticated API flow when you need repeatable product logic.

FAQ

Questions search visitors usually ask next

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

Does Meridian only cover headline CPI?

No. The documented coverage includes CPI, core CPI, PCE, and core PCE so you can compare broad and underlying inflation measures.

Should I use query or snapshot for inflation pages?

Use snapshot when you need structured fields for UI rendering. Use query when you want Meridian to write the summary in plain English.

Can agents use this page too?

Yes. The same inflation indicators are available over MCP, so an agent can explain the move and cite the series behind it.

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.