inertialai-chroma
InertialAI embeddings integration for Chroma — supports text-only, time-series-only, and multi-modal (text + time-series) semantic search via the inertial-embed-alpha model.
Overview
InertialAI's inertial-embed-alpha model produces dense vector embeddings from three input types:
| Input type | Example |
|---|---|
| Text only | "temperature spike at noon" |
| Time-series only | [[72, 74, 73, 75, 71]] (e.g. heart rate readings) |
| Multi-modal | A time-series signal paired with its natural language description, combined into a single vector |
Multi-modal embeddings are InertialAI's core differentiator — a single vector that captures both the numerical signal and its semantic context simultaneously, enabling richer similarity search across domains like industrial IoT, healthcare, and financial markets.
inertialai-chroma implements Chroma's full eight-method EmbeddingFunction interface, including get_config() and build_from_config(), so that collections can be persisted to disk and reconstructed without storing credentials.
Requirements
- Python 3.11 or later
- An InertialAI API key — sign up at app.inertialai.com
- A running Chroma instance — see Chroma Docker deployment
Installation
pip install inertialai-chroma
# or
uv add inertialai-chroma
Quickstart
Set your API key as an environment variable:
export INERTIALAI_API_KEY="your-api-key"
Then create a collection and start embedding:
import chromadb
from inertialai_chroma import InertialAIEmbeddingFunction
client = chromadb.HttpClient(host="localhost", port=8000)
ef = InertialAIEmbeddingFunction() # reads INERTIALAI_API_KEY from env
collection = client.create_collection("sensors", embedding_function=ef)
collection.add(
documents=[
"temperature spike at noon",
"stable overnight readings",
"pressure anomaly detected",
],
ids=["doc-1", "doc-2", "doc-3"],
)
results = collection.query(query_texts=["anomalous thermal event"], n_results=2)
print(results["documents"])
Multi-modal Embeddings
Since Chroma documents are always strings, multi-modal inputs are passed as JSON-serialised dicts containing a text field, a time_series field, or both. Time-series data is formatted as a list of channels, where each channel is a list of numerical readings.
import json
import chromadb
from inertialai_chroma import InertialAIEmbeddingFunction
client = chromadb.HttpClient(host="localhost", port=8000)
ef = InertialAIEmbeddingFunction()
collection = client.create_collection("energy", embedding_function=ef)
# Each document pairs a text description with its raw time-series readings
collection.add(
documents=[
json.dumps({
"text": "Energy price spike Q4 2022",
"time_series": [[1.2, 1.5, 1.8, 2.1, 2.4]],
}),
json.dumps({
"text": "Stable energy prices Q1 2023",
"time_series": [[0.9, 0.9, 0.91, 0.88, 0.9]],
}),
],
ids=["doc-1", "doc-2"],
)
# Query with a multi-modal input — or just plain text
results = collection.query(
query_texts=[
json.dumps({"text": "abnormal energy reading", "time_series": [[1.3, 1.6, 2.0]]})
],
n_results=1,
)
print(results["documents"])
Configuration
InertialAIEmbeddingFunction(
api_key_env_var="INERTIALAI_API_KEY", # default
model_name="inertial-embed-alpha", # default
dimensions=None, # default — use full embedding size
timeout=60.0, # default — seconds
)
| Parameter | Type | Default | Description |
|---|---|---|---|
api_key_env_var |
str |
"INERTIALAI_API_KEY" |
Name of the environment variable holding the API key |
model_name |
str |
"inertial-embed-alpha" |
InertialAI model to use for embedding |
dimensions |
int | None |
None |
Truncate embedding output to this many dimensions |
timeout |
float |
60.0 |
HTTP request timeout in seconds |
api_key |
str | None |
None |
(Deprecated) Pass the key value directly — not persisted by Chroma; prefer api_key_env_var |
Note:
model_nameanddimensionsare immutable after a collection is created — changing either would invalidate the existing vector index.
Collection Persistence
When Chroma persists a collection to disk, it serialises the embedding function via get_config(). InertialAIEmbeddingFunction stores the environment variable name, never the key value itself, so serialised collections are safe to commit to version control. At load time, build_from_config() resolves the key from the environment automatically — no credentials need to be passed explicitly.
Links
Metadata
Release files for inertialai-chroma 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 |
|---|---|---|---|---|
| inertialai_chroma-0.1.0.tar.gz | 166.5 kB | With provenance | Details for inertialai_chroma-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| inertialai_chroma-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for inertialai_chroma-0.1.0-py3-none-any.whl |
Total release size: 177.1 kB
Release files / inertialai_chroma-0.1.0.tar.gz
| Download URL | inertialai_chroma-0.1.0.tar.gz |
|---|---|
| Size | 166.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72053541d87e54da1429ca85870ad225cd2fe8f26241347c019bcfcaf774efc6
|
|
BLAKE2b-256 checksum How to use checksums |
f1cda772b3491e97292337ef827c73d1d85af112eca80e2ea8949f9a44b9ec7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 11, 2026.
Transparency logRelease files / inertialai_chroma-0.1.0-py3-none-any.whl
| Download URL | inertialai_chroma-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d48c010997143a2bda21da95d72371b11ad89d3a8c9a1cf5ffc1c6f4a6fb21f
|
|
BLAKE2b-256 checksum How to use checksums |
ae8cd8fbf25e5a6d5d2354d9f71cc2f4207ec9e33b868301744dca9aa12be99a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 11, 2026.
Transparency logSecurity for inertialai-chroma 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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for inertialai_chroma-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 11, 2026.
Transparency logA 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.