A few points to be made to help give clarity to the scenario:
- The AGPL application and its API can and most likely be customised to suit business needs
- Other unknown licensed applications require to utilise these customised API calls (entry points) to ensure standardisation of calls
- The whole 'network' of other applications are stand alone applications e.g. ERP and CMS. The assumption would be that these talk between one another through the same means i.e. REST API
- Customers (on a SaaS network) would 'connect' to the AGPL application by means of 'indirect' or layered platforms/APIs e.g. customer uses the website portal (CMS) -> eCommerce -> AGPL Application's REST API
I have found few references of explicitly stating API below, but found they don't tackle or highlight the issue of 'how far' does this network interaction goes IF the application has been modified - tons of answers on unmodified though...
Does this mean that if any customisation is required to tailor to a business needs it must be made publicly available (and releasing their business logic advantage) even if the use of the business logic is through Rest APIs or within layers of applications?
If so would a potential solution be to develop and release a separately licensed wrapper around the AGPL application (including the customised API) to manoeuvre around releasing the complete business logic and only the wrapper?