Yeah, definitely. It's a product category called, somewhat prosaically, "enterprise search." Algolia's appropriate for this in that we allow you to define data structures on a per-content source basis, and can show the most relevant results for each content source. Usually, enterprise search providers provide lots of out of the box connectors — with us, you'd just shove JSON into the proper index using one of the API clients.
Security is super important, but we can provide encryption-at-rest and have a secured API key [1] feature that allows you to segment your user base.
Thanks for the rec! I'm obviously super biased (ReadMe founder, here), but ReadMe was built for this kind of scenario, spot on. apiDoc is good for keeping the endpoint docs up to date, and you can keep it internal with a password or admin-only access. Search should be improving later this month.
Thanks for the tip, Tim! Happy to answer any questions folks have about my product.
Also, plugging: Swagger support in just a few weeks. And we can currently auto generate endpoint reference docs from your source code using a commenting standard similar to javadoc.
We get all sorts of excited by good API documentation. Weird, right? Apparently not, based on this thread. :D
As Mark mentions on his summary page, the best place for that kind of information is our CTO's "Inside the Engine" series (8 parts).
https://blog.algolia.com/inside-the-algolia-engine-part-1-in...