oto-core
Repository: otomata-tech/connectors — renamed on 2026-09-14. The PyPI package keeps the name
oto-core, and so does the import namespaceoto.*.
Connector library for Oto — pure Python API clients for AI agents and automation. No command line, no server: clients return plain dicts.
Credentials are always provided by the consumer. Every client takes its secret (API key, token, OAuth credentials…) as a constructor argument; the library never reads secrets from the environment, files or a secret provider, and a missing one raises oto.tools.common.credentials.MissingCredential.
pip install oto-core # core (requests, france-opendata)
pip install "oto-core[google]" # + Google Workspace (Drive, Docs, Sheets, Gmail, Calendar, Tasks)
pip install "oto-core[browser]" # + browser-based scraping (LinkedIn, via o-browser)
pip install "oto-core[stock]" # + SIRENE stock queries (DuckDB/parquet)
What's inside
oto.tools.*— one client per service: French company data (SIRENE, INPI, BODACC, BOAMP, DVF via france-opendata), web search (Serper), email finding (Hunter), CRM (Attio, Folk), outreach (Lemlist, Kaspr, Fullenrich), Google Workspace, Slack, WhatsApp, Reddit, Pennylane, Silae (French payroll), and more.oto.tools.common.FieldFilter— reusable response redaction (mask IBANs, anonymize names, drop fields) any connector can apply; driven by code or afield_filters.<service>policy in~/.otomata/config.yaml.oto.tools.common.scrub— pseudonymises sensitive values written inside free text (social security numbers, IBANs, cards, e-mails, phones, secrets by their shape; names, addresses and credentials through an OpenAI-compatible model that only points at passages), each replaced by a stable keyed token; thescrubaction ofFieldFilter.
Shared connector descriptions
New shared connectors are described once, in YAML: connectors/<name>/connector.yaml, validated by connectors/connector.schema.json. A generator (the fabrique) turns each description into a Python client and TypeScript functions. Design docs (in French): docs/conception/README.md, description format, generator.
Ecosystem
| Package | Role |
|---|---|
| oto-core (this) | the clients — single source of truth |
@otomata_tech/connectors (npm, this repository) |
the shared connector definitions for TypeScript hosts, published with each tag at the library's version |
| oto-backend | hosted platform (mcp.oto.cx — MCP + REST, credential vault, orgs); pins a git version of this library |
| oto 2 npm package | upcoming consumer of the shared connectors, through the generator |
| bridge-boilerplate (private) | skeleton of a bridge: an internal HTTP micro-service the platform calls through its generic http connector, when the logic must be deterministic or a credential must stay out of the platform. Not a client — it does not live here |
from oto.tools.sirene import SireneClient
client = SireneClient(api_key="…") # the consumer passes the key
company = client.get_company("130025265")
Conventions: clients are import-lazy per optional dependency, raise on error (no silent fallbacks), and stay free of printing concerns.
MIT — © Otomata.
1 maintainer
Metadata
1 maintainer
Release files for oto-core 1.191.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 | |
|---|---|---|---|---|
| oto_core-1.191.0.tar.gz | 926.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| oto_core-1.191.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.1 MB
Release files / oto_core-1.191.0.tar.gz
| Download URL | oto_core-1.191.0.tar.gz |
|---|---|
| Size | 926.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5ad7260473c83c2fe4e47dbe83da7b1d3568319acb9baad574f4e680a233e5c6
|
|
BLAKE2b-256 checksum How to use checksums |
94b52a65444a6b38d794433387d111ed250fa14142ad68f813fdf8af198cf142
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 21, 2026.
Transparency logRelease files / oto_core-1.191.0-py3-none-any.whl
| Download URL | oto_core-1.191.0-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5b5c7178dd07828ee165a2e75e44f708e2e1b8e0a7eadd82cbd61ae7f6df9c16
|
|
BLAKE2b-256 checksum How to use checksums |
a45284c4e64b6796e5cf98aacdda2f9b4eccd1a1ba210eadcfb3d605c87eeed7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 21, 2026.
Transparency logSecurity for oto-core 1.191.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for oto_core-1.191.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 Oct 21, 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.
