From what I heard of this audio bot, he doesn't distribute it. Rather you have to give him your server details and only then he'll just plop an instance of it there.
The reason he probably does this and also why there aren't many TT bots, is that unlike Teamspeak or Discord where the developers have public, freely available bot API's and encourage bot development, the developer of TeamTalk doesn't. There is an SDK that allows you to do everything that a normal client can, but he's aiming it more at companies wanting to integrate it into their software (for example the voice chat rooms on the serotek system access network if anyone remembers those). This SDK is also priced appropriately as such, costing somewhere between 6 to 800 euros if memory surves. That puts it out of reach of most people who'd just want to make bots.
The TT protocol has been reverse engineered to an extent, which is why we now have things like Dug's TTCom console. In theory you could use its underlying code to make a bot, but its capabilities only extend to text. So bots written this way wouldn't be able to transmit or receive audio from channels.
<Insert passage from "The Book Of Chrome" here>