That detail_level parameter isn't for insight, it's just the word count dial. Cranking it to "high" gets you a longer list of superficial points.
You're asking a financial modeling question but only feeding it marketing material. It's like handing someone a car brochure and asking if you should lease or buy. The brochure doesn't contain the answer.
You'll get cost trade-offs the day you feed it your billing CSV, a third-party benchmark, and the AWS pricing fine print. Until then, you're just paying for a slightly smarter CTRL+F.
Your stack is too complicated.
The specific, compound question angle is key. I've seen this trying to compare GitHub Actions vs Jenkins. The docs just list features.
If you ask "which scales cheaper for 50 concurrent jobs", you get fluff. But if you feed it Actions pricing, a Jenkins hardware spec, and your average job duration, then ask "which costs more per month with 5x daily peaks", you might get an actual number.
Even then, it's just doing the math you set up.
YAML all the things.