Algo-Trading Bitcoin on Coinbase with FXMacroData Macro Signals

Why Macro Data Drives Bitcoin

Bitcoin trades less like a technology stock and more like a macro asset. It pays no dividends, reports no earnings, and has no cash-flow model to anchor its value. Instead, BTC moves with global liquidity conditions, real interest rate expectations, and dollar strength — the same forces that drive EUR/USD and AUD/JPY. That means the macro toolkit built for FX traders applies directly to Bitcoin.

When the Fed eases, dollar liquidity floods risk markets and BTC tends to lead the charge. When CPI surprises to the upside, monetary debasement narratives push capital into hard assets. When breakeven inflation rises, real yields compress and gold rallies alongside BTC. Every one of these signals is observable in advance via FXMacroData's indicator endpoints — timestamped to the second and available over a clean REST API.

This guide builds a macro-signal-driven algorithmic trading bot for BTC-USD on Coinbase Advanced Trade. By the end you will have a working Python strategy that:

• Pulls USD policy rate, inflation, breakeven inflation, and gold data from FXMacroData
• Combines them into a composite macro regime score
• Schedules execution around high-impact macro releases via the FXMacroData release calendar
• Submits BTC-USD market orders on Coinbase using the official coinbase-advanced-py SDK

Prerequisites

Before starting, make sure you have the following ready:

• Python 3.10+ — all snippets use modern typing syntax
• FXMacroData API key — sign up at /subscribe and grab your key from the account dashboard
• Coinbase Advanced Trade account with a funded USD balance — create a Cloud API Trading Key (API key name + EC private key) in the Developer Platform console with Trade permissions enabled
• Python packages: requests, coinbase-advanced-py, pandas, schedule

pip install requests coinbase-advanced-py pandas schedule

Store your credentials as environment variables — never hard-code secrets in source files:

export FXMACRO_API_KEY="YOUR_FXMACRODATA_KEY"
export COINBASE_API_KEY_NAME="organizations/ORG_ID/apiKeys/KEY_ID"
export COINBASE_PRIVATE_KEY="-----BEGIN EC PRIVATE KEY-----
MHQCAQEEIBs...
-----END EC PRIVATE KEY-----"

Step 1: Fetch Macro Signals from FXMacroData

Four macro series anchor the BTC regime model: the USD policy rate, CPI inflation, the 10-year breakeven inflation rate, and gold spot price. Together they describe the liquidity environment, inflation regime, and hard-asset demand sentiment.

import os
import requests

BASE_URL = "https://fxmacrodata.com/api/v1"
FXMACRO_KEY = os.environ["FXMACRO_API_KEY"]


def get_series(path: str, start: str = "2024-01-01") -> list[dict]:
    """Fetch a time-series from FXMacroData."""
    resp = requests.get(
        f"{BASE_URL}{path}",
        params={"api_key": FXMACRO_KEY, "start": start},
        timeout=10,
    )
    resp.raise_for_status()
    return resp.json()["data"]


# Macro inputs
policy_rate   = get_series("/announcements/usd/policy_rate")
cpi           = get_series("/announcements/usd/inflation")
breakeven_10y = get_series("/announcements/usd/breakeven_inflation_rate")
gold          = get_series("/commodities/gold")

# data[0] is always the most recent reading
print(f"Policy rate (latest): {policy_rate[0]['val']}%")
print(f"CPI (latest):          {cpi[0]['val']}%")
print(f"10Y breakeven:         {breakeven_10y[0]['val']}%")
print(f"Gold spot:             ${gold[0]['val']:.2f}")

Each endpoint returns data ordered most-recent first. For macro indicators, val holds the headline figure and announcement_datetime carries the second-level release timestamp — useful for scheduling covered in Step 4. For commodities, val is the spot price.

Step 2: Build a Composite Macro Score

Rather than reacting to a single indicator, a composite score synthesises all four signals into one directional number between -1 (risk-off, BTC bearish) and +1 (risk-on, BTC bullish). Each component contributes a weighted term based on whether its current reading historically supports or opposes BTC.

