Overview
Isaacus is a foundational legal AI research company building AI models, apps, and tools for the legal tech ecosystem.
Isaacus' offering includes Kanon 2 Embedder, the world's best legal embedding model (as measured on the Massive Legal Embedding Benchmark), as well as legal zero-shot classification and legal extractive question answering models.
Isaacus offers first-class support for Haystack through the isaacus-haystack integration package.
Installation
pip install isaacus-haystack
Components
IsaacusTextEmbedder– embeds query text into a vector.IsaacusDocumentEmbedder– embeds HaystackDocuments and writes todocument.embedding.
Quick Example
from haystack import Pipeline, Document
from haystack.document_stores.in_memory import InMemoryDocumentStore
from haystack.components.retrievers.in_memory import InMemoryEmbeddingRetriever
from haystack.utils import Secret
from haystack_integrations.components.embedders.isaacus import (IsaacusTextEmbedder, IsaacusDocumentEmbedder)
store = InMemoryDocumentStore(embedding_similarity_function="dot_product")
embedder = IsaacusDocumentEmbedder(
api_key=Secret.from_env_var("ISAACUS_API_KEY"),
model="kanon-2-embedder", # choose any supported Isaacus embedding model
# dimensions=1792, # optionally set to match your vector DB
)
raw_docs = [Document(content="Isaacus releases Kanon 2 Embedder: the world's best legal embedding model."),
Document(content="Isaacus also offers legal zero-shot classification and extractive question answering models.")]
store.write_documents(embedder.run(raw_docs)["documents"])
pipe = Pipeline()
pipe.add_component("q", IsaacusTextEmbedder(
api_key=Secret.from_env_var("ISAACUS_API_KEY"),
model="kanon-2-embedder",
))
pipe.add_component("ret", InMemoryEmbeddingRetriever(document_store=store))
pipe.connect("q.embedding", "ret.query_embedding")
print(pipe.run({"q": {"text": "Who built Kanon 2 Embedder?"}}))
Docs
- Isaacus Embeddings API: https://docs.isaacus.com/capabilities/embedding
- Haystack: https://haystack.deepset.ai/
License
Apache-2.0
Metadata
Release files for isaacus-haystack 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| isaacus_haystack-0.1.0.tar.gz | 7.3 kB | Without provenance | Details for isaacus_haystack-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| isaacus_haystack-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for isaacus_haystack-0.1.0-py3-none-any.whl |
Total release size: 16.6 kB
Release files / isaacus_haystack-0.1.0.tar.gz
| Download URL | isaacus_haystack-0.1.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddcd781659e0875ffd19cf1374a74c779fa963266497bd0634948fbcdba5fa79
|
|
BLAKE2b-256 checksum How to use checksums |
1447a39287b21c63b3246cdb22629714b95f935312d5246574cef8716a1d74c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Release files / isaacus_haystack-0.1.0-py3-none-any.whl
| Download URL | isaacus_haystack-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
85ba1897f0421794c41b169fa2298f0fb76bbdf4109d3e1f5d0bf0cd55e7149d
|
|
BLAKE2b-256 checksum How to use checksums |
84f1c56c8ae49188f56d2f07687512cdde57197918d7e93068cd701cdeed9ccb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.8
|
Security for isaacus-haystack 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.