Use case

Give your AI agent live macro data instead of stale context

Meridian gives agents a deterministic macro-data layer for questions about inflation, labor markets, rates, and historical regimes, without hard-coding static spreadsheets into prompts.

Primary interface

ask_meridian over MCP or POST /v1/query

Best first action

Ground macro answers in live data

Canonical URL

/use-cases/ai-agent-macro-data

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 changed most in inflation, unemployment, and rates over the last 3 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 -X POST https://api.meridianapi.io/v1/query \
  -H "Content-Type: application/json" \
  -d '{"question":"What changed most in inflation, unemployment, and rates over the last 3 months?"}'

Response shape

Typical output for agent workflows

This route is designed for grounded agent answers, so the most useful response is a structured explanation rather than a raw table.

A plain-English summary the agent can quote back to the user.
Named indicators such as CPI, unemployment, or Fed funds that explain the answer.
Context about direction, recency, or historical comparison for follow-up reasoning.

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 inflation, labor, and rates in one paragraph and cite the indicators that matter most."

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

Replace fragile macro prompt engineering with a live, typed tool boundary.
Let agents compare current conditions to named regimes like 2008_crisis or 2020_covid.
Use the public Ask Meridian demo first, then move the same workflow into production.

FAQ

Questions search visitors usually ask next

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

Do I need MCP to use Meridian with an agent?

No. MCP is the cleanest option for tool-aware clients, but you can also call the REST API from your own orchestration layer.

Does this page fetch live data during build?

No. The page is fully static and uses illustrative snippets only, so it stays fast and crawlable.

What should the agent ask first?

A broad macro status question works well first, followed by a narrower query on inflation, unemployment, or yield-curve changes.

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.