def macro_score(
    policy_rate_pct: float,
    cpi_pct: float,
    breakeven_pct: float,
    gold_usd: float,
    *,
    gold_baseline: float = 1900.0,
) -> float:
    """
    Returns a composite macro score in [-1, +1].

    Positive = risk-on / BTC bullish environment.
    Negative = risk-off / BTC bearish environment.
    """
    score = 0.0

    # ── Policy rate regime (weight 0.35) ──────────────────────────────
    # Below 4.5% = accommodative → bullish; above 5.5% = restrictive → bearish
    if policy_rate_pct < 4.5:
        score += 0.35
    elif policy_rate_pct <= 5.5:
        score += 0.35 * (5.5 - policy_rate_pct) / 1.0
    else:
        score -= 0.20

    # ── Inflation regime (weight 0.25) ────────────────────────────────
    # 2–4% moderate inflation → neutral/slightly bullish
    # >6% high inflation → debasement narrative → bullish
    # <1.5% deflationary risk → bearish
    if cpi_pct > 6.0:
        score += 0.25
    elif cpi_pct >= 2.0:
        score += 0.10
    else:
        score -= 0.15

    # ── Breakeven inflation (weight 0.20) ─────────────────────────────
    # Rising breakevens signal re-anchoring inflation expectations → bullish
    if breakeven_pct >= 2.5:
        score += 0.20
    elif breakeven_pct >= 2.0:
        score += 0.10
    else:
        score -= 0.10

    # ── Gold trend (weight 0.20) ──────────────────────────────────────
    # Gold above baseline confirms hard-asset demand → bullish
    gold_ratio = (gold_usd - gold_baseline) / gold_baseline
    score += 0.20 * max(-1.0, min(1.0, gold_ratio * 5))

    return round(max(-1.0, min(1.0, score)), 4)


score = macro_score(
    policy_rate_pct=policy_rate[0]["val"],
    cpi_pct=cpi[0]["val"],
    breakeven_pct=breakeven_10y[0]["val"],
    gold_usd=gold[0]["val"],
)
print(f"Composite macro score: {score:+.4f}")
# e.g. → +0.6000  (bullish regime)

Step 3: Connect to the Coinbase Advanced Trade API

The official coinbase-advanced-py library wraps Coinbase's REST API and handles JWT authentication automatically. Instantiate a RESTClient using your Cloud API Trading Key name and the associated EC private key.

import os
import uuid
from coinbase.rest import RESTClient

CB_KEY_NAME    = os.environ["COINBASE_API_KEY_NAME"]
CB_PRIVATE_KEY = os.environ["COINBASE_PRIVATE_KEY"]

client = RESTClient(api_key=CB_KEY_NAME, api_secret=CB_PRIVATE_KEY)

# Verify connectivity and fetch current BTC-USD price
product = client.get_best_bid_ask(product_ids=["BTC-USD"])
bids = product["pricebooks"][0]["bids"]
asks = product["pricebooks"][0]["asks"]
btc_price = (float(bids[0]["price"]) + float(asks[0]["price"])) / 2
print(f"BTC-USD mid-price: ${btc_price:,.2f}")

# Available USD balance
accounts = client.get_accounts()
usd_balance = 0.0
btc_balance = 0.0
for acct in accounts["accounts"]:
    if acct["currency"] == "USD":
        usd_balance = float(acct["available_balance"]["value"])
    if acct["currency"] == "BTC":
        btc_balance = float(acct["available_balance"]["value"])

print(f"Available USD: ${usd_balance:,.2f}")
print(f"Available BTC: {btc_balance:.6f}")

Step 4: Schedule Around Macro Release Events

One of FXMacroData's most powerful features for algo trading is the release calendar endpoint. Instead of polling on a fixed timer, you query the exact scheduled release time for any indicator and trigger your signal refresh precisely when new data prints.

import datetime
import schedule
import time


def get_next_release(currency: str, indicator: str) -> datetime.datetime | None:
    """
    Returns the next scheduled release datetime for an indicator.
    The calendar endpoint returns upcoming events in ascending date order.
    """
    resp = requests.get(
        f"{BASE_URL}/calendar/{currency}",
        params={"api_key": FXMACRO_KEY},
        timeout=10,
    )
    resp.raise_for_status()
    events = resp.json().get("data", [])

    now_utc = datetime.datetime.now(tz=datetime.timezone.utc)
    for event in events:
        if event.get("indicator") != indicator:
            continue
        release_str = event.get("release_datetime") or event.get("date")
        if not release_str:
            continue
        release_dt = datetime.datetime.fromisoformat(
            release_str.replace("Z", "+00:00")
        )
        if release_dt > now_utc:
            return release_dt
    return None


# Example: find the next FOMC policy rate decision
next_fomc = get_next_release("usd", "policy_rate")
if next_fomc:
    delta = next_fomc - datetime.datetime.now(tz=datetime.timezone.utc)
    print(f"Next FOMC: {next_fomc.isoformat()}  ({delta.days}d {delta.seconds // 3600}h away)")

