That's my main concern - I *know* that people tend to skip those texts even though they know they're required to read them.
I want to make sure your licence is unmissable. I think the easiest way is that I don't include anything with my package, but direct them to a download page where a single package (like radio42 outlines) can be downloaded.
I'm not really a fan of the separate package idea - it's extra maintenance, when releasing updates, etc... I guess you could package the DLLs yourself though (is that what you meant?), and make that a separate download, with the appropriate notices/etc...
By API, do you mean documentation? It shouldn't be necessary since they won't interact directly with Bass, but through my generic sound system wrapper.
Yep, the documentation, but also headers, and even examples. Basically, everything that isn't the DLL