Use case
Ship fintech features on top of a macro API built for product teams
Meridian exposes snapshots, comparisons, and natural-language answers so fintech apps can add macro context to onboarding, portfolio views, commentary, and internal risk tools.
Primary interface
GET /v1/snapshot plus compare and query endpoints
Best first action
Add macro context to product surfaces
Canonical URL
/use-cases/fintech-macro-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.
Show the latest unemployment, CPI, Fed funds, and yield-curve context for a market dashboard card.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,CPIAUCSL,FEDFUNDS,T10Y2Y"Response shape
Illustrative snapshot shape
The snapshot endpoint returns normalized indicator records that are easier to render in product UIs than scraping raw source files.
{
"snapshot_date": "2026-03-09",
"regime": {
"label": "expansion",
"confidence": 0.7
},
"indicators": [
{
"id": "UNRATE",
"title": "Unemployment Rate",
"latest": { "date": "2026-02-01", "value": 4.4, "units": "Percent" },
"changes": { "yoy": 4.76 },
"context": { "direction": "rising", "percentile_10y": 66.4 }
}
]
}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: "Prepare a product-safe macro summary for today with the four indicators most relevant to consumer credit."
{
"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.
FAQ
Questions search visitors usually ask next
Short answers keep these pages useful for humans while staying grounded in the product Meridian already exposes.
Which routes are best for a fintech app?
Most product surfaces start with /v1/snapshot for headline metrics, then add /v1/compare or /v1/query when you need narrative context.
Can I keep this server-side only?
Yes. Authenticated REST calls work well in backend or edge handlers, while public query routes can support demo or marketing surfaces.
Do I need a separate MCP integration for internal tools?
Only if your team wants the same data exposed directly inside an AI client. The REST API is enough for standard application code.
Internal links
Keep exploring Meridian
Every page links into docs, signup, pricing, and related live pages so visitors can move from discovery to implementation.
Read the docs
See the full REST, MCP, and coverage reference.
View pricing
Check the free tier and paid usage limits.
Get a free API key
Create a project and start calling Meridian.
Inflation API
Query CPI, core CPI, PCE, and related macro context through Meridian's inflation API for dashboards, agents, and fintech workflows.
Unemployment API
Use Meridian's unemployment API to track the headline jobless rate, payrolls, claims, and labor-market context across apps, dashboards, and AI agents.
Macro data server
Connect Meridian as a remote MCP server so Claude, Cursor, and other MCP clients can call macro snapshot, compare, and explanation tools with your API key.
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.