# Example: find the next CPI print
next_cpi = get_next_release("usd", "inflation")
if next_cpi:
    print(f"Next CPI:  {next_cpi.isoformat()}")

With the exact release timestamp, you can schedule a post-release signal refresh — allowing the initial price reaction to settle before re-scoring and trading:

def on_macro_release():
    """Called shortly after a scheduled macro release fires."""
    print("Macro release detected — refreshing signals...")
    run_strategy()


def schedule_next_release(currency: str, indicator: str, delay_seconds: int = 90):
    """
    Schedules the strategy to run 'delay_seconds' after the next release.
    A 90-second delay lets the initial market reaction absorb before entry.
    """
    release_dt = get_next_release(currency, indicator)
    if not release_dt:
        return

    fire_at = release_dt + datetime.timedelta(seconds=delay_seconds)
    fire_str = fire_at.strftime("%H:%M:%S")
    schedule.every().day.at(fire_str).do(on_macro_release).tag(
        f"{currency}_{indicator}"
    )
    print(f"Scheduled refresh at {fire_str} UTC after {currency.upper()} {indicator}")


schedule_next_release("usd", "policy_rate", delay_seconds=90)
schedule_next_release("usd", "inflation", delay_seconds=60)

Step 5: Size Positions and Submit Orders on Coinbase

Coinbase Advanced Trade orders work differently from Binance: buy orders specify a quote_size (USD amount to spend), while sell orders specify a base_size (BTC amount to sell). The sizing function below scales the USD allocation with the absolute magnitude of the macro score — higher conviction warrants a larger allocation, capped at a configurable maximum.

import math


def compute_usd_allocation(
    score: float,
    usd_balance: float,
    max_position_pct: float = 0.20,
    min_threshold: float = 0.30,
) -> float:
    """
    Returns the USD amount to deploy for a BUY order.
    Scales between 0 and max_position_pct of available USD balance.
    Returns 0.0 if |score| < min_threshold (noise-filtered).
    Minimum order size on Coinbase Advanced Trade is $1 USD.
    """
    if abs(score) < min_threshold:
        return 0.0
    conviction = (abs(score) - min_threshold) / (1.0 - min_threshold)
    usd_to_trade = usd_balance * max_position_pct * conviction
    return max(1.0, round(usd_to_trade, 2))


def place_buy(usd_amount: float) -> dict | None:
    """Submit a market BUY order for a given USD amount."""
    if usd_amount <= 0:
        print("USD amount zero — no buy order placed.")
        return None
    order_id = str(uuid.uuid4())
    try:
        result = client.market_order_buy(
            client_order_id=order_id,
            product_id="BTC-USD",
            quote_size=str(usd_amount),
        )
        print(f"BUY order submitted: ${usd_amount:.2f} USD  (order_id={order_id})")
        return result
    except Exception as exc:
        print(f"Coinbase buy error: {exc}")
        return None


def place_sell(btc_amount: float) -> dict | None:
    """Submit a market SELL order for a given BTC amount."""
    # Minimum BTC lot size on Coinbase Advanced Trade is 0.000001 BTC
    btc_amount = math.floor(btc_amount * 1_000_000) / 1_000_000
    if btc_amount <= 0:
        print("BTC amount zero — no sell order placed.")
        return None
    order_id = str(uuid.uuid4())
    try:
        result = client.market_order_sell(
            client_order_id=order_id,
            product_id="BTC-USD",
            base_size=str(btc_amount),
        )
        print(f"SELL order submitted: {btc_amount:.6f} BTC  (order_id={order_id})")
        return result
    except Exception as exc:
        print(f"Coinbase sell error: {exc}")
        return None

Step 6: Assemble the Full Strategy Loop

Now bring all the pieces together into a single run_strategy() function. On each call it fetches fresh macro data, recomputes the score, detects a regime change, and either enters or exits accordingly. State is persisted to a JSON file so the process can survive restarts without losing position tracking.

import json
import pathlib

STATE_FILE = pathlib.Path("coinbase_strategy_state.json")


def load_state() -> dict:
    if STATE_FILE.exists():
        return json.loads(STATE_FILE.read_text())
    return {"position_btc": 0.0, "last_score": 0.0}


def save_state(state: dict) -> None:
    STATE_FILE.write_text(json.dumps(state, indent=2))


