RoboSystems Python Client
Official Python client for the RoboSystems financial intelligence platform — accounting, financial reporting, and investment management over a knowledge graph API. Type-safe and async-ready, generated from the OpenAPI spec, with GraphQL reads and idempotent operation writes.
Features
- Type-safe API client with full type hints and typed models
- Async/await support for high-performance applications
- Parquet file uploads for table ingestion
- Streaming support for memory-efficient processing of large result sets
- Financial AI Agent integration for natural language queries
- Comprehensive error handling with typed exceptions
Installation
pip install robosystems-client
Versioning
This client is 1.x and follows semantic versioning, with one distinction worth knowing before you pin.
The stable surface is the facades (robosystems_client.clients), the root exports, the error classes, the auth configuration, and every symbol used by robosystems-integration-template — the emit path most integrations are built on. It is frozen for the life of 1.x; breaking any of it costs a major version.
The generated surface — the rest of robosystems_client.api.* and models.* — is regenerated from the platform's OpenAPI spec and tracks it. Operations there can be added, renamed, or removed on a minor release, and every such removal is named in that release's notes.
So robosystems-client>=1,<2 is the right pin if you build on the stable surface. If you depend on a generated operation outside it, either pin a minor range (>=1.7,<1.8) and read the release notes when you widen, or open an issue to have it promoted — the way something joins the stable surface is by being used in the integration template.
Resources
Support
License
This project is licensed under the MIT License - see the LICENSE file for details.
MIT © 2026 RFS LLC
1 maintainer
Release files for robosystems-client 1.13.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 | |
|---|---|---|---|
| robosystems_client-1.13.0.tar.gz | 557.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| robosystems_client-1.13.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.8 MB
Release files / robosystems_client-1.13.0.tar.gz
| Download URL | robosystems_client-1.13.0.tar.gz |
|---|---|
| Size | 557.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e02ab5bc29fc5edaba2eab7ee8f3ad55b9aebf4ed7c2bc2f1d3a62ee1da51947
|
|
BLAKE2b-256 checksum How to use checksums |
69e25117bf22308bd604f2990bc9e6862df5f4f8f4bbf0b7651fdcb1b433e5f0
|
| 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 Aug 29, 2026.
Transparency logRelease files / robosystems_client-1.13.0-py3-none-any.whl
| Download URL | robosystems_client-1.13.0-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d89a642480e1267a6458c0cf8a5117256359e5e1dde8988ace372c7affbbd34
|
|
BLAKE2b-256 checksum How to use checksums |
dfce43e04530f0e096730f7682d9663ac2d7ecfc907eb7295f7b08e370562884
|
| 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 Aug 29, 2026.
Transparency log
