There might be an argument for providing both the lower level API and a higher level API though, to allow people to use the lower level as an "escape hatch" for custom abstractions or calls. I've had to reprioritise some projects recently, but it seems like the project where I use authzed is soon coming back up into being prioritised so I hope to be able to look at that issue asking for feedback about reflection and what I did for my poc TypeScript lib. (and maybe even find time to make my lib more production ready)

definitely would agree with this - I've created my own typescript abstraction for my project that covers the basic API's (no streaming or bulk check etc).

Yes, it is. There's still a couple issues with it. Mainly around the generator and schema parser. But it's basically a typesafe version of what I have in an internal codebase

@swantzter let us know if you want to work together on this; we're in early planning on what an official typed client might look like

@Joey I'd be delighted to, but fair warning that I'm probably a little low on cycles the next couple months

no worries