Agile is about doing things which provide value to the customer or product owner.

You have an API which fulfills its purpose in its current form, but it is not really REST compliant. The only reason to extend effort to make it REST compliant seem to be that you at one point decided that it was supposed to be REST. That line of thinking is not agile.

REST can of course be perfectly fine in an agile project if you actually need it. But it seems you don't.

Agile is about doing the things which provide the most value to the customer or product owner. There is nothing special about REST in this, it applies to any feature or task you might spend effort on: Is this the best possible use of your time, of would you generate more value by working on something else?

You have an API which fulfills its purpose in its current form, but it is not really REST compliant. The only reason to extend effort to make it REST compliant seem to be that you at one point decided that it was supposed to be REST. That line of thinking is definitely not agile.

REST can of course be perfectly fine in an agile project if you actually need it and it provides value. But it seems you don't.