OkayOkayOkay

Okay3.xyz solves the legal aspect of reimbursement requests for Agentic x402 payments.

The current landscape of Agentic commerce offers no guarantee over the quality of the resource. Users are 100% subject to the goodwill of the resource in case of requested reimbursements.

Current proposed standards do not take this legal aspect into account yet. Users cannot trust resource sellers to return a payment.

Okay3.xyz acts as a verifiable intermediary between the buyer and the seller. With Okay3.xyz Payments are locked in an escrow contract as long as the legal framework allows for chargebacks. Once a payment is recorded on the Okay3 escrow, our platform links the payment to the purchase and starts the dispute period. The exchanged data is verifiable for both parties and also retrievable for neutral arbitration agents that observe the escrow for unsettled dispute cases.

In the first instance, a user can record a filing for a dispute on the escrow contract. After this, the seller can either accept or deny the claim. If buyer and seller are not in agreement, the dispute period reaches a higher level, where arbitration agents retrieve and verify the request and can then vote for an outcome of the case. Once the case is resolved, the outcome specifies whether the buyer or sellers receive the payment in the escrow. Arbitration agents can be rewarded with a small tipping fee for their neutral work. (Further economic mechanism are planned)

The Okay3 protocol is offered as a web platform for demo purposes on top of these escrow contracts of resource sellers (agents would the protocol without web platform). Both parties have access to dashboards where they have an overview about past and pending dispute processes. Beyond that, we offer general analytics for buyers and sellers.

Okay3.xyz escrows are created through a smart contract factory for each seller. Escrow contracts receive the buyers funds and record the process from purchase until resolved dispute claims. In particular, events are emitted on the escrow contract which are observed by arbitration agents. As latency and costs are of essence to solve claims on micro payments at scale, we have indexers getting triggered on these dispute events on the escrow contract.

All smart contracts are deployed on Base and the web platform uses Coinbase Server Wallets offered by the CDP to allow x402 payments as well as signing the other transactions involved in dispute filings.

A centralized proxy stores all request data, which is additionally hashed and signed by the seller for verifiability.

Arbitration agents are custom light-weight LLM agents with a custom prompt that load and verify the data and then vote on the dispute claim. They are triggered as serverless functions.