About datarobot
DataRobot is a client library for working with the DataRobot platform API.
This package is released under the terms of the DataRobot Tool and Utility Agreement, which can be found on our Legal page, along with our privacy policy and more.
Installation
Python >= 3.7 are supported. You must have a datarobot account.
$ pip install datarobot
Usage
The library will look for a config file ~/.config/datarobot/drconfig.yaml by default. This is an example of what that config file should look like.
token: your_token endpoint: https://app.datarobot.com/api/v2
Alternatively a global client can be set in the code.
import datarobot as dr dr.Client(token='your_token', endpoint='https://app.datarobot.com/api/v2')
Alternatively environment variables can be used.
export DATAROBOT_API_TOKEN='your_token' export DATAROBOT_ENDPOINT='https://app.datarobot.com/api/v2'
Extra
datarobot has the following optional groups:
- application-utils (requires Python 3.11+): Light async ORM over the
DataRobot Agentic Memory Service, plus an AG-UI chat-history layer (models, repositories, and AG-UI event storage). This can be used in DataRobot Custom Applications and Agent Workflows.
- auth (requires Python 3.9+): Provides an abstraction to handle OAuth2 authentication with DataRobot API (11.1+).
This can be used in DataRobot Custom Applications and on its own.
- auth-authlib (requires Python 3.9+): OAuth2 authentication handling via Authlib.
This can be used in DataRobot Custom Applications and on its own.
- core (requires Python 3.8+): Platform library functions to improve building with DataRobot.
This can be used in DataRobot Custom Applications, Custom Models, and Agent Workflows.
fs (requires Python 3.9+): Provides file system implementation to work with the DataRobot file system.
- pipelines (requires Python 3.10+): Adds the runtime needed to author pipelines locally
(the dr.task / dr.pipeline decorators and dr.CloudExecutor). The pipelines REST surface (dr.Pipelines, dr.Pipeline, dr.PipelineImage, …) is in the base install and needs no extra.
- query-engine (requires Python 3.9+): Engine to run SQLAlchemy-compatible queries against DataRobot data stores
and JDBC connections.
You can install these optional groups by specifying them in the pip command, for example:
$ pip install datarobot[auth]
Helpful links
Bug Reporting and Q&A
To report issues or ask questions, send email to the team.
Metadata
Release files for datarobot 3.20.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 | Provenance | Actions |
|---|---|---|---|---|
| datarobot-3.20.0.tar.gz | 1.1 MB | Without provenance | Details for datarobot-3.20.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datarobot-3.20.0-py3-none-any.whl | Python 3 | none | any | Details for datarobot-3.20.0-py3-none-any.whl |
Total release size: 2.4 MB
Release files / datarobot-3.20.0.tar.gz
| Download URL | datarobot-3.20.0.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16e5e07df9737d73735fbbf1a7fce11bfea17f0ab8e479c8a1ec9ed0abd8d75b
|
|
BLAKE2b-256 checksum How to use checksums |
6288d7cf451a28196f5068a82d5cf98aceae8a53ee52789ddc337315d6b3a957
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / datarobot-3.20.0-py3-none-any.whl
| Download URL | datarobot-3.20.0-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e2478c9cc847364da24965c36f41bbbb02b3d884228f69fdf6f61ea125c980e3
|
|
BLAKE2b-256 checksum How to use checksums |
0ed8a225a2146decea612f902ed265e74df3b072dab4fdc058f5a25756702c73
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for datarobot 3.20.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.