1. for purchases.  I've been doing this with web scrapers.  I do it at Daz with the same method.  By virtue of how Daz has coded their website, it's easier.  In effect, they download your entire purchase library to browser memory.  This is why their filtering, sorting, and searching are so fast.  There is no round trip to server.  For my purposes, it's almost an API in that I can just retrieve the download library from a single URL.  With rendo, the library has to be retrieved by page, with a sever roundtrip each time.  It must be brutal on rendo servers :p

2. for catalog.  My code wants to make rendo quickly searchable during a Poser session.  It looks in 1) installed content 2) my cached uninstalled content and 3) online content suppliers.  Then I can purchase (acquire) the content right then, it downloads into my repo, installs, optimises and refreshes library.  Without losing content/time.

Yes, I know Rendo has some integration with Poser in that direction.  1) it's suboptimal for me.  2) rendo is just one source.  A great one, to be sure.  Which is why I'm suggesting :)