MachineTransferTHE PAYMENT PROTOCOL
MachineTransfer organizes an agent payment around four explicit steps. Each participant has a clear role, and each step produces information the next one can verify.
REQUEST
The agent identifies a service from the operator’s approved catalog. A request describes the required result, such as a named dataset or a specific API response. The service identity connects the task to the operator’s rules.
“Retrieve the specified dataset within my approved budget.”
QUOTE
A merchant registers its service, recipient and quote signer. A signed quote ties the deliverable to its service revision, price, accepted token, network, recipient and expiry. MTR amounts distinguish the gross amount sent from the net amount received. An operator compares the complete cost, including gas and conversion.
AUTHORIZE
The model selects a known service. Application policy controls which routes and costs are eligible. The wallet approval binds the exact payment terms, while a unique authorization identifier supports replay protection.
MachineTransfer’s separation of intent, policy and signing keeps a model’s recommendation distinct from payment authority.
VERIFY
The settlement contract checks the current service revision and signed terms. The receiving application matches both the service event and token settlement to the invoice: the request, recipient, amount and authorization. A durable record connects the accepted payment with the service request. Retries reconcile that record so a repeated request can recover the same result.
Service delivery belongs to the provider’s application. Receipt verification gives that application a precise event on which to act.
Chooses the catalog, budget and allowed payment routes. Controls the wallet and approval policy.
Identifies a useful service and asks the configured tool for a purchase plan.
Defines the service, supplies its terms and matches the receipt to the requested result.
FROM CONCEPT TO INTERFACE