That is not true. If you expose an service based on AGPL licensed service, you have to make the source code available to the services that use it. For example

That is not true. If you expose an service based on AGPL licensed service, you have to make the source code available to the services that use it. For example you could modify WordPress (which is GPL licensed), put it on your server and let it serve pages without providing your modified source code to anyone. If WordPress was AGPL licensed you would have to provide your modified source code to anyone using the system. This also effects services that use libraries that are AGPL licensed (like newer versions of iText), but not services, that use other services. The point is AGPL only adds that if you consume it over the network, you have the right to the source code. If you use it as a network service, for your webapp, your webapp is the consumer. MongoDB has the same licensing model, and nobody sued Foursquare for the source code, so I guess this is legally tested ;)