Query Client
Access Requirements
To interact with a workload, an end-user will need a unique access key—called a Token—provided by the workload service provider using LatticaAI. This token is crucial for establishing secure connections with the computations and maintaining private communication through the Query Client.
Try Our Demo!
LatticaAI offers demo models using a predefined token. No special permissions needed—just explore the Query Client’s features and experience secure, encrypted interactions firsthand.
Interaction Options
LatticaAI offers a TypeScript SDK for queries within web environments and a Python SDK for integrating secure query capabilities in native applications. We also maintain a GitHub repository, containing the core Fully Homomorphic Encryption (FHE) logic, which covers key generation, encryption, and decryption.
Query Client: Key Functions and Flow
Note on Query Semantics The term query is used generically to describe an encrypted request sent for secure execution. Depending on the workload, a query may represent an inference request, a vectorized search operation, or an execution step of a TFHE-based program.
The Query Client process consists of three stages:
Environment Preparation
Set up an environment to support the Query Client.
One-Time Action: Cryptographic Key Generation
Once the environment is ready, generate a pair of cryptographic keys—an evaluation key and a secret key.
The secret key protects all future interactions with the computation, securing your data every step of the way.
The evaluation key is public and accelerates the computation of these interactions to reduce latency.
This key generation is a one-time process and doesn't need to be repeated for each query.
Last updated
Was this helpful?