WLFI (@worldlibertyfi): AgentPay SDK v0.2.1 is LIVE

AgentPay SDK v0.2.1 is LIVE The first release of AgentPay SDK gave agents a local, self-custodial runtime for wallet setup, policy-aware transfers, and human approvals. The new release extends that same runtime to paid HTTP flows with support for x402 and MPP, while also expanding EIP-3009 signing support and adding @tempo mainnet support. Your agent can now pay any x402 or MPP endpoint. Policy-checked, locally signed. One command. With x402, we now support: Exact-payment and EIP-3009 x402 HTTP payment flows Reusable HTTP request controls including --method, repeatable --header, --data, and --json-body And the flow is simple： Agent requests the resource and hits an API. API responds 402 with a price. AgentPay checks your spending policy, signs with EIP-3009 locally, retries with payment proof. API returns the data. One command. With MPP, we now support: MPP HTTP 402 payments on Tempo mainnet Tempo session flows including session open, voucher signing, optional --deposit, automatic top-up, and explicit close Added persisted session reuse via --session-state-file Decoded Payment-Receipt output plus JSON and NDJSON automation modes The flow expands into sessions: Session mode: open session, deposit funds, make multiple requests, close out when the work is done. Read more in our official Github AgentPay remains a local runtime for self-custodial, policy-aware wallet operations. The wallet stays under operator control. The approval path stays under operator control. The same local toolchain that already handled transfers now extends to x402 and MPP flows. Operators don’t have to choose between autonomy and oversight. They can let agents transact inside boundaries they define. This is the real shift in v0.2.0. Built for developers who want agent payments with operator control still intact. Before, AgentPay helped agents move money. Now it also helps them use money to unlock work: paid APIs, paid data, machine-to-machine services, and other HTTP-native flows that increasingly sit in the middle of agent execution. x402 and MPP are different payment paths, but the operator problem is the same: who signs, under what rules, and with what controls? AgentPay’s answer is a single local-first runtime with policy-aware execution. Agents pay. Your policies protect. That is what shipped in v0.2.0.