Skip to main content

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.
  • 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; the scrub action of FieldFilter.

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.

Metadata

Release files for oto-core 1.224.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.224.0
File Size Uploaded Provenance Actions
oto_core-1.224.0.tar.gz 1.5 MB With provenance Details for oto_core-1.224.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for oto-core 1.224.0
File Interpreter ABI Platform Actions
oto_core-1.224.0-py3-none-any.whl Python 3 none any Details for oto_core-1.224.0-py3-none-any.whl

Total release size: 3.2 MB

Release files / oto_core-1.224.0.tar.gz

Download URL oto_core-1.224.0.tar.gz
Size 1.5 MB
Tags Source
SHA-256 checksum
How to use checksums
2b20891ff41f3a2f7f2b1a29f2efa89032a0a19413d3141edb8146fec8774565
BLAKE2b-256 checksum
How to use checksums
82194e129472d932f7d75ba9b9dc601f8273a18d6eeb5bca5f52891481b26b5a
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 Nov 12, 2026.

Transparency log

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

Download URL oto_core-1.224.0-py3-none-any.whl
Size 1.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
2f1acd25c1b07cc347e3a60399d3d1ecff4183648f168972afc64c8fb8d5e81e
BLAKE2b-256 checksum
How to use checksums
9bc2d500daf97fbfa3a9ac066d0e055c3026ec85237b0830e7b5dd6b64de2ea5
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 Nov 12, 2026.

Transparency log

Security for oto-core 1.224.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.

Select from 2 files

Attestation for oto_core-1.224.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 Nov 12, 2026.

Transparency log

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

1.224.0 This release

2 release files Full 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