Put a budget on your next build. Real people play it and report what breaks, Sage scores every report from the clip and the logs, and Claude fixes the confirmed bugs. You read one summary a day.

Testers paid from your own wallet Pay in USDG or your own token BuggyPay never holds your money
Game screen: a giant sandworm glitching through a canyon wall, a physics bug. The same scene after the fix: the sandworm bursts cleanly out of the sand in the arena.
HP 72
Rust Dunes · build 0.4.12
Last 30 s saved

Every bug on one board, moving by itself.

Reported, confirmed, sent to Claude, fixed, checked by players, verified. You step in only when a card needs you.

app.buggypay.com/rust-dunes/fix-pipeline
The BuggyPay studio console showing the fix pipeline for Rust Dunes: bugs in columns from Reported to Verified, with an Approve release button for three verified fixes.

One bug, start to finish, while you sleep.

This is a real path through BuggyPay on Autopilot. People do the playing and the checking. Sage and Claude do the reading and the fixing. You spend under a minute.

Example campaign: Rust Dunes, map 2. The times show a typical night.

  1. @kitedrop taps Report during the boss fight

    The last 30 seconds, the console logs and the phone model are attached on their own. One sentence: “The worm went through the wall on its second dive.”

  2. Sage scores it 82 out of 100

    Visible in the clip at 00:21, a navmesh warning in the logs, no earlier report like it. Marked S2 Major, three more testers confirm it within the hour.

  3. The tester is credited a base of 3.00 USDG

    Held for 48 hours, so a wrong call can be undone. You send it from your wallet when they withdraw.

  4. The ticket goes to Claude

    Steps to reproduce, expected and actual result, the clip and the logs, sent through MCP to your coding agent.

  5. Claude opens a pull request and a test build

    “Clamp the worm dive to the arena bounds.” PR #482, build 0.4.13. Nothing is merged without you.

  6. A paid fix check goes live

    The tester who found the bug is asked first.

  7. Three testers confirm it is fixed on 0.4.13

    @kitedrop is credited the 9.00 USDG bonus. The other confirmations are credited too.

  8. You approve release 0.4.13

    From the daily summary: 23 reports, 17 fixed, 15 verified, 2 waiting for you.

    Your time on this bug: about 40 seconds.

You choose how much Sage decides.

Set it per campaign and change it whenever you like. In every mode Sage explains each score with evidence, and fraud flags, appeals and unsure calls always reach a person.

Sage never moves your money: it credits testers, and you send the coins from your own wallet when they withdraw. Paying in points? Then Autopilot is hands-off from start to finish, with nothing to send. Every automatic decision can be undone during the hold, and every action Sage and Claude take is written to an activity log.


Stop reading bug reports. Start shipping fixes.

Everything a studio needs to run testing as a pipeline, not a pile.

Fixes move on their own

Confirmed bugs go to Claude, fixes come back as a test build, and players check them before you release.

37 reports become 11 bugs

Sage groups duplicates. Each bug is one ticket with steps, a clip and the logs.

Sage shows its working

Every score lists the evidence behind it, so you can trust it or overrule it in one click.

  • Visible in clip at 00:21 +30
  • No earlier report matches +25
  • Navmesh warning in logs +15

Plug in your coding agent

The BuggyPay MCP server works with Claude Code and any agent that speaks MCP.

list_confirmed_bugs()
get_ticket("BP-2318")
post_fix(build, pr)
request_fix_check()

Private or public, your call

Private campaigns run under NDA. Public ones can pay players to post their clips on X.

Get paid to play what is not out yet.

Pick a mission, play, tap Report when something breaks. Sage tells you your score and why within minutes, and the money lands in your wallet or your bank.

40.00USDG for a critical bug
8 sto send a report
48 huntil it is yours
  • See the price of every mission before you start
  • Get asked first to check the fix for the bug you found
  • Rank up from Rookie to Elite for better-paid private tests
  • For players aged 18 and over, one account per person
Start testing
The BuggyPay tester app on a phone: Sage scored a report 76 out of 100, with the reasons, the severity S3 Minor and 5.00 USDG on its way.

Seven kinds of mission, one place to run them.

You set the price for each. They work for games and apps, including onchain apps on Robinhood Chain.

