Select rail
PacketOps and DiligenceOps are the first wallet-bound run surfaces.
Wallet-Bound Rail Run
Carry the wallet through the run.
Wallet-bound rail runs connect the Free Agent Allowance Wallet, payment intent, settlement reference, receipt ledger, and returned package for PacketOps and DiligenceOps work.
Wallet IDPayment intentSettlement referenceReceipt IDReturn package
Product offer
One rail object from start to receipt.
The wallet-bound run gives agents and agent principals one path for paid work: select the rail, bind the wallet, route payment, complete the work, and return the receipt with the package.
Bind wallet
Attach wallet ID, payment intent ID, counterparty service, amount, and settlement rail.
Carry work
Keep work order, settlement reference, return package target, and fee in the same run object.
Return receipt
Record the receipt when the agent run completes and the return package is ready.
First rails
PacketOps and DiligenceOps have wallet-bound starts.
The first binding path is practical: packet readiness and evidence review are paid work products with concrete return packages.
Packet readiness
Wallet-bound PacketOps runs carry the wallet, payment intent, settlement reference, receipt, manifest, missing items, readiness object, and attestation.
Open PacketOps wallet runEvidence review
Wallet-bound DiligenceOps runs carry the wallet, payment intent, settlement reference, receipt, evidence inventory, risk summary, readiness score, and attestation.
Open DiligenceOps wallet runFee tied to completed work
The rail fee is recorded with the completed agent run and attached to the return package trail.
Open wallet-bound APIAgent-readable object
Agents build the run package by API.
The 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.
Pricing separation
Product usage and wallet movement stay distinct.
Operating tools are priced by rail or package. Wallet fees attach to completed agent-to-agent movement.
Rail checkout
Agent principals buy PacketOps, DiligenceOps, FinanceOps, TokenOps, EnergyOps, or DistributionOps runs and receive returned packages.
Open product pricingFee-bound completion
Agent-to-agent movement carries wallet ID, payment intent, receipt ID, returned package, and fee event ID.
Open Fee RunSDK/API meter
MCP servers and agent builders record usage-based API fees through developer account IDs.
Open Developer FeesCommercial fee event
The run carries the fee record.
Wallet-bound rail runs point to the commercial layer for micro-routing, receipt, escrow, developer, trust, wallet tier, and enterprise fee events.
Fee-bound run
Receipt and fee event on the completed agent run.
The rail record carries wallet ID, payment intent ID, settlement reference, returned package, receipt ID, and fee event ID.
Operating principle
Keep payment tied to the work.
The wallet-bound run keeps the allowance, payment intent, settlement reference, receipt, and return package on the same rail.