My understanding is the same as kylebarron's[0] since you lack linking protections (which you would get under LGPL), so any work that includes cozo would be a "derived work" under the (A)GPL. Interestingly there doesn't seem to be an affero LGPL license[1], which could be what you might want here.
Otherwise, simplest solution provided you want a copyleft license would be to use the LGPL I think.
We kinda do have it; it's just mostly useless, given the linking clause. (Not entirely useless, though, as that article sets out.)
GPL and AGPL have the same layout, so you can just take the LGPL, and replace all references to 'GPL' and 'GNU General Public License' with 'AGPL' and 'GNU Affero General Public License'. Of course, you couldn't call that license 'GNU ALGPL' or 'GNU LAGPL'; you'd have to come up with your own name. (Disclaimer: I'm not a lawyer, and I haven't checked this as thoroughly as I would if I were going to use this for my own software.)
Maybe it's worth bothering Bradley M. Kuhn (http://ebb.org/bkuhn/) again and seeing what the current status of a Lesser AGPL is?
Otherwise, simplest solution provided you want a copyleft license would be to use the LGPL I think.
NOTE: not a lawyer.
[0] https://softwareengineering.stackexchange.com/questions/1078...
[1] https://redmonk.com/dberkholz/2012/09/07/opening-the-infrast... (old link, but I couldn't find anything since then describing this kind of license?)