Two different bets on precision
GoldAPI.io bets on depth within a narrow catalog: gold and silver, LBMA fix redistribution rights, and 20+ years of history. Metals.dev bets on breadth: nine metals under one key, with LBMA, LME, MCX, and IBJA blended together rather than exposed as separate rows. Neither approach is wrong, they're built for different buyers.
Pricing
Metals.dev's entry point is considerably cheaper: $1.79/mo for 2,000 requests against GoldAPI.io's $4.99/mo, and Metals.dev's free tier (100 requests/month, no card) is explicitly documented where GoldAPI.io's free-tier limits aren't spelled out in its public pricing page. At the top end, GoldAPI.io's $129/mo production plan sits well above Metals.dev's $39.99/mo for 100,000 requests, though the two aren't metering the same thing (a production-scale redistribution license vs a request-volume cap).
Coverage: narrow vs broad
GoldAPI.io claims the deeper historical record on gold specifically, 20+ years against Metals.dev's 5+ years, and Metals.dev caps any single historical request to a 30-day window. Metals.dev wins decisively on catalog width: platinum, palladium, aluminum, copper, nickel, lead, and zinc are all in scope, none of which GoldAPI.io's own comparison page claims to cover.
Source attribution
Metals.dev names its authority sources (a dedicated LBMA/LME/MCX/IBJA endpoint exists) but still returns one blended number per metal without disclosing how the blend is weighted. GoldAPI.io holds LBMA fix redistribution rights, a real license claim, but its public docs don't describe a named-source breakdown the way Metals.dev's authority endpoint does. Neither publishes per-source timestamps or a staleness flag.