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, converting Python integer gas and nonce fields to JSON-RPC 0x quantities before submission. 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.3

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.3
File Size Uploaded
aegis_smart_accounts-0.1.3.tar.gz 10.7 kB Details

Built distribution (wheel)

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

Total release size: 22.0 kB

Release files / aegis_smart_accounts-0.1.3.tar.gz

Download URL aegis_smart_accounts-0.1.3.tar.gz
Size 10.7 kB
Tags Source
SHA-256 checksum
How to use checksums
5f833ace2f0c7545e295c23c73ae9104f241f92873aa8410d54eda8cb081540b
BLAKE2b-256 checksum
How to use checksums
339814fa9f8c111863be1d19403fd21bbe2d6d38151fbb77b365dbd8bce9039c
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.3-py3-none-any.whl

Download URL aegis_smart_accounts-0.1.3-py3-none-any.whl
Size 11.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8531aeefa722de71e2d611c42956135d966aaade73d90b7027862248556816de
BLAKE2b-256 checksum
How to use checksums
52db1473d6d24b13117eda196c2c40ff46cfed3288ec4b9bc19218c791b580fe
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

This release

0.1.3 This release

2 release files

0.1.2

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