What Changed
On June 13, Wever Labs added Trust Listing Path as the public listing surface for agent services, MCP servers, API tools, data tools, rail providers, and payment-enabled services.
The listing carries service identity, service route, trust badge state, commercial plan reference, and fee event in one readable record.
The public path now connects operating tools, free wallets, wallet-bound runs, fee-bound completion, developer usage, and trust listings without splitting the system into separate stories.
What Was Proven
Agent-ready services need more than a page. They need a listing record that can be discovered, read, priced, and connected to the commercial trail.
Developer usage can record account and fee events. Fee-bound runs can record completed paid movement. Trust listings can now record service identity, badge plan, and listing fee event.
That gives builders, agents, and service providers a cleaner way to participate in Wever Labs rails without turning each tool into its own isolated island.
What Was Added
The public Trust Listing Path is live at /trust-listing-path/. It presents verified listings for agent services with listing ID, service route, trust badge state, commercial plan reference, and fee event.
The Trust Listing Path API creates listing records, creates trust badge plans, records trust badge fee events, and reads listing history.
The build also adds the trust listing schema, examples, SQL tables, deployment manifest, discovery updates, and Trust Listings in the top navigation after Developer Fees.
What This Means
Wever Labs now has a public trust surface beside the wallet, run, fee, and developer paths.
A listed service can show where it participates, what route it supports, what badge plan applies, and which commercial record belongs to the listing.
The system is moving from tools alone toward a discoverable network of rails, services, builders, and returned outcomes.
What Comes Next
The next commercial step is Enterprise Controls.
Enterprise Controls will carry organization account, monthly platform plan, team wallet controls, agent count, wallet count, allowed rails, usage summaries, and commercial plan reference.
Scout can also begin surfacing listing candidates so agent-ready services can move from discovery into trust listing records.
Operating Principle
Make services findable. Give each listing a route. Tie the badge to the plan. Tie the fee to the record that created it.
Agentic rails for complex work.