ApiPi
Documentation: geki-ai.github.io/apipi
ApiPi is an open-source agent platform. Pi runs the agent loop. You host the gateway, keep control of the agents, and point them at your own LLM endpoints. Clients use an HTTP API compatible with the OpenAI Agents API.
Production sessions run in Firecracker microVMs. Each guest has its own kernel. The gateway stays on the host. Pi and the session files share the guest.
GEKI also runs a managed ApiPi on European infrastructure.
Quickstart
You need Python 3.13 and a model host URL. Live turns also need the Pi
CLI (pi --mode rpc) on PATH. The gateway pins Pi 0.85.1; apipi install puts that binary in a user-local prefix.
A single process stores data in SQLite at .apipi/apipi.db and binds
0.0.0.0:8000. OPENAI_BASE_URL on the gateway is the model host that
Pi calls. Clients send Authorization: Bearer; that value is the model
key unless you set OPENAI_API_KEY_OVERWRITE. Isolation defaults to
none (Pi as a child process). For production, set
APIPI_RUN_MODE=microvm. Several processes share Postgres.
From PyPI
pip install geki-apipi
apipi install
export OPENAI_BASE_URL=http://your-model-host/v1
apipi migrate
apipi serve
uv add geki-apipi works in a project. The import package and CLI are
apipi. S3-compatible artifact storage is pip install "geki-apipi[s3]".
From a git checkout
git clone https://github.com/GEKI-AI/apipi.git
cd apipi
uv sync
uv run apipi install
export OPENAI_BASE_URL=http://your-model-host/v1
uv run apipi migrate
uv run apipi serve
Prefix every apipi command with uv run in a checkout.
Client
In a second shell, point a client at http://localhost:8000/v1.
agent.model must exist on the model host. Install the openai
package yourself if you want the official client:
export OPENAI_API_KEY=dev-token
export OPENAI_BASE_URL=http://localhost:8000/v1
uv run --with openai python examples/openai_sdk.py
A full script is examples/openai_sdk.py. The stream stays open across idle, so that script stops after the first turn outcome. The same flow is on Using the API.
Production isolation:
APIPI_RUN_MODE=microvm apipi serve
More setup is on Install.
License
MIT. See LICENSE. Contributions: CONTRIBUTING.md.
Release files for geki-apipi 0.2.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 | |
|---|---|---|---|
| geki_apipi-0.2.0.tar.gz | 285.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| geki_apipi-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 381.2 kB
Release files / geki_apipi-0.2.0.tar.gz
| Download URL | geki_apipi-0.2.0.tar.gz |
|---|---|
| Size | 285.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7bcd431a36601b99f5c9d43cea0fe18d517072f95e895d978e85c854f2913843
|
|
BLAKE2b-256 checksum How to use checksums |
da08497a0b2c0360d8b1b6b653f2811067cf3cd5b82d09afd838498245ad54d2
|
| 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 Sep 15, 2026.
Transparency logRelease files / geki_apipi-0.2.0-py3-none-any.whl
| Download URL | geki_apipi-0.2.0-py3-none-any.whl |
|---|---|
| Size | 95.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d5b41f0cffa426a35b1b5a7fe97419efe3d6302040573f4525e0551773da8a8c
|
|
BLAKE2b-256 checksum How to use checksums |
b14a969c99c186bd050156824a486e9dc3a3fad7181ca0e04893ac35943ec830
|
| 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 Sep 15, 2026.
Transparency log