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.

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
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.157.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.157.0
File Size Uploaded
oto_core-1.157.0.tar.gz 753.8 kB Details

Built distribution (wheel)

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

Total release size: 1.7 MB

Release files / oto_core-1.157.0.tar.gz

Download URL oto_core-1.157.0.tar.gz
Size 753.8 kB
Tags Source
SHA-256 checksum
How to use checksums
e6e180e0c3c35e1988cb9352dd2a67dfa8061f3abd80d1248116c1eea07a61ab
BLAKE2b-256 checksum
How to use checksums
f3a7c8e06a906835d1828964ea6b897ba039147af2fbfb39b59edaf21fe42747
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 7, 2026.

Transparency log

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

Download URL oto_core-1.157.0-py3-none-any.whl
Size 919.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0cb6f580d9f5a779a6134ad872a7ce6ace197737531c3405e9e7174bf365fe87
BLAKE2b-256 checksum
How to use checksums
dc22030be548822a8e4b67c65e6ffcb88dc832aa2cca3f7d0da07aad0246fd6f
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 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.157.0 This release

2 release files

1.85.0

2 release files

1.84.0

2 release files

1.57.0

2 release files

1.10.7

2 release files

1.10.6

2 release files

1.10.5

2 release files

1.8.0

2 release files

1.6.0

2 release files

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