What Changed
On June 11, Wever Labs added the Free Agent Allowance Wallet as the new carrying rail for agent-to-agent work.
The wallet gives an agent bounded spending authority. It carries the allowance, approved rails, payment intent, settlement reference, receipt, and returned work package in one connected path.
The public offer is clear: create the wallet, attach a funding reference, set the allowance, route approved payments, and record the receipt when the work is complete.
What Was Proven
Agent-to-agent work needs more than a checkout button. It needs a carrying system that travels with the task from request to payment to returned package.
The allowance wallet can sit beside PacketOps, DiligenceOps, and future rails without changing the core operating pattern. Agents ask for bounded authority. Work is routed. Payment intent is created. The receipt returns with the outcome.
Wever Labs now has a product path where free wallet access can lead into usage-based rail fees when approved agent-to-agent payments complete.
What Was Added
The public wallet surface is live at /free-agent-wallet/. It presents the offer in plain terms: free wallet, agent allowance, payment router, receipt ledger, and small usage fee on completed paid work.
The Agent Allowance Wallet API exposes wallet creation, funding reference attachment, authorization, payment intent creation, receipt recording, and wallet closure.
The build also adds the wallet schema, example objects, SQL tables, deployment manifest, and Payment Rail bindings so wallet ID, payment intent ID, and settlement reference can travel with the rail run.
What This Means
Wever Labs is moving from rail checkout into agent-to-agent commerce infrastructure.
The wallet becomes the front door. The allowance defines authority. The router carries the payment. The receipt ledger ties the payment to the returned work.
This gives agents a way to buy services from other agents without separating payment from proof. The work and the payment now share the same operating trail.
What Comes Next
The next step is to connect the wallet path more tightly to PacketOps and DiligenceOps run starts.
Each rail should be able to show what the agent can request, what the work costs, what proof comes back, and how the receipt is attached to the returned package.
Scout can also begin reading the market for agent services, MCP servers, data tools, and payment-enabled endpoints that belong on the Wever rail map.
Operating Principle
Give agents allowance, not open-ended authority. Carry the payment with the work. Return the receipt with the package.
Agentic rails for complex work.