agentic-paybench

Research artefacts for measuring agent-to-agent payment rails: a pre-registered evaluation methodology and a capability oracle. Rail-neutral by design: the method is designed for pairwise comparison, the published measurement asserts no merit ordering of named rails, and the work holds no commercial relationship with any rail it measures.

Repository What it is
payhelm PayBench: the measurement methodology (frozen v1.2), harness, and calibrated fixtures, as a fork of HELM. Pre-registered and anchored before publication of any result: OSF DOIs 10.17605/OSF.IO/XGFUJ and 10.17605/OSF.IO/UFQG5.
oracle The capability oracle: schema, ingestion, methodology, and the static read surface, live at oracle.agentic-paybench.dev.

What is published, and what is not. The methods are public. The authorization-primitive latency (DIM-02) findings for six named rails are published as a measurement at oracle.agentic-paybench.dev/results/. Rails on that page are listed alphabetically by rail name; that ordering is fixed and carries no performance meaning. The figures are a measurement and not a recommendation: no rail is endorsed, no ordering implies a best buy, and no rail is being suggested for use. Settlement-finality results are withheld by choice, not omission, and the published measurement asserts no merit ordering of named rails. Nothing here recommends a rail or routes a payment.

Rails covered by the methodology: x402, AP2, the Machine Payments Protocol (the Stripe and Tempo HTTP 402 protocol, on more than one settlement rail), and Lightning-based rails, measured on test networks and first-party traffic.

Research context, writing, and contact: everydayai.link, mblake@everydayai.link.

This page is the research index for the agentic-paybench GitHub organisation. Nothing here is a product, a service, or an invitation to transact.