Or put the API definitions into some database (sqlite, datascript + nodejs or babashka or nbb), then you can decide what http library or mocked http solution would you like to use, eg https://github.com/oliyh/martian

Most of the code is just a thin veneer over that information...

i mean, the go binary would still probably be a bit large, but having a statically linked binary to copy around would be welcome.

Touché!