Bug hunt

Find what is broken. Paid per bug by severity, from S1 Critical to S4 Polish.

e.g. 2.00 to 40.00 USDG per bug

Fresh eyes

A first-time session. Sage marks the moments a new player gets stuck or wants to quit.

e.g. 6.00 USDG per session

App review

Testers use your app, rate it, run your flows step by step and send screenshots. You see which step loses people.

e.g. 3.00 USDG per review

Balance survey

Play, then answer a few questions on difficulty and fairness.

e.g. 2.00 USDG per survey

Device check

“We need five cheap Android phones.” Fill the gaps your team cannot test.

e.g. 4.00 USDG per device

Fix check

Created on its own when Claude has a fix ready. Testers confirm it on the new build.

e.g. 1.50 USDG per check

Post on X

Public campaigns only. Testers post their clip, and Sage checks the post is real and theirs.

e.g. 3.00 USDG per post

Professional testing for every team on Robinhood Chain.

However small your team or project is. Testers check every onchain step: connecting the wallet, approving, signing, sending and what happens after. BuggyPay reads the transaction on Robinhood Chain, so your team sees if it went through or failed, and why.

Every onchain step

Wallet, network switch, approval, signature, transaction and the screen after it, tested on real phones with real wallets.

Your flows, step by step

Write the paths that must work. Testers follow them and tell you the exact step where it broke.

USDG, your token or points

Pay in dollars or your own token, or start free with your own named points and a leaderboard.

BuggyPay for Robinhood Chain


of what you pay testers. That is the whole price.

  • Sage scoring, duplicate grouping and tickets included
  • The MCP server, every integration, unlimited team members
  • No subscription, no seats, no setup fee
  • No budget yet? Pay in your own points (SEED, XP…). Free during the beta
If testers earn 70% of it1,400.00
BuggyPay fee, 10% of that140.00
You pay in total1,540.00
Never leaves your wallet600.00

You pay testers in USDG or your own token on Robinhood Chain, straight from your wallet, only when they withdraw. Your coding agent is billed by its own provider.


Your money and your final say stay visible.

Your coins stay yours

BuggyPay never holds your money. You pay each tester from your own wallet, and testers see that the wallet holds what they are owed. Every payment is checked on Robinhood Chain.

Your own token works too

Pay testers in USDG, or in your own game coin on Robinhood Chain. Testers withdraw straight to their wallet.

People in the loop

Real people find the bugs and check every fix. You approve releases and can switch any campaign back to Manual.

Built against farming

One account per person, caps that grow with rank, a hold before payouts, and Sage flags reused clips and edited screenshots.


Questions studios ask

Can I use BuggyPay now?

Yes. BuggyPay is in open beta. Sign in with your email (no password, no card). Testers can join any open mission right away; studios can set up a campaign in a few minutes, free when you pay in your own points.

Does Sage decide who gets paid?

Only inside the rules you set. In Manual your team confirms everything. In Assisted Sage handles small, clear bugs and sends S1 and S2 to you. In Autopilot Sage confirms every report it is sure about, within your budget and limits. Sage only credits testers: the coins leave your wallet when you send them. Every decision shows its reasons and can be undone during the hold.

Will Claude push code to my game without asking?

No. Claude opens a pull request and a test build. Merging and releasing stay off until you turn them on, and you approve every release.

Do I need crypto?

Yes, for now. Studios pay testers in USDG or their own token on Robinhood Chain, from their own wallet. Testers withdraw to a wallet such as MetaMask or Rabby. A studio without a wallet gets one made by BuggyPay at sign-up.

What if my product is not a game?

The same missions work for web and mobile apps. Testers can upload a screenshot or video when there is no SDK in the build.

What happens to money we do not use?

Nothing: it never left your wallet. You only pay what testers earned, plus the 10% fee on that.

Who can be a tester?

Anyone aged 18 or over with one verified account. New testers start with small daily caps that grow as their reports are confirmed.

Ship the build your players asked for.

BuggyPay is in open beta. Sign in with your email and start today: testers play and earn, studios run their first campaign in minutes.

Or leave your email and we send you news about new missions and features:

We only use your email for BuggyPay news. We never sell or share it.