Claude confidently gave incorrect advice on Apple MusicKit API access tier, costing the user money

Resolved 💬 3 comments Opened Apr 26, 2026 by TBSammy Closed May 28, 2026

Claude recommended Apple MusicKit JS for playlist creation and when explicitly asked whether a personal or business Apple Developer account was required, stated a personal account was sufficient. This was wrong. A personal account does not provide the MusicKit API access needed. The user paid for an Apple Developer account based on Claude's advice and hit a hard wall.

Claude later recommended Spotify as an alternative in the same project context, then when questioned acknowledged Spotify's preview API is heavily restricted — again, something it should have known before suggesting it.

The core issue: Claude stated a confident, specific, factually incorrect answer to a direct question about API access tiers. The user made a financial decision based on that answer. Claude should either know the correct answer or say "I'm not certain, verify with Apple's documentation before paying."

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