Kervon provides a normalized execution interface for machine-payment intents across x402, stablecoin networks, facilitators, and emerging AI payment rails. This documentation describes the concept model. Endpoints referenced are fictional examples.
A MachinePaymentIntent declares the economic action an agent wishes to take: a resource, a maximum value, and a set of rail/asset/network constraints. Kervon compiles the intent into a candidate execution graph.
Kervon normalizes rail-specific semantics (x402, MPP, AP2, ACP) into a common quote and settlement model so the compiler can compare candidates on cost, latency, and admissibility.
x402 is treated as an HTTP-native rail adapter. See the x402 network page for lifecycle and adapter detail.
An ExecutionGraph is the set of candidate paths produced by the graph constructor, each annotated with cost, latency, and admissibility under the current policy.
Policy defines spend caps, allow lists, rail restrictions, and the threshold above which principal (human or upstream system) approval is required.
A SettlementReceipt records the economic outcome of an execution plan. A separate ResourceReceipt records whether the underlying resource was delivered.
SATISFIED, PAID_UNFULFILLED, PAYMENT_FAILED, and INDETERMINATE describe the combined economic and resource outcome of an execution. See the homepage settlement section.
Errors carry a domain, terminality, and recovery strategy. See the full taxonomy on the homepage and specification.
See the homepage compiler and execution explorer for end-to-end simulated flows.
All endpoints referenced in this documentation are fictional examples. No live API is available.