> this code can only be used under the agplv3 :-)
This code can only be used to make a derived work under the AGPLv3. What constitutes a derived work is still... complicated.
I wouldn't risk this in a production setting for a real business just out of caution, but my reading of the license would suggest that you'd be perfectly fine to wrap AGPLv3 code in a web service and then have your own code interact with that web service. Release the wrapper service as AGPL, but then the rest can be proprietary.
The main protection that AGPL gives isn't legal, it's that you scare most legal departments away just because it's such a weird license with no established precedent.
> I wouldn't risk this
This seems like a technical workaround for a legal requirement. Indeed, that seems risky xD