JiggyBase
API DocumentationIntroducing JiggyBase, the cutting-edge tool that's redefining the way we interact with digital data. Designed to mine through your personal or work-related document collections—including files, emails, web pages, or any data—JiggyBase is an information retrieval system that provides factual, up-to-date responses to your queries. The tool operates by accessing the /collections endpoint to list all available collection names for a user, then proceeding to /query to sift through this curated list. What sets JiggyBase apart is its ability to furnish users with precise document titles and collection names, providing a clear understanding of the source for the information in its responses. The tool is meticulous in its approach, ensuring that it only offers facts that are corroborated by the information within the user's documents. JiggyBase is not just a tool, but an innovative solution for those who value accuracy, efficiency, and transparency in their data interactions.
Share:
Tags:
Example Prompts
"Can you fetch all collections available to me?"
"Can you provide me with a list of all collections that I can use?"
"What collections can I search in?"
"Can you perform a query for 'machine learning' in my collection?"
"Search for documents that contain 'neural networks' in my collection."
"I need to find all documents related to 'climate change' in my collection."
"Can you filter my documents by the author 'John Doe'?"
"Show me all documents created between
"Search for 'Quantum Physics' in my collection and return the top
"I need to find all documents with the title 'Artificial Intelligence' in my collection."
"Can you perform a query for 'blockchain technology' in my collection?"
"Filter my documents by the source 'email'."
"Can you fetch all documents from the source 'file'?"
"Show me all documents from the source 'chat'."
"Can you filter my documents by the source 'web'?"
Description for AI
Tool for searching through the user's collections of documents (such as files, web pages, emails, data, etc) to find answers to questions and retrieve relevant information. Use it whenever a user asks something that might be found in their personal or work information. Use the /collections endpoint once before calling /query to get the list of collection names available for a user. Use only the information provided by the query response to answer the user. Provide references to document titles and collection names to help the user understand the source for the info in your responses. Do not provide facts that are not supported by information in the user documents.