APIs please :)

[ZackBradshaw]

What's the problem?
I find integrating Bloop into my Open-Sourcerer project challenging due to the lack of comprehensive documentation and APIs for specific features. This makes it difficult to efficiently utilize Bloop's capabilities for indexing repositories, storing knowledge maps in a vector store, and retrieving them.

What's the solution?
I propose enhancing the documentation and providing well-defined APIs for key features of Bloop. This would greatly streamline the integration process and enable projects like Open-Sourcerer to leverage Bloop's unique capabilities more effectively.

Additional context
Integrating Bloop holds the potential to significantly enhance the functionality of Open-Sourcerer. Having clear documentation and APIs would foster collaboration and innovation within the open-source community while making it easier for developers to harness the power of Bloop in their projects.

[MahmoodKhalil57]

please :)

[Jirito0]

Same here. I'd like to utilize Bloop in a langchain, but it doesn't appear Bloop offers an API.

[TheoMcCabe]

+1 here. Is there any plan to release an API ? I imagine third parties would pay good money for API access to bloops context retrieval for use in building their own tools

[ycclnn]

Still couldn't find api doc in 2024...I started bleep instance as standalone but the only query that returns response is :curl -v "localhost:7878/api/repos/indexed" | jq