One commitment.
Two possible outcomes.
Illustrative exampleMatching bytes return 25 USDG to available collateral.
A service fee pays for the call. Reserved collateral backs the promise to deliver.
Matching bytes return 25 USDG to available collateral.
25.00USDG
2.5% of the initial operator bond.
Reserved before the client pays.
Not loaded USDG
Available and reserved. Protocol-wide.
Not loaded jobs
Not loaded USDG
Latest 20 commitments. Reserved or active.
Not loaded USDG
Latest 20 commitments. Claimed onchain.
Reading the deployed contract...
The operator puts collateral behind a specific promise before the client pays. Every condition is fixed onchain.
A fixed client, agreed result hash and compensation amount. The reserved bond cannot be withdrawn.
Capital lockedOne dedicated destination for one commitment. Activation transfers the fee and starts its delivery window.
Clock startedMatching bytes release the bond. After a missed deadline, anyone can trigger compensation to the fixed client.
Outcome onchainSurety starts with public data whose hash is agreed before payment. No subjective scoring of an AI answer.
Explore the covered conditionThe operator, from collateral already reserved for that commitment.
Only available bond can be withdrawn. Reserved compensation stays locked until delivery, compensation or expiry of an unactivated reservation.
After its payment cutoff, the reservation can expire. Its vault refunds the fixed client and releases the operator's bond. Late or excess funds remain recoverable to that same client.
Not by itself. Reserve cover first, pay the dedicated vault and activate the job before its cutoff. The delivery clock starts at activation.
Pay the service fee in USDG to the commitment’s dedicated vault, then activate the funded job. The application supports direct onchain payment. x402 integration details
Inspect the bond. Reserve a commitment. Follow its outcome.
Explore the application