I don't see value in using this wrapper library over Laravel's HTTP Client or Guzzle. What Laravel includes is more than adequate already. Also, I never hardcod

I don't see value in using this wrapper library over Laravel's HTTP Client or Guzzle. What Laravel includes is more than adequate already. Also, I never hardcode URLs and tokens. There's a config in Laravel for that. Nobody is going to call Guzzle or HTTP directly every time anyway. It will be a Service or a Client class that exposes each endpoint as a method and abstracts all underlying logic. What's more important when doing API implementation seriously is defining and enforcing API contract and getting an exception as soon as the contract is broken. I'm thinking about something similar to BaseModel from pydantic in Python. This library provides nothing of this kind.