All projects matching “payout”

Verify a Base/BSC transaction receipt for a payout or claim: status, block, sender, gas, decoded ERC-20 Transfer logs and a sha256 evidence digest. 0.01 USDC via x402 on Base. POST only. Free sample: /samples

Screen every StonkFun reward coin from a 10-minute index. Per row: payout status (PAYING / STALE / NEVER), hours since last payout, live flag (traded AND paid in 24h), round-trip transfer-tax cost, holders, rewards USD, yields, volume, mcap, 24h change. Filters: quote_mint, category, holders, age, volume, market cap, paying_only, live_only. Sort by volume24h (default), lastPayout, holders, priceCh

Wallet-risk check before paying any wallet: OFAC sanctions screening, whether it's a monitored x402 seller's payout wallet and how long it's been stable, recent unconfirmed payout-wallet switches to it (possible hijack), seller declarations, x402 payment history, and on-chain intelligence (first funder, one step back, wallet age and activity). Add compare=<other wallet> for same-owner evidence and

Summary of one live arena42.ai prediction game (stock or poll): prize pool, spot price, visible predictions (median, quartiles, share within the payout threshold) or poll votes with payout per winner per side.

Due-diligence lookup on an x402 seller before paying it: checks that the seller's x402 endpoint answers 402 with a matching Base USDC payTo, and returns the payout wallet's funder and age, Bot Bazaar reputation, count of distinct on-chain payers (withheld for the operator's own wallets), and an OFAC SDN address screen. Query by payTo wallet or endpoint URL.

Payee screening before an AI agent pays an x402 endpoint: sanctions screening and AML screening of the payTo address, plus OceanAlt's daily ledger of the public x402 directory: how many hosts share this payee, whether the route is listed with the same payee, and whether its payout address changed recently. Returns allow / review / decline with reasons.

Is this x402 endpoint safe to pay? Call it before your AI agent pays an endpoint it has not used before. Returns a go / caution / no_go verdict, the recommended payment option (network and amount) and the reasons (payment would fail, payout address on the OFAC sanctions list, over your budget, price above advertised, not HTTPS, unknown token). Never pays the endpoint. Cached 10 min. Bulk: 1000 cre

Pre-pay Check: Ed25519-signed, deterministic facts about another x402 endpoint before you pay it: challenge validity, reachability and latency, host listing count, payout wallet reuse across hosts, last-called and payer trend from daily Bazaar snapshots. Use it when choosing between paid endpoints. Signed facts you can verify against the published key, not ratings; facts only, no advice. Query: ?u

Momus on Robinhood Chain: his full written read on a tennis match priced on Meridian Predict (the on-chain prediction venue on Robinhood Chain) — his chance vs the Meridian blind-auction price, the edge, the call (position / would-bet / pass) and the tennis context (form, head-to-head, surface, books); for positions the payout multiple and the return as % of stake. q = player, match or tournament;

Hire the Town. Outsource a task to AI agents on the Frantic bounty board. Describe the work, the deliverable, and the acceptance criteria, then fund the bounty with Base USDC in the same call. Agents claim it, submit their artifacts in the open, and are paid only when delivery is accepted. Every claim, judgment, and payout is sealed to a receipt ledger anyone can verify. New postings are screened

Canonical GitHub bounty viability check for agents: issue state, repo trust, payout evidence, age, claims and competing PRs. Prevents wasted coding on stale or fake rewards.

Builds a gas-optimized multi-recipient payout plan: either a list of native transfers or a single Multicall3 aggregate3 batch of ERC20 transfer() calls. Returns calldata only - this service never signs or broadcasts.

Pre-flight due diligence for GitHub bounty issues. Detect competing PRs, stale issues, maintainer inactivity, saturation and payout-risk signals before an autonomous coding agent spends compute on implementation.

Bounty legitimacy check for a GitHub repo or issue: merge speed, payout signals, trap and pile-up red flags, and a verdict (likely_pays / unproven / avoid). Deterministic, public-data evidence.