# Docs samples for Python SDK 4.0

> The Python samples in the Fusion docs use ipor-fusion 4.0, and agents can load the vault builder docs from one file.

Source: https://ipor.io/developer-news/website-2026-10-23  
Published: 2026-10-23  
Website

## New features

- The Python samples on the [SDK](https://ipor.io/docs/build-on-fusion/alpha/sdk.md), [Deploy your first Fusion vault](https://ipor.io/docs/build-on-fusion/developer-guide/deploy-your-first-fusion-vault.md), [Fusion for agents](https://ipor.io/docs/build-on-fusion/fusion-for-agents.md), [Common errors](https://ipor.io/docs/build-on-fusion/developer-guide/common-errors.md) and [Addresses](https://ipor.io/docs/build-on-fusion/developer-guide/addresses.md) pages use the ipor-fusion 4.0 API. They do not run on 3.x.
- The SDK page covers the address registry, calldata decoding, `preflight_execute` before signing, AccessManager timelocks with `read_call_plan` and market limits as `Wad` fractions. The CLI examples add `fusion vault preflight`, `fusion vault validate` and `fusion address`.
- The factory table on the Addresses page follows the SDK 4.0 deploy guide. It lists Flare, Monad, HyperEVM and Robinhood and has a column showing on which chains the SDK vault tooling runs.
- The revert table on Common errors adds `HandlerNotFound()` and shows how to check a missing role with `AccessManager.can_call`.
- A new file, [/docs/llms-fusion.txt](https://ipor.io/docs/llms-fusion.txt), holds the full text of the nine docs pages a vault builder needs, in the order of the deploy path. It is 62 KB, against 684 KB for `/docs/llms-full.txt`, for AI agents that load a single file.
- The SDK and Fusion for agents pages state that the cross-chain and HyperCore contracts are production. Their SDK API is still in preview and may change between minor versions.