| Info: | Check Github for the latest source code and documentation for more information. |
|---|---|
| Maintainer: | Aito <admin@aito.ai> |
The Aito Python SDK is an open-source library that helps you to integrate your Python application to Aito quicker and more efficiently.
The SDK also includes the Aito Command Line Interface (CLI) that enables you to interact with Aito using commands in your command-line shell, e.g: infer a table schema from a file or upload a file to Aito.
Each Aito API version has its own package, whose meaning never changes:
from aito.v2 import Client # the v2 API (`from aito.v1 import Client` for v1) # the public read-only sandbox; use your own instance URL and key in production client = Client('https://shared.aito.ai/db/aito-demo', 'yg4rTlXkqDzm4y8gPeY75HCKaNwfbTQ2si64ONTi', env='v2') prediction = client.predict( from_table='invoices', where={'Description': 'cloud services'}, predict='GLCode') print(prediction.first.value, prediction.first.probability) # E002 0.83...
aito.Client is the default version, and moves only on a major release of this package:
since aitoai 1.0 it is the v2 client (0.x: v1). Quickstarts can use it; production code
should import the version it means, aito.v1 or aito.v2, so an upgrade cannot change
the API underneath it. To stay on v1: from aito.v1 import Client, or pin aitoai<1.
The pre-0.7 paths (aito.client, aito.client.v2, aito.api) were removed in 1.0;
importing one raises an ImportError naming its replacement. The command-line tool still
talks to the v1 API in 1.x: v2 support arrives as an opt-in in a 1.x minor release, and the
CLI's default moves to v2 only in 2.0. The design is written up in
docs/versioned-namespaces.md.
pip install aitoai installs the API clients. The command-line tool, schema inference
and file conversion need the dataframe toolchain: pip install 'aitoai[cli]'.
With Docker installed, aito start runs a local Aito and stores its keys, so the client
needs no arguments:
$ pip install aitoai $ aito start # pulls a pinned image, listens on http://127.0.0.1:9005, prints the keys $ python -c "import aito; print(aito.Client().get_schema())"
aito stop stops it (data and keys are kept), aito status checks it, aito keys
prints the keys again (--rotate replaces them), aito logs shows its log and
aito upgrade moves to the engine version this package pins. These work without the
[cli] extra. From Python, aito.Client() with no arguments uses AITO_URL and
AITO_API_KEY if set, else the local server's profile.
examples/v2_quickstart.py is a runnable end-to-end example that creates a collection,
loads it, predicts, explains, evaluates and drops it again.
pip install 'aitoai[mcp]' (Python 3.10+) adds aito-mcp, an MCP server for coding
agents and assistants. Its tools are predict, recommend, relate, match, search, query,
evaluate and schema/upload. Each tool's description says when Aito fits and when another
tool (a language model, a trained model, a search engine) is the better choice. Results
carry $p and a flattened $why. The server finds the instance the same way as
aito.Client(). It is read-only unless started with AITO_MCP_ALLOW_WRITES=1.
$ claude mcp add aito -- aito-mcp # Claude Code; any MCP client runs `aito-mcp` over stdio
Setup for Claude Code and other assistants: Use Aito from Claude Code and other AI assistants. When Aito fits and when not: When to use Aito, and when not.
claude-plugin/ is a Claude Code plugin with this server and a skill,
add-predictive-feature. The skill walks an agent through a fit check, a schema from
an existing table, a first prediction, a threshold chosen with _evaluate, and
act / assist / abstain wiring.
For issues with, questions about, or feedback, please join our support channels.
Aito Python SDK can be installed with pip
$ pip install aitoai
Check our installation guide for more information
You will need sphinx installed to generate the documentation.
$ pip install sphinx $ pip install sphinx_rtd_theme
Documentation can be generated by:
$ cd docs $ make clean html
Generated documentation can be found in the docs/build/html/* directory.
The Python SDK SQL integration and the tests depend on the ODBC db drivers and the postgres and mysql functionality.
The main drivers can be installed in Debian based Linuxes with:
`
sudo apt install unixodbc-dev odbc-postgresql postgresql-client default-mysql-client
pip install pyodbc
`
You can find more information about installing the MySQL ODBC drivers [here](https://dev.mysql.com/doc/connector-odbc/en/connector-odbc-installation.html)
Also note: that the database integration tests require local postgres / mySQL servers.
To run the test, you need to have the following environment variables defined:
- AITO_GROCERY_DEMO_INSTANCE_URL
- AITO_GROCERY_DEMO_API_KEY
- AITO_INSTANCE_URL
- AITO_API_KEY
Install the required packages:
$ pip install -r requirements/build.txt $ pip install -r requirements/test.txt
You can use our test cli to run tests:
$ python -m tests -h
Note
Some tests require some environment variables to be setup. Use the test CLI list command to discover and display the test suites and cases
There are multiple test suites:
- CLI suite:
$ python -m tests -v suite cliNote
You need an Aito instance and set up the credentials with
`AITO_INSTANCE_URL`and`AITO_API_KEY`to test some functions.
- SDK suite:
$ python -m tests -v suite sdkNote
You need an Aito instance and set up the credentials with
`AITO_INSTANCE_URL`and`AITO_API_KEY`to test some functions
- SQL functions tests:
Test against Postgres:
$ python -m tests -v case sql_functions.test_connection.TestPostgresConnection $ python -m tests -v case sql_functions.test_cli_sql_functions.TestPostgresFunctionsTest against MySQL:
$ python -m tests -v case sql_functions.test_connection.TestMySQLConnection $ python -m tests -v case sql_functions.test_cli_sql_functions.TestMySQLFunctionsNote
To test the SQL functions, you need to install pyodbc and the specific database ODBC driver.
- Build and test built package:
To build the package:
$ pip install -r requirements/deploy.txt $ ./scripts/deploy test.pypi --no-publish -b devWARNING: This will update the version in 'aito/__init__' file. DO NOT commit this to Git!
The built wheel should be at
`dist/`. To install:$ pip install dist/aitoai-<version>.whlTo test the built package, create an environment variable
`TEST_BUILT_PACKAGE`and run the above tests
- Test the documentation:
To test the inline documentation:
$ python -m tests -v suite inline_docsTo test the code blocks in rst files:
$ cd docs $ curl -o reddit_sample.csv https://raw.githubusercontent.com/AitoDotAI/kickstart/master/reddit_sample.csv $ export SPHINX_DISABLE_MOCK_REQUIREMENTS=TRUE $ make doctest
- Making changes
- Add unittest to the appropriate test suite (e.g: test case for Aito Schema: tests/sdk/test_aito_schema.py) or create a new test suite inside the tests folder
- Add documentation:
- Inline documentation if applicable
- Update .rst file in docs/source folder (e.g: Add a new Client function to docs/source/sdk.rst)
- Add inline doc test if applicable (e.g: inline doc test for Aito Client: tests/inline_docs/test_client_inline_docs.py)
Note
Remember to update the autodoc_mock_imports in conf.py file if there are additional requirements
- Update the version in aito/__init__ to e.g. '1.2.3rc1' and write release notes in docs/changelog.rst
- Check CircleCI and issue a PR
- Deploy to production (scripts/deploy) with the appropriate version after the PR is reviewed