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.

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
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.

Metadata

Release files for oto-core 1.162.0

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.162.0
File	Size	Uploaded
oto_core-1.162.0.tar.gz	796.6 kB	Oct 8, 2026	Details

Built distribution (wheel)

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

Total release size: 1.8 MB

Release files / oto_core-1.162.0.tar.gz

Download URL	oto_core-1.162.0.tar.gz
Size	796.6 kB
Tags	Source
SHA-256 checksum How to use checksums	`497f59dd4cd6e38c08803c0677511e55a5356af457d2a335b6545cc11ef021f6`
BLAKE2b-256 checksum How to use checksums	`cdf359df6429df722c24c0265ffaa5546cdaa1a1cf82ed1dcc7a60432fa52bce`
Upload date	Oct 8, 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/afb961f2de104464d09a06f3d7652a6ebf134be4

Workflow

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

Artifact

Subject: oto_core-1.162.0.tar.gz
SHA-256 checksum: 497f59dd4cd6e38c08803c0677511e55a5356af457d2a335b6545cc11ef021f6 Verifying attestations

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

Download URL	oto_core-1.162.0-py3-none-any.whl
Size	976.3 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`78c5f857bf2458414d1d908526caa816f2d8b02685632961bcbc6fb4ed02f9a2`
BLAKE2b-256 checksum How to use checksums	`84b38a7695355506de034832192dedfb189d1173b7ba8f09a502db31ca7b2724`
Upload date	Oct 8, 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/afb961f2de104464d09a06f3d7652a6ebf134be4

Workflow

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

Artifact

Subject: oto_core-1.162.0-py3-none-any.whl
SHA-256 checksum: 78c5f857bf2458414d1d908526caa816f2d8b02685632961bcbc6fb4ed02f9a2 Verifying attestations