In my research of AGPL I have found that creating REST API around AGPL licensed library is enough to make it communication at arms length and as such it bypasses the need to publish all of your codebase.
If I was interested in using iText (which is offered under AGPL and Commercial licence) for free in closed source commercial software without disclosing the source code to the user or public, creating REST API and putting it in docker container should be fine.
What I have noticed is that the text on their website describes license in a way that is contradictory to that statement. (Emphasis mine)
Buying a license is mandatory as soon as you develop commercial activities distributing the iText software inside your product or deploying it on a network without disclosing the source code of your own applications under the AGPL license.
How to use the AGPL license correctly? The AGPL license comes with a couple of restrictions you should be well aware of.
You may not deploy it on a network without disclosing the full source code of your own applications under the AGPL license. You must distribute all source code, including your own product and web-based applications.
It’s a legal violation to use iText Community and our open source add-ons in a non-AGPL environment.
My question is how is this contradiction resolved? Are they offering it under a AGPL license only under additional conditions, are they altering the license or is that just useless flavor text which describes their (potentially wrong) understanding of AGPL.