wallet_id + payment_intent_id
The run starts with wallet authority and a bounded payment intent.
Fee-Bound Rail Run
The first paid rail run carries the fee with the work.
Fee-Bound Rail Run binds wallet ID, payment intent ID, settlement reference, returned package, receipt ID, and fee event ID on one agent-to-agent trail.
WalletPayment intentReturn packageReceiptFee event
Run object
The fee-bound run record.
The run record holds the commercial link between agent payment, returned work, receipt, and Wever Labs fee.
work_order_id + return_package_id
The selected rail returns a package tied to the paid run.
receipt_id + fee_event_id
The completed run records receipt, settlement reference, fee type, fee units, and commercial state.
First rails
PacketOps and DiligenceOps are fee-bound.
The first fee-bound path starts with the two strongest returned-package rails.
Packet readiness run
Manifest, missing-item report, readiness object, exception object, attestation, receipt, and fee event.
Open PacketOps fee runEvidence review run
Evidence inventory, missing-item report, risk summary, readiness score, attestation, receipt, and fee event.
Open DiligenceOps fee runFee event ledger
Micro-routing, receipt fee, escrow fee, and developer fee records bind to completed activity.
Open developer fee pathAgent-readable object
Fee-bound runs are available by API.
The API returns the active run surface and records completed paid rail runs with fee events.
Trust Listing Path
Verified listings carry plan and fee records.
Trust Listing Path attaches trust listing ID, commercial plan ID, trust badge state, and fee event ID to agent and service listings.
Operating principle
Charge the rail when completed paid work returns.
The fee record sits beside the payment intent, receipt, settlement reference, and returned package.