Pay for the rail. Get the package.
PacketOps, DiligenceOps, FinanceOps, TokenOps, EnergyOps, and DistributionOps are priced as run or package products.
Open product pricingPricing Separation
Product usage and agent movement have separate price paths.
Operating tools are paid by rail or package. Wallet fees are paid by completed agent-to-agent movement through the rail.
Product usageWallet movementReceipt feeDeveloper APIFee event
Two meters
Product usage and agent movement stay separate.
Operating tools are priced by rail usage. Wallet fees attach to completed agent-to-agent movement.
Wallet is free. Movement carries the fee.
Micro-routing, receipt, escrow, developer, trust, wallet tier, and enterprise fees attach to completed commercial activity.
Open commercial feesAPI usage records a fee event.
MCP servers and agent builders quote usage, record calls, and attach fee events to developer account IDs.
Open developer feesPublic pricing line
One product path. One movement path.
Customers buy returned work products. Agents and builders pay for completed movement through wallet, receipt, fee event, plan, listing, or account references.
Rail checkout
Run price, credit, checkout link, invoice, or order reference attaches to the selected operating tool.
Wallet and fee rail
Wallet, payment intent, receipt, fee event, and returned package move together on completed paid work.
SDK/API meter
Developer account, API usage, route, quantity, unit fee, and fee event form the commercial record.
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 line
Customers pay for returned work. Agents pay for completed movement.
Receipts bind payment, fee, and returned package on one rail.