AgentHealth Python SDK
Typed synchronous and asynchronous access to AgentHealth's Go CLI. This package preserves AHS v1 results, diagnostic codes, dependency relationships and graph IDs. Health failures return results; tool failures raise exceptions.
Install the package with pip install agenthealth once published. Install a
verified AgentHealth CLI of the same software version separately and put it on
PATH, or pass its absolute path. Installation and imports never download or
execute a binary. This first SDK targets Python 3.10+ and CLI v0.14.0.
from agenthealth import Client, HealthStatus
client = Client(binary="/usr/local/bin/agenthealth", timeout=30)
report = client.check(target_type="http", endpoint="http://localhost:8080/health")
print(report.status, report.exit_code)
if report.status == HealthStatus.HEALTHY:
print(report.result.target.name)
from agenthealth import async_check
async def probe():
return await async_check("agenthealth.yaml")
Use Configuration for Python dictionaries or load_config for JSON/YAML.
The same configuration supports all implemented CLI adapters, explicit active
checks, nested dependencies and graph references. Credentials stay in configured
references. Configuration is trusted executable input: MCP stdio can launch
programs and endpoints can reach private networks. Loading validates schema;
Go validates graph semantics at execution.
The SDK checks the exact CLI version, bounds configuration and output, enforces an overall deadline and stops checks on timeout/cancellation. POSIX checks use a dedicated process group to clean up descendants. On Windows termination covers the CLI process; detached stdio descendants require operator lifecycle controls. CLI stderr is never included in exceptions.
The SDK does not aggregate health independently, run OAuth login, register
Python adapters, or auto-install the CLI. report.results preserves ordered
roots, including each dependency projection. to_dict() preserves additional
result fields. Relative paths retain the caller's working directory, matching
the CLI; Configuration(data, base_dir=...) selects a different directory.
Source implementation is pre-1.0; PyPI availability is recorded separately in the repository capability status. See the repository's Python SDK guide for installation, release setup, errors and examples.
Metadata
Release files for agenthealth 0.14.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 | |
|---|---|---|---|
| agenthealth-0.14.0.tar.gz | 15.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agenthealth-0.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 33.3 kB
Release files / agenthealth-0.14.0.tar.gz
| Download URL | agenthealth-0.14.0.tar.gz |
|---|---|
| Size | 15.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
63ddfd1ab70c22d25708ae73fd1d7af1522e2b6fc7124bef737df107d9ab23b3
|
|
BLAKE2b-256 checksum How to use checksums |
72623dd77b9553fff3765021f87d94f94d6a2097d69ac7d6ca7de3c6bc068b2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 15, 2026.
Transparency logRelease files / agenthealth-0.14.0-py3-none-any.whl
| Download URL | agenthealth-0.14.0-py3-none-any.whl |
|---|---|
| Size | 18.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
44f2c16bd7fd989ee0564035c96f082fc3bc2d5fa882cc4fa6029197219dfdf3
|
|
BLAKE2b-256 checksum How to use checksums |
7ec3e68b346d001f81ade0ccfff70262d4a9ac85dc900cc9138a40a5f20828d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Oct 15, 2026.
Transparency log