It doesn't seem like anybody who really knows cares to answer this question, so here's my take on it as a fellow developer.
I suppose that you've had a look at the API Documentation. The API is read-only, which I believe is a reflection of the policy. To put it bluntly, it's simply too easy to wreak havoc upon the database with DIY import tools.
Probably the only feasible way to create profiles on a semi-automatic basis is to create a Gedcom and import it via GEDCompare. I think that the best way to go about it would be to create small batches (say 20-50 profiles) with the bare-bones data, and then fill in with script-generated biographies afterwards.
Great profile, by the way. I'm also doing script-generated biographies from my own database, a self-developed application in PostgreSQL, PHP, and Perl. I'm creating the profiles manually, and do a lot of manual editing, but the automatic export of BMD events and inline references saves me a lot of drudgery.