Overview
Inflation Rate works by aggregating consumer price index data from the World Bank for over 180 countries. It provides both the annual inflation rate (year-over-year percentage change in consumer prices) and the CPI index value (base year 2010 = 100). Data is refreshed daily.
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/mcpPer-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.
| Argument | Type | Description |
|---|---|---|
countryRequired | string | ISO 2-letter country code (e.g., US, GB, JP, DE, BR) length 2–2 |
yearOptionalPremium | integer | The year to retrieve data for. Defaults to the previous year. range 1960–2030 |
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.
{
"status": "ok",
"error": null,
"data": {
"country": "US",
"countryName": "United States",
"year": 2023,
"inflationRate": 4.12,
"cpiIndex": 139.81,
"cpiBaseYear": 2010,
"lastUpdated": "2026-02-05T04:00:00.000Z"
}
}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.
| Field | Type | Example | Description |
|---|---|---|---|
country | string | US | ISO 2-letter country code of the requested country |
countryName | string | United States | Full name of the country in English |
year | number | 2023 | Year for which inflation data was retrieved |
inflationRate | number | 4.12 | Annual inflation rate as percentage year-over-year change |
cpiIndex | number | 139.81 | Consumer Price Index value for the year |
cpiBaseYear | number | 2010 | Base year used for CPI calculation and comparison |
lastUpdated | string | 2026-02-05T04:00:00.000Z | ISO 8601 timestamp of last data update |
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.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 1 credit each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Economic Analysis
- Use the Inflation Rate API to analyze inflation trends across countries and time periods for economic research and reporting
- Financial Planning
- Incorporate inflation data into financial planning tools to adjust projections and account for purchasing power changes
- Currency Analysis
- Compare inflation rates across countries to understand currency strength and purchasing power parity
- Data Visualization
- Build dashboards and charts showing historical inflation trends by country using the Inflation Rate API
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: