World Liberty Monetary ($WLFI) has launched AgentPay SDK v0.2.1, an replace that extends its open-source AI agent fee toolkit to help x402 and MPP (Machine Cost Protocol) HTTP fee flows, whereas additionally increasing EIP-3009 signing help and including Tempo mainnet compatibility.
What Is AgentPay SDK?
Consider AgentPay SDK as a pockets and fee system constructed particularly for AI brokers, not people.
When an AI agent is operating a activity, it usually must pay for issues alongside the way in which: pulling information from a paid API, accessing a service, or finishing a machine-to-machine transaction. With no purpose-built fee layer, that agent both cannot do the job or has handy off management to an outdoor system to deal with the cash.
AgentPay solves that. It provides the agent its personal pockets, a set of spending guidelines outlined by the operator, and the flexibility to signal and ship funds regionally with out contacting $WLFI or any third celebration. The agent can spend, however solely throughout the boundaries the operator units.
SDK stands for Software program Improvement Equipment, which is basically a packaged set of instruments builders use to construct or prolong software program. On this case, the equipment features a command-line interface (CLI), an area signing daemon, a coverage engine, and a talent pack that connects the pockets to agent hosts like Claude Code, Codex, and OpenClaw.
What Modified In AgentPay SDK v0.2.1?
The unique AgentPay SDK, launched round March 21, gave AI brokers an area, self-custodial runtime for pockets setup, policy-based transfers, and human approval checkpoints. Model 0.2.1 builds on that basis by letting brokers pay for API entry and HTTP-native companies straight, with out handing management away from the operator.
All transactions settle in $USD1, $WLFI‘s dollar-pegged stablecoin, which has roughly $4.4 billion in circulation based on DefiLlama.
What x402 Help Provides
The x402 circulate handles HTTP 402 fee responses, an ordinary the place an API alerts {that a} useful resource requires fee earlier than entry is granted. With v0.2.1, AgentPay helps:
- Precise-payment and EIP-3009 x402 HTTP fee flows
- Reusable HTTP request controls together with –method, repeatable –header, –data, and –json-body
The circulate works like this: the agent requests a useful resource, the API responds with a 402 standing and a worth, AgentPay checks the operator’s spending coverage, indicators regionally utilizing EIP-3009, and retries with fee proof connected. The API then returns the information.
What MPP Help Provides
MPP (Machine Cost Protocol) introduces session-based funds on Tempo mainnet. As a substitute of paying per request, an agent can open a session, deposit funds, make a number of requests, and shut out when the job is completed.
New MPP options in v0.2.1 embrace:
- MPP HTTP 402 funds on Tempo mainnet
- Tempo session flows with session open, voucher signing, non-compulsory –deposit, computerized top-up, and express shut
- Endured session reuse by way of –session-state-file
- Decoded Cost-Receipt output plus JSON and NDJSON automation modes
How Does AgentPay Preserve Operator Management Intact?
That is the core design query the SDK is constructed round. Each transaction, whether or not a easy switch or a paid API name, runs via the identical native coverage engine earlier than any signing takes place. There is no such thing as a code path that bypasses coverage enforcement.
The structure spans 4 layers: a command-line interface (CLI), an area signing daemon, a coverage engine, and a talent pack for integration with agent hosts like Claude Code, Codex, and OpenClaw. Non-public keys by no means go away the operator’s machine. $WLFI doesn’t custody belongings, entry keys, or course of funds.
When a transaction exceeds a preset threshold, the SDK pauses and requires human approval. If a pockets runs low on funds, the system halts the operation and returns an error with the pockets handle, chain ID, and a QR code for replenishment.
The SDK fees no platform charges. Solely customary blockchain fuel charges apply. It’s launched underneath the MIT licence with no telemetry or auto-update mechanisms.
Who Is AgentPay SDK v0.2.1 Constructed For?
AgentPay targets builders constructing autonomous brokers that must pay for companies throughout execution, akin to paid APIs, information feeds, or machine-to-machine companies, whereas holding a human operator accountable for how and when cash strikes. The macOS-first setup integrates with macOS Keychain and runs a root-managed LaunchDaemon regionally.
Conclusion
AgentPay SDK v0.2.1 does one factor the unique launch couldn’t: it lets AI brokers pay for work in actual time, mid-task, with out the operator shedding management of how that cash strikes.
The addition of x402 and MPP help means brokers can now entry paid APIs, information feeds, and HTTP-native companies as a part of their regular execution circulate. Periods will be opened, funded, used throughout a number of requests, and closed out, all inside coverage limits the operator defines upfront.
The core design has not modified. Keys keep native. Signing stays native. $WLFI has no entry to wallets or funds. The one factor that has expanded is what the agent can do inside that managed atmosphere.
For builders constructing autonomous brokers that work together with paid companies, v0.2.1 closes a sensible hole that the primary launch left open.
-
World LibertyFi on X: Put up on March 31
-
World LibertyFi docs: About AgentPay SDK
-
Report by The Defiant: World Liberty Monetary Launches Toolkit to Let AI Brokers Spend $USD1
