Loops HouseMeteredPay

NEAR HACKATHON
Team
1 member- OLOwner
Olly McBride
Overview
A buyer agent needs one document checked — a quote, an invoice — and the seller is paid only if the check is schema-valid. MeteredPay does that on NEAR testnet: the buyer prepays testnet NEAR into a contract and sets a spending limit; a seller agent offers a deterministic schema-validation check at 0.1 testnet NEAR per call. The contract deducts only when the buyer verifies the seller's signed success receipt and authorises the deduction itself — the seller can never mark its own calls successful. A failed check is released, never deducted (deducted: zero): the buyer submits the failure claim. Security: a call past the spending limit is refused on-chain at request time. MeteredPay puts the success condition in a NEAR contract the payer can verify and replay: buyer-verified hash, payer-signed receipt, on-chain cap refusal, buyer-claimed release, a 600 s backstop, and a dispute-audit view. Every outcome is a transaction on the frozen testnet contract apathetic-party.testnet, and a judge can replay the same wasm on their own contract from the README (frozen replay needs the builder's seller key). Agents: one agent earns, one spends, payment tied to a delivered result. Open: x402's auth-capture permits an arbiter to gate capture, but no shipped x402 flow on NEAR gates it on the payer's verified receipt — that condition is new on NEAR, a single-seller primitive, with a public seller spec, a redeploy runbook and a second seller now proven paid on a parallel instance, and a summariser at 0.05 on a third instance. Business: a micro-transaction with no human in the payment loop. DeFi: only as a settlement primitive — the contract holds the deposit and enforces deduction, release and refusal, no custodian. Testnet only; no production-network funds move. Honest limits: a buyer could claim failure after a genuine success — it protects the buyer from paying for failure, not the seller from a dishonest buyer; and v1 has no buyer withdraw.