aice-agent-platform
Python SDK for the Agent Platform the config-driven LangGraph agent runtime exposed over Aegra's Agent Protocol.
This SDK is a composition of two surfaces:
- AICE-specific management routes (
agents,skills,usage,suggestions) go throughaice-core's shared transport, so they get the usual typedAiceErrorhierarchy, retries, and idempotency-key handling. - The native LangGraph surface (
threads,runs,assistants,crons) this service is a LangGraph Platform-compatible deployment, so this SDK composes the officiallanggraph-sdkdirectly rather than re-implementing it. This is where streaming/run execution lives.
These two surfaces do not share error types or retry behavior.
client.threads/client.runs/client.assistants/client.crons raise
whatever langgraph-sdk itself raises, with its own retry policy never
aice_core.AiceError. client.agents/client.skills/client.usage/
client.suggestions behave like every other AICE SDK. See the docstring at
the top of client.py for the full rationale.
from aice_agent_platform import AgentPlatformClient
client = AgentPlatformClient(base_url="https://agents.example.com", api_key="sk-…")
# ── AICE-specific management routes ────────────────────────────────────
# List available agents
agents = client.agents.list()
# Publish a saved agent definition so it's runnable
client.agents.publish("ag_123")
# Discover skills
skills = client.skills.list()
# Fetch usage counters for the current project
usage = client.usage.get()
# Trigger the post-turn suggestion engine for a thread
suggestions = client.suggestions.create_for_thread("th_123")
# ── Native LangGraph surface (streaming, threads, runs) ────────────────
thread = client.threads.create()
for chunk in client.runs.stream(
thread["thread_id"],
assistant_id="agent",
input={"messages": [{"role": "user", "content": "hi"}]},
):
print(chunk.event, chunk.data)
Async variant mirrors this with AsyncAgentPlatformClient and await/
async for.
See the upstream service's own
docs/API.md for the
AICE-specific endpoint spec this SDK tracks, and the
LangGraph SDK reference
for the native threads/runs/assistants/crons surface.
Metadata
Release files for aice-agent-platform 0.2.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 | |
|---|---|---|---|---|
| aice_agent_platform-0.2.1.tar.gz | 7.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aice_agent_platform-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.6 kB
Release files / aice_agent_platform-0.2.1.tar.gz
| Download URL | aice_agent_platform-0.2.1.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e29d372813e851ec2f1a76e640dcf71c0af1bfbbd8ede00196bdcf8c3dd133de
|
|
BLAKE2b-256 checksum How to use checksums |
7542185238ac648cf849bf62f32d50b6d2bdde687033172da538d05f9f6795ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.24
|
Release files / aice_agent_platform-0.2.1-py3-none-any.whl
| Download URL | aice_agent_platform-0.2.1-py3-none-any.whl |
|---|---|
| Size | 5.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf58ca2a421050d99d62bf912fd234f82c0d317ec1fdb968e941d95f06e3dd63
|
|
BLAKE2b-256 checksum How to use checksums |
2c76a8035a9959232358265fccbadc073514169373810999c51dd4e2bd6b43b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.24
|
Security for aice-agent-platform 0.2.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.