Skip to main content

limma-ai

The Limma client: the Python SDK for Limma's agent verbs, and the limma command.

Limma gets the right information to an AI agent: every fact at an address, with a receipt that redeems to the exact bytes of the document it came from, and a count that says whether you hold all of them.

Install

pip install limma-ai                  # the SDK (import limma) and the `limma` command
pip install "limma-ai[s3]"            # + reading S3 buckets (also: [azure], [gcs])
pip install "limma-ai[gdrive]"        # + Google Drive      (also: [sharepoint])

The distribution is limma-ai; the package you import and the command are limma.

Keep a folder, a bucket, a Drive folder or a SharePoint library in Limma

export LIMMA_API_KEY=<your key>
limma sync ./contracts --url https://api.limma.ai
limma sync s3://my-bucket/contracts --url https://api.limma.ai --delete --watch 300
limma sync gdrive://<folder-id> --url https://api.limma.ai
limma sync "sharepoint://contoso.sharepoint.com/sites/finance/Shared Documents" --url https://api.limma.ai

Without --workspace the files go to your key's default workspace (created on first use); each pass prints its id. limma sync --help lists every option.

Use it from Python

from limma import LimmaClient

client = LimmaClient(api_key="<your key>", base_url="https://api.limma.ai")
client.ingest("Ingrid Solberg was appointed CFO on 1 March 2024.", filename="minutes.txt")
facts = client.facts("Who is the chief financial officer?")["facts"]
receipt = client.region(facts[0]["source_id"], facts[0]["char_start"], facts[0]["char_end"],
                        page=facts[0].get("page"))

Every method takes workspace_id= to name another workspace your key reaches.

Attach an agent

Agents attach over MCP at https://api.limma.ai/mcp (or your own deployment's /mcp) with the X-API-Key header — no package needed. Documentation: https://docs.limma.ai.

Metadata

Release files for limma-ai 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for limma-ai 0.1.0
File Interpreter ABI Platform Actions
limma_ai-0.1.0-py3-none-any.whl Python 3 none any Details for limma_ai-0.1.0-py3-none-any.whl

Release files / limma_ai-0.1.0-py3-none-any.whl

Download URL limma_ai-0.1.0-py3-none-any.whl
Size 63.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b6cb4e35cc6665f03faeaf9e52a9a2d4eb55378589a265a916b78504fb511846
BLAKE2b-256 checksum
How to use checksums
b064eb2b1cba9c5db6da45b67b88872445266f2eae08d481c329301507f67b0d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.13

Security for limma-ai 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.

Release history Release notifications | RSS feed

This release

0.1.0 This release

1 release file No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page