Inspiration
Every AI-payments project we saw moved money one direction: human to agent. Checkout agents, shopping copilots, paywalls — all spend. We wanted the missing direction: agents produce verified work, humans get paid. Slop.cash is the payroll lane — a bridge between delta-git, an agent-native git forge where AI agents ship code behind signed, hash-chained attestations, and PayPal Payouts.
What it does
An agent ships commits to a repo on code.widespread.fyi; a signed dg-ship-1 claim lands in the repos public hash-chained op-log. Slop.cash picks up the claim, independently replays the chain, recomputes every referenced commits real diff against the upstream patch, and asks a Workers AI LLM (Llama 3.3 70B) to adjudicate spec-fit and evidence validity — not a rules engine. Accept -> a real PayPal Payouts transaction to the contributors PayPal-linked email, and the receipt is written back to the forge as a signed commit status. Reject -> logged with the models reasoning, no money moves. The reverse lane too: an HTTP-402 paywall on premium op-log exports settles via a PayPal Order — x402 semantics, PayPal settlement, not crypto. Both money directions through PayPal.
How we built it
One Cloudflare Worker (~600 lines TypeScript, no framework). KV stores bounties, claims, and review records; Workers AI is the adjudicator; PayPal Payouts and Orders APIs (sandbox) move real money. Pipeline: fetch op-log -> replay hash chain -> recompute upstream commit diffs -> LLM verdict -> idempotent payout keyed by claim hash -> signed forge write-back. Dashboard: AG Grid. Postman collection replays the whole flow.
Challenges we ran into
Workers AI wraps the verdict in an OpenAI-style choices envelope — our first parse returned nothing until we unwrapped message.content. Re-running a review re-POSTed the payout and PayPal rejected the duplicate sender_batch_id — the fix refreshes the existing batch instead of re-sending, keyed by claim hash. The forge wipes op-logs periodically and reuses seq numbers, so same-seq-different-hash entries must trigger fresh reviews. And sandbox order approval needs a real buyer session — we drove the whole checkout flow in-browser to prove the 402 lane end-to-end.
Accomplishments that were proud of
A real PayPal sandbox transaction fired from an AI verdict — batch and transaction ID, SUCCESS. Bidirectional money: payouts out, and a PayPal-settled HTTP-402 premium lane back. Verifiable provenance: anyone can replay the same chain and diff — dont trust, replay. And the demo is 100% live — judges can click every receipt themselves.
What we learned
Idempotency is the difference between a payment demo and a payment system. x402 is a natural fit for PayPal settlement — the wallet-address assumption was the only crypto part. And verification means recompute, not trust: the chain replay made the adjudicator evidence-first.
Whats next for Slop.cash
ERC-8004 signed payout receipts as agent identity. AG Studio agent-driven dashboards. Per-work-intent bounties, reputation-weighted pools, and recurring salary payouts for standing agents.
Log in or sign up for Devpost to join the conversation.