oto-core

Repository: otomata-tech/connectors — renamed on 2026-09-14. The PyPI package keeps the name oto-core, and so does the import namespace oto.*.

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 a field_filters.<service> policy in ~/.otomata/config.yaml.

Ecosystem

Package	Role
oto-core (this)	the clients — single source of truth
oto-backend	hosted platform (mcp.oto.cx — MCP + REST, credential vault, orgs)

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.

Metadata

Release files for oto-core 1.151.1

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

Source distribution (sdist)

Source distribution for oto-core 1.151.1
File	Size	Uploaded
oto_core-1.151.1.tar.gz	709.1 kB	Oct 1, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for oto-core 1.151.1
File	Interpreter	ABI	Platform	Reset
oto_core-1.151.1-py3-none-any.whl 856.0 kB Oct 1, 2026	Python 3	none	any	Details

Total release size: 1.6 MB

Release files / oto_core-1.151.1.tar.gz

Download URL	oto_core-1.151.1.tar.gz
Size	709.1 kB
Tags	Source
SHA-256 checksum How to use checksums	`a0f14a9d670583c3fec517cc70dc8ba4ef67b5f48cfcedc8944b4cf17268ca06`
BLAKE2b-256 checksum How to use checksums	`7255f7670feabc98fd97c183308510a6c6197c78fe2c39ada98f6ef1f943762c`
Upload date	Oct 1, 2026
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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/otomata-tech/connectors
Publishing commit: github.com/otomata-tech/connectors/tree/6a592ad9b15c6a89eb46afd3af381e9acdf2b8ec

Workflow

Publishing configuration: github.com/otomata-tech/connectors/blob/6a592ad9b15c6a89eb46afd3af381e9acdf2b8ec/.github/workflows/publish.yml
Publishing logs: github.com/otomata-tech/connectors/actions/runs/36870149884/attempts/1

Artifact

Subject: oto_core-1.151.1.tar.gz
SHA-256 checksum: a0f14a9d670583c3fec517cc70dc8ba4ef67b5f48cfcedc8944b4cf17268ca06 Verifying attestations

Release files / oto_core-1.151.1-py3-none-any.whl

Download URL	oto_core-1.151.1-py3-none-any.whl
Size	856.0 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`7f49800398e6b5e5f6bec70a8ce10e854657785c54c23c3b3030b0607695ecd7`
BLAKE2b-256 checksum How to use checksums	`7bb8b4e24deb823d0cb2cc8fbb7678ddacf728f2aa578623ddc82e9b3f5d8f17`
Upload date	Oct 1, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/otomata-tech/connectors
Publishing commit: github.com/otomata-tech/connectors/tree/6a592ad9b15c6a89eb46afd3af381e9acdf2b8ec

Workflow

Publishing configuration: github.com/otomata-tech/connectors/blob/6a592ad9b15c6a89eb46afd3af381e9acdf2b8ec/.github/workflows/publish.yml
Publishing logs: github.com/otomata-tech/connectors/actions/runs/36870149884/attempts/1

Artifact

Subject: oto_core-1.151.1-py3-none-any.whl
SHA-256 checksum: 7f49800398e6b5e5f6bec70a8ce10e854657785c54c23c3b3030b0607695ecd7 Verifying attestations