agi-diy
Python client for api.agi.diy. Lease a VLA policy, run it over the LeRobot remote-inference protocol (zenoh). One call = one token per action in the chunk.
pip install agi-diy "lerobot[remote] @ git+https://github.com/huggingface/lerobot"
agi login
agi run act/so101 --probe
import agi
with agi.Policy("act/so101") as session:
actions = session.predict(
{"observation.state": state, "observation.images.top": top, "observation.images.wrist": wrist},
task="pick up the cube",
) # np.ndarray [n_action_steps, dof]
The key comes from AGI_API_KEY or ~/.agi/credentials (AGI_API_KEY=agi_sk_live_…).
Surface
agi.Policy("act/so101") # POST /v1/sessions → lease; raises agi.NoSlots / agi.InsufficientCredits / agi.AuthError
session.endpoint # "tcp/bore.pub:35706" (verbatim from the runner; session.encoding = "jpeg")
session.deployment # "d_…"
session.url # "zenoh://bore.pub:35706/d_…" → strands_robots.Policy(session.url)
session.connect() # admitted lerobot.remote_inference.RemoteClient
session.predict(obs, task="…") # one chunk, np.ndarray
session.policy() # strands-robots policy: arm.run(session.policy(), seconds=30)
session.rollout_args() # flags for lerobot-rollout
session.close() # DELETE /v1/sessions/:id (also a context manager)
agi.models(); agi.me(); agi.usage(); agi.sessions(); agi.health()
CLI: agi login · agi models · agi session act/so101 · agi run act/so101 --probe ·
agi rollout act/so101 -- --robot.type=so101_follower … · agi usage.
connect(), predict() and rollout need LeRobot's remote inference, which is on lerobot main only today
(pip install "lerobot[remote] @ git+https://github.com/huggingface/lerobot"). The REST part has no dependencies.
Errors subclass agi.Error with .error, .status, .retry_after_s.
Metadata
Release files for agi-diy 0.1.1
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 | |
|---|---|---|---|---|
| agi_diy-0.1.1.tar.gz | 14.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agi_diy-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.2 kB
Release files / agi_diy-0.1.1.tar.gz
| Download URL | agi_diy-0.1.1.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5dc00e679d6e51e6283181b8da17d7b02db930be31b1ea1ed11cf81a38a6da5c
|
|
BLAKE2b-256 checksum How to use checksums |
4b68ec2c8cd3a859cd8a6224e80ae386a11e1eee42906e1a81306cbfb83e6850
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / agi_diy-0.1.1-py3-none-any.whl
| Download URL | agi_diy-0.1.1-py3-none-any.whl |
|---|---|
| Size | 11.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
236b324e7c512739dc874b2f9d9b8b5104a6f90381ca1763bb08818bb4ec5883
|
|
BLAKE2b-256 checksum How to use checksums |
490d60c6f5ca61f7eb7ab8ad43c0ebbd4a7399f66f40ba2a20014fea708e89f7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for agi-diy 0.1.1
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.