Inflation Grounding Data for AI Agents

Overview

The collector reads the World Bank inflation and consumer price indicators for every country once a day and stores one record per country per year. `inflationRate` is the annual percent change in consumer prices for `year`; `cpiIndex` is the index level for that year against `cpiBaseYear` (2010 = 100); `lastUpdated` is when the record was last refreshed.

When `year` is omitted the API starts from the previous calendar year and, if that year is not published yet, walks back up to ten years to the newest one that is. World Bank annual data commonly trails the calendar by more than a year, so expect the default to be two years back. An explicit `year` (paid plans) is never substituted: if it is missing you get a 404 that names the most recent year available.

`changes=true` reads the five preceding years. `previousInflationRate` and `inflationRateChange` (in percentage points, so 8.0 to 4.12 is -3.88) compare with the year before; `changeDirection` is up, down or unchanged. `averageInflationRate5y`, `highInflationRate5y` and `lowInflationRate5y` cover the reading year plus the four before it and are only filled when all five years exist, so a gap gives null instead of a shorter window. `cpiChange5y` is the percent rise in `cpiIndex` from five years earlier, rounded to two decimals. These fields are computed on every plan but returned only on paid plans.

Live Test Inflation Grounding Data for AI Agents Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as InflationGroundingDataforAIAgents. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

{
  "name": "InflationGroundingDataforAIAgents",
  "arguments": {
    "country": "US"
  }
}

You do not name the tool yourself; the model picks it. Asking about US in the terms this source covers is enough for it to reach for InflationGroundingDataforAIAgents on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

https://api.vervecontext.com/v1/mcp

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

{
  "status": "ok",
  "error": null,
  "data": {
    "country": "US",
    "countryName": "United States",
    "year": 2023,
    "inflationRate": 4.12,
    "cpiIndex": 139.74,
    "cpiBaseYear": 2010,
    "lastUpdated": "2026-11-06T04:00:00.000Z",
    "previousYear": 2022,
    "previousInflationRate": 8,
    "inflationRateChange": -3.88,
    "changeDirection": "down",
    "averageInflationRate5y": 3.97,
    "highInflationRate5y": 8,
    "lowInflationRate5y": 1.23,
    "cpiChange5y": 21.34
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at countryName: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Salary Adjustment Calculations

Compensation software calculates real wage growth across international offices by adjusting regional salaries against annual inflation figures.

Cross-Border Contract Indexing

When drafting multi-year vendor agreements, legal teams index payment schedules to annual consumer price changes for each supplier's country.

Portfolio Return Deflation

Wealth management dashboards subtract local consumer price index shifts from gross portfolio returns to present accurate purchasing power gains.

Purchasing Power Modeling

To forecast global product pricing, revenue teams evaluate relative purchasing power trends using annual price change rates and index values.

Other ways to use Inflation Grounding Data for AI Agents

Set up Inflation Grounding Data for AI Agents on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Related

More in Finance: