Skip to main content

Aegis Python SDK

The released SDK is published as aegis-smart-accounts. It requires Python 3.10 or newer. Install it in an isolated environment:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install aegis-smart-accounts

For repository development instead, use python -m pip install -e sdk/python.

The SDK never stores a private key. aegis init records only public identifiers and addresses in a mode-0600 state file so an interrupted setup can resume.

export AEGIS_API_KEY=aegis_...
aegis init --name my-agent --owner 0x... --signer 0x... \
  --chain-id 11155111 --policy-file /path/to/policy.json
aegis doctor AGENT_UUID --permission-id PERMISSION_UUID --asset native
# Equivalent flag form:
aegis doctor --agent-id AGENT_UUID --permission-id PERMISSION_UUID --asset native

A minimal Sepolia policy example is available in the repository at examples/minimal-sepolia-policy.json. Use an explicit policy file that matches the account and chain you intend to operate on.

Use permission_calldata(permission_id, calldata) to create the exact Aegis permission envelope. Never select a permission by “newest”; pass the permission UUID or on-chain bytes32 ID explicitly and run doctor immediately before use.

build_execute and build_execute_batch encode policy-only account calls. estimate_userop preserves the bundler's raw RpcError.data for diagnosis and fails before RPC when the UserOperation has no signature; sign_userop uses the EIP-191 encoding expected by the account; and submit_userop sends the fully estimated and signed v0.6 operation. This prevents an unsigned simulation from being misreported as an AA21 prefund failure. Use wait_for_userop_receipt after submission. It reads the mined transaction hash from the nested receipt.transactionHash field and exposes it as tx_hash; the top-level userOpHash is not an EVM transaction hash.

When checking an intended token, pass --asset <address> (or native) to Doctor. Doctor's normal asset rows describe the permission's configured asset list; an account holding a token does not by itself mean that token is allowed by the permission.

Release files for aegis-smart-accounts 0.1.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 aegis-smart-accounts 0.1.2
File Size Uploaded
aegis_smart_accounts-0.1.2.tar.gz 10.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for aegis-smart-accounts 0.1.2
File Interpreter ABI Platform
aegis_smart_accounts-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 20.8 kB

Release files / aegis_smart_accounts-0.1.2.tar.gz

Download URL aegis_smart_accounts-0.1.2.tar.gz
Size 10.0 kB
Tags Source
SHA-256 checksum
How to use checksums
498c9ea4666bd6fd5ffa479a6e2dbfc4e9b5cdc9df9d83fbc95031ec2d658f28
BLAKE2b-256 checksum
How to use checksums
83a10f536e720486135654d939b5ada3ef8c76989bafa43dde5f374afa95c9b9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 1, 2026.

Transparency log

Release files / aegis_smart_accounts-0.1.2-py3-none-any.whl

Download URL aegis_smart_accounts-0.1.2-py3-none-any.whl
Size 10.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d956d9f6ed64c0cbb6c1b8ada41a59c5d9542f4c1bb171be8dba548e355c7037
BLAKE2b-256 checksum
How to use checksums
17c8f6da83a51d5644bfaa7c4b7d57b6e43dab1e66d672933c9b5ae3707920bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Aug 1, 2026.

Transparency log

Release history Release notifications | RSS feed

0.5.0

2 release files

0.4.0

2 release files

0.2.0

2 release files

0.1.3

2 release files

This release

0.1.2 This release

2 release files

0.1.0

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