Skip to content

Changelog

Agent SDK 0.1.6 · Provider SDKs 0.2.0

Any wallet. Cleaner records.

The Python agent SDK retires a session its provider or anyone else closed and funds a new one with the same signer, proves a provider's reported close when it next opens, retries a failed withdraw, idle release or close request, and opens in fewer chain round trips. The Python and Rust provider SDKs admit a session's waiting requests in the order they first waited, read the chain in one batched call per step, and hand each operation they no longer need to the wallet's optional retire, so wallet records stop growing. One set of wallet requirements now covers every wallet; Circle stays the recommended one. Both SDKs use protocol 0.1.4; upgrade a provider's mppi CLI and Python package together.

Agent SDK 0.1.5

Close a session, then start the next.

The Python agent SDK opens a new session after you close one: once your own close is confirmed, the next request or sessions.open funds a new session with the same signer, and the closed session's record stays beside the checkpoint. A close or exit that captured more than your recorded usage is never retired, so the discrepancy stays visible. An optional voucher headroom lets later requests start without waiting for a voucher round trip. A retried top-up first checks whether an earlier attempt already took effect, so it never funds twice. Onboarding now names a missing Circle CLI, an expired or wrong-network login and an unfunded wallet. The wire protocol, contract and signatures are unchanged, protocol package 0.1.3 stays the same, and providers stay on 0.1.2.

Agent SDK 0.1.4.1

New sessions stay ready.

A fix to the Python agent SDK 0.1.4. If the SDK's background chain check landed while your wallet was still signing and sending a session's opening, the next check could wrongly treat the new session as inconsistent. Requests were then refused until the provider next collected payment. The opening now records its time only from a block no later than its own. Nothing else changes: the wire protocol, payments and protocol package 0.1.3 stay the same, and providers stay on 0.1.2.

Agent SDK 0.1.4

Opens in seconds, from any wallet.

The Python agent SDK opens a session in a few chain lookups instead of about a hundred, proves each payment from the contract's own events, and serves requests without reading the chain. Any wallet provider fits behind the funding wallet interface: the SDK checks your agent ID and the signature as USDC will, not the wallet's version. A payment that never reached your wallet, or that definitely failed, is retried safely. The wire protocol and payments are unchanged, and providers stay on 0.1.2.

Agent SDK 0.1.3

Ready for many requests at once.

The Python agent SDK keeps every completed answer through dropped connections, rate limits and lagging RPC nodes. Requests keep running while a top-up confirms, the client reads the chain far less, and your funding code hears only about the shortfall it must cover. The wire protocol and payments are unchanged, and providers stay on 0.1.2.

SDKs 0.1.2

One wallet. Two networks.

Give your agent a Circle wallet and choose Arc mainnet or testnet. The Python agent SDK and Python and Rust provider SDKs now include both verified deployment profiles and use Circle Agent Wallet for onboarding and payments.

SDKs 0.1.1

A shorter path to your first exchange.

Start with the packaged Arc testnet profile. The agent loads its saved setup with Client.from_config. Providers generate their declarations and connect an onboarded configuration to the Python or Rust runtime.

MPPI 0.1.0

Inference payments, live on Arc testnet.

The first public release brings together the MPPI smart contract, Python agent SDK, Python and Rust provider SDKs, and shared protocol. Exchange inference through funded sessions, authorize usage as it unfolds and settle in USDC.