To keep external wire-format quirks out of core domain code.
Third-party JSON often contains awkward names, nullable fields, optional arrays, or units that do not match internal business language. Boundary DTOs absorb those differences so the domain model stays clean.