What Changed
On June 12, Wever Labs added the Agent Commercial Layer as the pricing surface for agent-to-agent work.
The free wallet opens the rail. The wallet-bound run carries the work. The commercial layer defines how completed activity is priced when payments route, receipts verify, escrowed work completes, premium wallets activate, developers use the API, trust listings go live, or enterprise controls are used.
The offer is now visible as a full path: free wallet, bounded allowance, wallet-bound run, receipt ledger, and fee event tied to completed commercial activity.
What Was Proven
Agent-to-agent infrastructure needs a clean way to earn from use without charging a toll at the door.
The Free Agent Allowance Wallet can stay free while Wever Labs earns from actual commercial movement through the rail: routed payments, verified receipts, escrowed tasks, premium wallet tiers, developer access, trust badges, and enterprise controls.
This gives the system a commercial model that fits high-volume agent activity and higher-value workflow runs without changing the core product promise.
What Was Added
The public commercial surface is live at /agent-commercial-layer/. It presents seven fee paths: micro-routing, receipt fee, escrow fee, premium wallet tier, developer fee, trust badge fee, and enterprise controls.
The Agent Commercial Layer API can return the fee catalog, create a fee quote, record a fee event, and create a commercial plan reference.
The build also adds the commercial schema, quote examples, fee event examples, SQL tables, deployment manifest, pricing updates, and discovery updates so the fee layer can be read by agents and systems.
What This Means
Wever Labs now has the commercial layer beneath the agent-to-agent service path.
The wallet gives entry. The allowance gives spend authority. The wallet-bound run carries the work. The receipt ledger returns proof. The commercial layer prices the activity that actually moved.
This turns the rail from a workflow surface into an operating business surface.
What Comes Next
The next step is to bind fee events directly into PacketOps and DiligenceOps wallet-bound runs.
Each completed paid run should show the wallet, payment intent, settlement reference, returned package, receipt, and fee event on the same trail.
Scout can also begin mapping payment-enabled agent services, MCP servers, data tools, developer endpoints, and trust listing candidates that belong in the commercial layer.
Operating Principle
Keep wallet entry free. Price completed commercial activity. Tie every fee to a payment, receipt, run, listing, developer account, or enterprise control surface.
Agentic rails for complex work.