def run_strategy() -> None:
    state = load_state()

    # ── 1. Refresh macro data ──────────────────────────────────────────
    policy_rate_val = get_series("/announcements/usd/policy_rate")[0]["val"]
    cpi_val         = get_series("/announcements/usd/inflation")[0]["val"]
    breakeven_val   = get_series("/announcements/usd/breakeven_inflation_rate")[0]["val"]
    gold_val        = get_series("/commodities/gold")[0]["val"]

    # ── 2. Compute macro score ─────────────────────────────────────────
    score = macro_score(policy_rate_val, cpi_val, breakeven_val, gold_val)
    prev  = state["last_score"]
    print(f"Macro score: {score:+.4f}  (prev: {prev:+.4f})")

    # ── 3. Fetch current Coinbase balances ─────────────────────────────
    accounts  = client.get_accounts()
    usd_avail = 0.0
    btc_avail = 0.0
    for acct in accounts["accounts"]:
        if acct["currency"] == "USD":
            usd_avail = float(acct["available_balance"]["value"])
        if acct["currency"] == "BTC":
            btc_avail = float(acct["available_balance"]["value"])

    # ── 4. Regime change logic ─────────────────────────────────────────
    is_bullish = score >= 0.30
    was_bullish = prev >= 0.30
    is_neutral  = abs(score) < 0.30
    is_bearish  = score < -0.30

    if is_bullish and not was_bullish:
        # New bullish regime — enter long via USD allocation
        usd_to_use = compute_usd_allocation(score, usd_avail)
        place_buy(usd_to_use)

    elif is_neutral and was_bullish and btc_avail > 0.000001:
        # Regime turned neutral — exit position
        place_sell(btc_avail)
        print("Regime neutral — exiting BTC position.")

    elif is_bearish and btc_avail > 0.000001:
        # Hard exit on bearish macro signal
        place_sell(btc_avail)
        print("BEARISH regime — full exit.")

    # ── 5. Persist state ───────────────────────────────────────────────
    state["last_score"] = score
    state["position_btc"] = btc_avail
    save_state(state)


# ── Run once on startup, then on each scheduled macro release ──────────
run_strategy()

while True:
    schedule.run_pending()
    time.sleep(10)

Step 7: Risk Management and Operational Considerations

A macro-signal strategy trades infrequently — regime changes driven by FOMC, CPI, and NFP prints typically produce 6–10 actionable signals per year. That low frequency is by design: you are positioning for multi-week directional moves, not intraday noise. But each position carries meaningful risk, so disciplined controls are essential.

All timestamps from FXMacroData — including announcement_datetime in indicator responses and release datetimes from the calendar endpoint — are UTC. Keep your scheduling logic in UTC throughout and convert only for display purposes. This eliminates daylight-saving ambiguity around US data releases, which is a common source of scheduler bugs.

Extending the Strategy

The framework is modular. Several natural extensions are worth exploring next:

• Add COT positioning data — FXMacroData's CFTC COT endpoint provides weekly speculative positioning in USD futures. Extreme short-USD positioning has historically been a tailwind for BTC. Pull it at /cot/usd and add a net-positioning term to the macro score.
• Multi-currency liquidity index — incorporate EUR, JPY, and GBP macro signals alongside USD. When multiple G10 central banks are easing simultaneously, global liquidity conditions are most favourable for risk assets like BTC.
• Breakeven velocity signal — rather than the level of breakeven inflation, use the 4-week rate of change. A sharp rise in breakevens is an earlier and more timely signal than the level alone.
• Limit order execution — replace market_order_buy/market_order_sell with limit_order_gtc_buy/limit_order_gtc_sell to avoid paying the full taker spread. Fetch the current order book with client.get_best_bid_ask and sit one tick inside the best bid/ask.
• Release calendar clustering — query the release calendar for all USD events one month out and identify windows where multiple high-impact releases cluster within 48 hours. Those dense windows are the highest-conviction periods for positioning.

Summary

You now have a working macro-signal-driven Bitcoin trading bot connected to Coinbase Advanced Trade. The strategy reads USD policy rate, CPI, breakeven inflation, and gold from FXMacroData to construct a composite regime score, schedules itself around real-world macro announcement events, and submits BTC-USD market orders proportional to regime conviction.

The macro approach trades infrequently and with high conviction — which is precisely what separates regime-based strategies from noise-chasing technical systems. The next logical step is back-testing this framework against historical FXMacroData time-series to calibrate score weights and measure drawdown across multiple Fed cycles.