Monitor Federal Reserve and Bank of Canada policy announcements and rates

The problem

The Federal Reserve announces monetary policy through press releases: Federal Open Market Committee statements after each meeting, FOMC minutes three weeks later, the Summary of Economic Projections and minutes of the Board's discount rate meetings. The Bank of Canada sets the target for the overnight rate, its policy interest rate, on eight fixed announcement dates a year, and publishes it with the Bank Rate as business-daily series.

This guide pairs two monitors: the Federal Reserve Board's monetary policy RSS feed, read hourly as one record per release, and the Bank of Canada's Valet series for both rates, read daily as one record per business day.

What the source contains

Federal Reserve monetary policy press releases · Board of Governors of the Federal Reserve System

Monetary policy press releases from the Federal Reserve Board's RSS feed: FOMC statements, FOMC minutes, economic projections, discount rate meeting minutes and related announcements, one record per release.

5 typed fields · 15 records in SourceFinch's latest run on October 12, 2026 · publisher updates: around each FOMC meeting and with other announcements; monitor hourly · full source page

What a change means

• Federal Reserve: a new url is a new release. title is the headline, category the feed category and published the publication time as the feed gives it. On decision days the FOMC statement is published at 2:00 p.m. Eastern, and an hourly monitor reports it within the hour.
• Bank of Canada: a new date is another business day. Because each day is its own record, a rate decision shows as a new record whose policy_rate differs from the day before, not as a change to an existing record. bank_rate normally sits 25 basis points above the target.

Set it up in the console

1. Open the Verified recipe. Open the Federal Reserve monetary policy press releases recipe in the console. It keeps the reviewed URL, fields and record key (url), and shows the latest captured sample. Open in the console
2. Create the monitor. Name the monitor, keep the hourly schedule or pick another (the console shows the monthly run cost), confirm that you have the right to monitor the source, and choose Create monitor.
3. Run the baseline. The first run is the baseline: every record is new. From the second run on, the monitor reports what was added, changed or removed, field by field, with the evidence behind each value.
4. Choose how you hear about changes. In Alerts, choose immediate change emails or a daily or weekly digest; each monitor can override that on its own page. For your own systems, add a signed webhook in Destinations. Alerts and team
5. Add the Bank of Canada monitor. Open the Bank of Canada recipe the same way. It runs daily; the Federal Reserve monitor keeps its hourly schedule.

The other recipe: Bank of Canada policy interest rate and Bank Rate, daily.

The same through the REST API, CLI or MCP

Every surface creates the same monitor from the same Verified recipe. You confirm you have the right to collect the source (rights: true).

Federal Reserve monetary policy press releases

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/federal-reserve-monetary-policy-press-releases -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

sourcefinch login
sourcefinch catalog get federal-reserve-monetary-policy-press-releases --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Federal Reserve monetary policy press releases: get_catalog_source federal-reserve-monetary-policy-press-releases,
then create_source with its create_source_args (dry run first), then run_source."

{
  "name": "Federal Reserve monetary policy press releases",
  "url": "https://www.federalreserve.gov/feeds/press_monetary.xml",
  "recipe": {
    "mode": "http",
    "format": "xml",
    "items": "item",
    "fields": {
      "url": "guid",
      "title": "title",
      "category": "category",
      "published": "pubDate",
      "description": "description"
    },
    "required": [
      "url",
      "title"
    ]
  },
  "key_field": "url",
  "schedule": "hourly",
  "rights": true,
  "catalog": {
    "slug": "federal-reserve-monetary-policy-press-releases",
    "version_id": "906100be-c70a-45c2-adbd-71891973375c"
  }
}

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/bank-of-canada-policy-interest-rate -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

sourcefinch login
sourcefinch catalog get bank-of-canada-policy-interest-rate --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Bank of Canada policy interest rate and Bank Rate, daily: get_catalog_source bank-of-canada-policy-interest-rate,
then create_source with its create_source_args (dry run first), then run_source."

{
  "name": "Bank of Canada policy interest rate and Bank Rate, daily",
  "url": "https://www.bankofcanada.ca/valet/observations/V39079,V39078/json?recent=30",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "observations[*]",
    "fields": {
      "date": "d",
      "bank_rate": "V39078.v",
      "policy_rate": "V39079.v"
    },
    "required": [
      "date"
    ],
    "types": {
      "date": "date",
      "bank_rate": "number",
      "policy_rate": "number"
    }
  },
  "key_field": "date",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "bank-of-canada-policy-interest-rate",
    "version_id": "66eda8b6-4b42-4ae2-82d5-d11454494b80"
  }
}

Alerts and evidence

For the Federal Reserve feed, an immediate change email or a webhook delivers each release after the run that finds it. The Bank of Canada monitor adds a record every business day, so a daily digest, or a webhook that compares `policy_rate` with the previous day, avoids an email per day.

Every run keeps the publisher's exact response with its SHA-256 hash and a signed manifest, and every value points back to where it was read. How that works is in the docs:

• Review changes and receipts
• Alerts: change emails and digests
• Evidence and export: what a run keeps, bundles, CSV/JSON/XLSX
• Checking an evidence bundle offline
• Verifying signed webhooks
• Rights and acceptable use

Limitations

• The Federal Reserve feed carries the 15 most recent releases, and release pages are not fetched: a record is the headline, category and time, not the statement text. A release leaving the window is not a withdrawal.
• Speeches, testimony and enforcement actions are separate Federal Reserve feeds and are not read.
• Each Bank of Canada run reads the 30 most recent observations of Valet series V39079 (policy rate) and V39078 (Bank Rate).
• The records say what was announced and when. They are not investment or trading advice.

Usage rights, terms posture and reliability for each source are on its source page. They are our documented understanding of each publisher's stated terms, not legal advice.

Related