Skip to main content

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.13.2.

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.13.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for agenthealth 0.13.2
File Size Uploaded
agenthealth-0.13.2.tar.gz 15.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for agenthealth 0.13.2
File Interpreter ABI Platform
agenthealth-0.13.2-py3-none-any.whl Python 3 none any Details

Total release size: 33.3 kB

Release files / agenthealth-0.13.2.tar.gz

Download URL agenthealth-0.13.2.tar.gz
Size 15.0 kB
Tags Source
SHA-256 checksum
How to use checksums
38ae0ec50ddf351191ba7b8ed4a506afdd9eff1f9154c54a30482644734abeaa
BLAKE2b-256 checksum
How to use checksums
d10505ff31429286bdde7441800ca643aef7631698db64403a48b7a490e852a9
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 14, 2026.

Transparency log

Release files / agenthealth-0.13.2-py3-none-any.whl

Download URL agenthealth-0.13.2-py3-none-any.whl
Size 18.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
28d8ea403a7bad3b91ce37717cd0a8665dc213a3140826e22d8fe3e7b5d7014d
BLAKE2b-256 checksum
How to use checksums
3e76037efc53bfac963645124e4b9685a3421523d020ace84b6d7709254f592b
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 14, 2026.

Transparency log

Release history Release notifications | RSS feed

0.14.0

2 release files

This release

0.13.2 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page