ACE-X Client
Synchronous Python client for the ACE-X backend.
Installation
pip install acex-client
Quick start
from acex_client import Acex
with Acex(base_url="https://acex.local") as client:
result = client.inventory.sites.query(name="stockholm")
for site in result:
print(site.id, site.name)
Auth is auto-detected from /auth/config. Override via env vars:
ACEX_BASE_URL— backend URLACEX_ISSUER_URL,ACEX_CLIENT_ID,ACEX_CLIENT_SECRET— OIDC overrideACEX_VERIFY_SSL=false— disable TLS verification
or inject an AuthProvider directly:
from acex_client.auth import ClientCredentialsAuth
auth = ClientCredentialsAuth(client_id="...", client_secret="...", issuer_url="...", verify_ssl=True)
with Acex(base_url="...", auth=auth) as client:
...
Namespaces
| Namespace | Resources / actions |
|---|---|
client.inventory |
sites, regions, region_assignments, contacts, contact_assignments, assets, asset_clusters, collection_agents, credentials, logical_nodes, management_connections, node_instances, node_credentials(node_id), site_credentials(site_name) |
client.observability |
agents (with bound outputs, rules, nodes), grafana |
client.operations |
config_history.list_changes(), lldp (.upload(), .topology(), .by_site(), .get(), .reverse()) |
client.config_components |
catalog(), generate(), reconcile(), drivers(), translate() |
client.neds |
list(), get(), download() |
client.ai |
ask(), analyze() (SSE-streamed) — None if backend has no ai_ops mounted |
client.compliance |
overview(), node(), site(), region() |
client.policies |
software (.query(), .get(), .create(), .update(), .delete()) |
client.system |
auth_config() |
CRUD pattern
Each resource inherits the mixins for the verbs it supports. All mutations
return a LiveInstance proxy that holds the Pydantic model; .save() diffs
against the original and PATCHes only changed fields, .delete() removes
the resource:
site = client.inventory.sites.create(name="stockholm", city="SE")
site.display_name = "Stockholm HQ"
site.save() # PATCH /inventory/sites/{id} with {display_name: ...}
site.delete() # DELETE /inventory/sites/{id}
get, update, create, delete all raise AcexNotFoundError on HTTP 404
rather than returning None — wrap in try/except for "if exists" flows.
Actions and sub-resources
Action methods use @action(method, path_template):
client.inventory.collection_agents.manifest(id=1)
client.inventory.collection_agents.ack(id=1, payload=CollectionAgentAck(config_revision=5))
CVE payload models format their date fields as ISO 8601 strings when dumped, so they work with the standard client actions without custom request handling.
Bound sub-resources are accessed via .parent_or_id:
client.inventory.collection_agents.rules(1).create(region="eu")
Via a LiveInstance, the bound sub-resource is exposed as an attribute:
agent = client.observability.agents.get(1)
agent.rules.create(region="eu")
Errors
from acex_client import (
AcexNotFoundError,
AcexValidationError,
AcexAuthError,
AcexPermissionError,
AcexServerError,
AcexTimeoutError,
AcexConnectionError,
)
All errors inherit from AcexError. HTTP errors carry status_code and
body attributes.
Examples
See examples/crud.py and examples/observe.py.
Metadata
Release files for acex-client 4.13.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 | Provenance | Actions |
|---|---|---|---|---|
| acex_client-4.13.0.tar.gz | 35.1 kB | With provenance | Details for acex_client-4.13.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| acex_client-4.13.0-py3-none-any.whl | Python 3 | none | any | Details for acex_client-4.13.0-py3-none-any.whl |
Total release size: 87.7 kB
Release files / acex_client-4.13.0.tar.gz
| Download URL | acex_client-4.13.0.tar.gz |
|---|---|
| Size | 35.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
328b188b0158259568861e76a96ed50e01aac4b24a5b5ab174bee16bb6fc2817
|
|
BLAKE2b-256 checksum How to use checksums |
c00127a1f2bf4c38738e95b995acd5cd290a40e64b75360969ab0c93c503a8ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logRelease files / acex_client-4.13.0-py3-none-any.whl
| Download URL | acex_client-4.13.0-py3-none-any.whl |
|---|---|
| Size | 52.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94905be9fd63c62187afd341cbff4fb8be2b796e9ece105edac240b4f59dc187
|
|
BLAKE2b-256 checksum How to use checksums |
458e07f327a5a6683351a424d3e37d7aaac484326f67ee702b2621ea78a0da90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 12, 2026.
Transparency logSecurity for acex-client 4.13.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for acex_client-4.13.0.tar.gz
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 Nov 12, 2026.
Transparency logA 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.