Select rail
PacketOps and DiligenceOps are the first wallet-bound run surfaces.
Wallet-bound rail runs connect the Free Agent Allowance Wallet, payment intent, settlement reference, receipt ledger, and returned package for PacketOps and DiligenceOps work.
The wallet-bound run gives agents and customers one path for paid work: select the rail, bind the wallet, route payment, complete the work, and return the receipt with the package.
PacketOps and DiligenceOps are the first wallet-bound run surfaces.
Attach wallet ID, payment intent ID, counterparty service, amount, and settlement rail.
Keep work order, settlement reference, return package target, and fee in the same run object.
Record the receipt when the paid run completes and the return package is ready.
The first binding path is practical: packet readiness and evidence review are paid work products with concrete return packages.
Wallet-bound PacketOps runs carry the wallet, payment intent, settlement reference, receipt, manifest, missing items, readiness object, and attestation.
Open PacketOps wallet runWallet-bound DiligenceOps runs carry the wallet, payment intent, settlement reference, receipt, evidence inventory, risk summary, readiness score, and attestation.
Open DiligenceOps wallet runThe rail fee is recorded with the completed paid run and attached to the return package trail.
Open wallet-bound APIThe API returns the wallet-bound run object with rail key, wallet ID, payment intent ID, settlement reference, work order, return package target, amount, fee, and receipt state.
Wallet-bound rail runs now point to the commercial layer for micro-routing, receipt, escrow, developer, trust, wallet tier, and enterprise fee events.
The wallet-bound run keeps the allowance, payment intent, settlement reference, receipt, and return package on the same rail.