Artemis Search is built on several interconnected components that work together to provide powerful, reasoning-based searches. The following diagram illustrates how these components relate to each other:
This diagram illustrates the structure of Artemis Search, highlighting key relationships:
Each project serves a particular search task. Each project may have multiple datasets but only one can be active at a time. Further, each project has dedicated machines to process search requests.
Datasets are two-column Pandas dataframes saved as parquet files with two columns (embedding and tags), and only one at a time may be activated.
Machines are cloud servers which process the search requests on the active dataset. These are automatically load balanced.
Let’s explore each of these components in more detail.
Artemis Search goes beyond traditional keyword matching or semantic similarity. Our technology uses task-specialized ML ranking models to enable us to bake “reasoning” and “context” into searches.
For example, when searching for “companies that require HIPAA compliance”, our system doesn’t just find companies related to medicine or HIPAA compliance. It actually reasons about which companies would be subject to HIPAA regulations based on their descriptions and activities.
Synthetic Dataset Size: Controls how much synthetic data is generated for each search request. This parameter must be between 10 and 70. Tuning this parameter allows you to balance between search accuracy and performance.
Probability Threshold: Filters results to keep only those above a certain probability of matching the search query. This parameter must be between 0 and 1. Tuning this parameter truncates results but does not affect search time.
Top-K Threshold: Limits the number of top results returned. This parameter must be between 1 and Infinity. Tuning this parameter truncates results but does not affect search time.
Adjusting these parameters allows you to fine-tune the balance between search accuracy and performance.
Artemis Search provides a RESTful API for seamless integration with your applications.
Each organization has its own API key for authentication.
The main endpoint is /search, which accepts parameters like search_query, num_batches, top_k, filter_query, and project_id.
API requests must include your API token in the Authorization header.
For detailed API documentation, check out our API Reference section.
Understanding these key concepts will help you leverage the full power of Artemis Search in your projects. If you’re ready to start building, head over to our Quickstart Guide to set up your first project.