# Hermes Macro Research: Install the Accepted FXMacroData Plugin

Canonical: https://fxmacrodata.com/articles/fxmacrodata-hermes-integration
Author: Rob Tidball
Published: 2026-10-08T11:52:15Z

Use the official Hermes catalogue plugin to discover FXMacroData tools, build a sourced USD brief and assess pagination, access notices and publication quality.

**The accepted FXMacroData community plugin adds native REST and hosted MCP research tools to Hermes Agent. Version 0.2.0 requires Hermes 0.21 or newer and includes 72 API tools plus one[USD](/united-states) macro brief. Install, enable and restart Hermes, then ask it to discover indicators and return a sourced, explicitly bounded research result.**

**Who this guide is for:**Analysts using Hermes Agent who want native macro tools and clear evidence in a conversation.

**Outcome:**A sourced macro brief inside the same conversation where you form the research question.

A conversational research assistant becomes more useful when an analyst can inspect the evidence behind the answer. The plugin lets Hermes retrieve a catalogue, a history window or a release schedule through named tools and keep the response's sources and access notices attached. The practical gain is a shorter path from a question to a reviewable evidence packet, without asking the model to remember changing observations from training data.

Use[USD policy-rate evidence](/united-states/policy-rate#api-docs) and the[release calendar](/dashboard/release-calendar) to orient the first session. The goal is to preserve the data's meaning as it moves into the research workflow.

## 1. Connect the accepted integration

The official Hermes catalogue pins adapter version 0.2.0 to a specific source commit and declares the minimum host version. The repository README documents the commands below. Restart Hermes after enabling the plugin so the tool registration is available in the conversation. Model-provider configuration belongs to Hermes itself and is separate from optional FXMacroData data access.

Use the[official listing](https://github.com/NousResearch/hermes-agent/blob/main/plugin-catalog/fxmacrodata.yaml) for discovery and the[FXMacroData integration README](https://github.com/fxmacrodata/hermes-fxmacrodata#readme) for its version-specific instructions.

```
hermes plugins install fxmacrodata/hermes-fxmacrodata
hermes plugins enable fxmacrodata
```

**Research workflow**

- **Install and enable the catalogue plugin**

Enable the accepted plugin on a supported Hermes version and restart the agent.

- **Discover the native MCP tools**

Begin with the hosted MCP catalogue so the model selects actual data tools.

- **Request a bounded research packet**

Request one defined indicator, date scope and calendar window.

- **Check sources, scope and timing**

Keep citations and access notices attached when turning tool results into an answer.

*The tool call supplies evidence; Hermes carries it into a cited answer that the analyst reviews.*

## 2. Run the native research workflow

Begin the AI-facing workflow with the hosted MCP tools exposed by the plugin: catalogue discovery, indicator queries and release-calendar retrieval. Ask Hermes to state which tool it used and to preserve the original publisher`source_url`when present. The plugin also exposes direct REST tools and a convenience`/fxmacrodata`command. That command builds a USD catalogue/history/calendar brief; it is a quick orientation workflow rather than a complete archive request.

```
/fxmacrodata policy_rate
```

**Choose the right result surface**

Native surface Useful research output Scope to check 72 API tools 23 REST operations and 49 hosted MCP tools Inventory is packaged with version 0.2.0 USD macro brief Catalogue, up to ten history rows, next seven UTC calendar days`complete`means sections succeeded MCP resources and artifacts Text, structured content and resource links Interactive MCP Apps are not rendered by this plugin

*The integration surface determines what is immediately visible; the provider response determines access and data semantics.*

## 3. Interpret the result before using it

The response carries original data, an additive`records`view and citations. Keyless responses can include notices identifying the recent history window or access delay. A successful section does not imply a full series, and an empty record set is unavailable evidence rather than a numeric zero. For longer history, inspect pagination and request the next offset/page through the tool's declared schema instead of relying on the first answer.

**Four meanings that should survive extraction**

Time meaning Interpretation**Reference period**The period described by an observation.**Observed publication**A publisher instant only when the response's quality fields establish it.**Official schedule**A future time or date-only announcement, retained with its status.**Client receipt**When a client received the response, separate from all three above.

*Keep these meanings distinct when interpreting a returned record.*

## 4. Review scope, access and quality

The brief is fixed to USD, up to ten history rows and a seven-day calendar window anchored to the current UTC date. Failed sections remain explicit. For a historical information-cutoff question, inspect`publication_time_status`,`capture_time_basis`and assumed-time flags, and distinguish revised values from the values demonstrably known then. Schedules and capture clocks do not prove an observed publisher instant. Keep market consensus, official projections and generated predictions separate in the answer.

Public USD catalogue, recent indicator history and the release calendar can be evaluated without a key. Protected datasets require the appropriate access. This plugin reads only`FXMACRODATA_API_KEY`from the process environment or a configured Hermes secret source; it does not read`FXMD_API_KEY`. REST authentication uses`X-API-Key`, hosted MCP uses a`Bearer`header, and credentials do not belong in prompts or tool arguments.

**A repeatable review checklist**

- **Name the tool and requested window**

Compare the tool names with the installed plugin inventory before relying on an instruction.

- **Repeat access notices in the answer**

A data notice belongs in the answer whenever delay or scope affects the interpretation.

- **Cite original publisher links when present**

Retain the publisher URL with the value so a reader can trace the underlying series.

- **Keep section success separate from completeness**

The brief's`complete`flag applies to section success; ten recent history rows are not an archive.

*A research packet is useful when another reader can reconstruct its scope and evidence.*

Keep the original response or a reproducible local snapshot alongside the analysis. Measure row coverage, the treatment of missing values and the ability to reproduce the same window. If those checks fail, diagnose the extraction or interpretation before attributing a difference to the market.

## Troubleshooting a first session

If tools are absent, confirm the host version, enable the plugin and restart. Discover a currency's indicator slug before requesting it. Check optional access when a protected tool reports a subscribe/access message. Inspect each failed brief section independently, and respect rate-limit errors before retrying. The pinned local adapter does not pin the remotely served behaviour of hosted MCP tools.

## Sources and next steps

Version and acceptance evidence:[official integration listing](https://github.com/NousResearch/hermes-agent/blob/main/plugin-catalog/fxmacrodata.yaml) and[public adapter source](https://github.com/fxmacrodata/hermes-fxmacrodata) . Data behaviour and optional access:[FXMacroData API reference](/documentation/reference) ,[hosted MCP guide](/mcp) and[subscription access](/subscribe) .

For the wider agent workflow, continue with the[AI trading guide collection](/ai-trading) and the separate[Hermes research-journal guide](/articles/hermes-agent-fx-research-journal) .

AI was used for research, creating images and editing.

Source: FXMacroData
