BuggyPaydocs Sign inStart now

Connect your game to BuggyPay

Real players test your build and get paid per confirmed bug. Sage scores every report in seconds, your team decides the rest, and your AI agent can fix confirmed bugs while testers check the fix.

Players find itReport button inside your build
Sage judges itScore, severity, duplicates
Claude fixes itOver MCP, on a test build
Players verify itPaid retest before it closes

How BuggyPay works

  1. You create a campaign with a short brief, a price per severity (S1 to S4 and Idea) and Private (NDA) or Public. Then you fund the prize pool.
  2. Testers open your build from BuggyPay. Their link carries a personal key, so the yellow Report button appears only for them. Normal players never see it.
  3. A tester presses Report (or F8) and writes one sentence. The last seconds of play, the logs, the device and a screenshot they can draw on are attached for them.
  4. Sage scores it out of 100, proposes a severity and checks duplicates. Clear cases follow your rules (Manual, Assisted or Autopilot). Unclear ones land in Needs you.
  5. Confirmed bugs become tickets. Send them to Claude (or any MCP agent). It posts a fix on a test build and BuggyPay opens a paid fix check, so real testers confirm the fix before you release it.

Quick start (5 minutes)

  1. Sign in at buggypay.com/app, open Studio and create your studio.
  2. Press New campaign: name, brief, prices, Private or Public, and how much Sage may decide alone.
  3. Open the campaign's Setup tab. Either upload a zip of your web build (we host it and add the Report button for you) or paste the one-line script into your own build.
  4. Open your build once. Setup shows ✓ Report button detected within a minute.
  5. Fund the pool (USDG on Robinhood Chain) and press Go live. Testers see the mission right away.
BuggyPay is in open beta: sign in with your email and start. Tell us what feels wrong with the Feedback button.

Web games and apps

Anything that runs in a browser: HTML5 games, Three.js, Phaser, PlayCanvas, Unity WebGL, Godot web exports, Electron or Tauri apps, and normal web apps. Paste this before </body>. Your campaign id is in Setup.

<script src="https://buggypay.com/sdk.js" data-build="0.4.14" data-campaign="YOUR_CAMPAIGN_ID" async></script>
AttributeWhat it does
data-buildThe version testers are on. It is saved on every report, so you know which build a bug came from.
data-campaignLets Setup show "Report button detected" before any tester has opened the build.
data-alwaysShows the button even without a tester key. For your own testing only, reports without a key are refused.

Options in code

// Optional: point the clip recorder at your canvas, or change the version at runtime
BuggyPay.init({ build: '0.4.14', canvas: document.querySelector('#game') });
BuggyPay.report();   // open the form from your own menu
BuggyPay.active();   // true when a tester opened this build from BuggyPay

What a report contains: the tester's sentence, steps and expected result, a full-screen screenshot (game canvas and HTML menus) the tester can draw on, the last 20 to 40 seconds of the game canvas as a clip, the last 200 console lines and errors, the device, the page and the build.

Builds and versions

Testers always open your campaign's current build. Add builds in Setup > Builds:

  • Upload a zip of a web build with an index.html (at the top, or inside one folder). Up to 400 MB. We host it at buggypay.com/b/… and add the Report button and version for you. Unity WebGL builds with Brotli or Gzip files work as they are.
  • Paste a link to a build you host. Add the script line to it.

Every build gets a version and a "what changed" note. When you make a new build current, testers who already reported on your campaign get an email, missions show "new", and reports keep the version they were made on. Reports on an older build are flagged in your queue. You can switch back to any earlier build with one click.

Hosted builds run in a sandbox (see Security). Saving with localStorage works while the tab is open, but IndexedDB, service workers and cookies are not available. If your game needs them, host it yourself and use a link.

Upload from the command line

For CI, build scripts, or Claude after a fix. Needs Node 18+, nothing to install. Create a studio token in Setup > Connect Claude first.

curl -sO https://buggypay.com/tools/buggypay-upload.mjs
BUGGYPAY_TOKEN=bp_live_... node buggypay-upload.mjs ./dist --campaign YOUR_CAMPAIGN_ID --version 0.4.15 --notes "Fixed the double jump"

It prints the hosted link. Add --not-current to upload a test build without switching testers to it (this is what Claude uses for fix checks).

Build API

POST https://buggypay.com/api/build with Authorization: Bearer bp_live_…. JSON bodies:

opBodyReturns
startcid, version, notes, files:[{path,size}]bid, entry, part (max bytes per part)
putQuery ?op=put&cid=&bid=&path=&part=&parts=, raw bytes as the bodyok
finishcid, bid, current (default true)build {id, version, url}
linkcid, url, version, notes, currentbuild
use / listcid, id / cidswitch the current build / all builds

Native SDKs

For games that do not run in a browser. Testers copy a tester key from their mission card (it lasts 7 days and works on one campaign), then press F8, or shake the phone, and paste it once. After that the Report button shows for them, and only for them.

Desktop builds also read the key from --bp_token=KEY on the command line or the BP_TOKEN environment variable, which suits Steam launch options.

Unity

Windows, Mac, Linux, Android and iOS (Unity 2021.3 or newer). For WebGL builds use the script line or upload the build instead.

Download the Unity package

  1. Unzip and copy com.buggypay.report into your project's Packages folder (or Package Manager > Add package from disk > package.json).
  2. It starts by itself before the first scene. Optionally set the version:
BuggyPay.Init("0.4.14");          // optional, defaults to Application.version
BuggyPay.Open();                   // open the form from your own menu
BuggyPay.OpenChanged += open => Time.timeScale = open ? 0 : 1;  // pause while the form is open

Testers press F8 (or shake the phone) and paste their key once. The SDK attaches a screenshot taken before the form opens, the last 200 log lines from Application.logMessageReceived and the device and GPU. It works with both input systems. With only the new Input System, shake is off and F8 and the button still work.

Godot 4

Download the Godot addon

  1. Unzip into your project so you have addons/buggypay/.
  2. Project Settings > Plugins: enable BuggyPay. It adds the BuggyPay autoload.
BuggyPay.init("0.4.14")        # optional
BuggyPay.open()                  # from your own menu
BuggyPay.add_log("boss phase 2")  # extra lines for the report
BuggyPay.open_changed.connect(func(o): get_tree().paused = o)

Android

Download BuggyPay.kt Copy the file into your app (compileSdk 31 or newer, needs the INTERNET permission).

BuggyPay.init(this, buildVersion = "0.4.14")// in Application.onCreate or your main Activity
BuggyPay.handleIntent(intent)            // optional: key from a link with ?bp_token=
BuggyPay.open(activity)                  // from your own menu

Testers shake the phone (or tap the button once a key is saved). Callable from Java too. Pure NativeActivity games have no view for the floating button, so call open() yourself or rely on shake.

iOS

Download BuggyPay.swift Copy the file into your app (iOS 15+, Swift 5 language mode).

BuggyPay.start(build: "0.4.14")        // in application(_:didFinishLaunchingWithOptions:)
BuggyPay.handle(url: url)                 // optional: key from a link with ?bp_token=
BuggyPay.open()                           // from your own menu

Shake opens the form. Logs come from OSLogStore (NSLog, os_log, Logger), not Swift print.

Any engine (HTTP)

One JSON call. CORS is open.

curl https://buggypay.com/api/report -H "Content-Type: application/json" -d '{
  "token": "TESTER_KEY",
  "sentence": "The worm goes through the canyon wall after the second wave",
  "steps": "1. Start round 2  2. Wait by the north wall",
  "expected": "The worm bursts out of the sand",
  "device": "Windows 11, RTX 3060, 2560x1440",
  "build": "0.4.14",
  "logs": "last 200 lines of your log",
  "shot": "data:image/jpeg;base64,..."
}'
FieldNotes
tokenThe tester key (required). Send {"token": "...", "check": true} to validate it.
sentenceRequired, 8 to 400 characters.
steps, expected, actual, device, build, pageOptional text.
logsUp to 12,000 characters. The newest lines matter most.
shotData URL, PNG, JPEG or WebP, up to 3.5 MB. Keep it under 1600 px wide.
clipData URL, MP4 or WebM, up to 3.5 MB.

Success returns { ok, num, status, score, severity, dupOf, reasons }. Errors return a status code and { error } with a message you can show the tester. Keep the whole body under 4.4 MB.

Claude fixes (MCP)

BuggyPay is an MCP server. Create a token in Setup > Connect Claude and run this in your game's repository:

claude mcp add --transport http buggypay https://buggypay.com/api/mcp \
  --header "Authorization: Bearer bp_live_..."

Then ask Claude: "Work the BuggyPay queue." Any MCP client works the same way.

ToolWhat it does
list_confirmed_bugsTickets waiting for a fix.
get_ticketSentence, steps, device, build, logs, 24-hour links to the screenshot and clip, Sage reasons, repository.
claim_ticketMarks it as being fixed.
post_fixFix is on a test build: opens a paid fix check for real testers.
get_fix_check_resultVerified or reopened, with tester notes.
add_ticket_note, release_ticket, request_fix_checkTalk to your team, give a ticket back, retry a fix check.

Claude opens a pull request and a test build. It never merges unless you tell it to. For web games without hosting it uploads the fixed build with the command-line uploader.

How fixes are verified

  1. Claude proves the fix. It opens the new build, goes to the spot of the bug and uploads 1 to 3 screenshots plus the new logs (POST /api/build?op=evidence&ticket=BP-1234, add &kind=logs for logs). For late bugs it adds a temporary start option to the test build.
  2. Sage pre-checks it against the original report: does the screenshot still show the problem, does it show the expected result, is the original error gone from the logs, does the change fit the bug. If Sage still sees the bug, the ticket goes straight back to Claude before any tester is paid.
  3. Your rule per severity decides the rest (campaign Settings, "Who verifies a fix"). The default is Sage alone for Idea and S4, 1 tester for S3, 2 for S2 and 3 for S1. Sage only verifies alone when it is sure. Otherwise a tester checks.
  4. Testers retest inside the game. They open the fix check, the game shows the original bug, and the button becomes Retest BP-1234. At the spot they press Fixed or Still broken. The screenshot, clip and logs are attached automatically, so there is nothing to upload.

Games can jump testers straight to the bug in retest mode:

BuggyPay.onRetest(function (info) {
  // info.num, info.sentence, info.steps, info.expected
  if (info.steps.includes('wave 18')) startAtWave(18);
});
Sage reads logs exactly but game screenshots only loosely. A screenshot alone never costs a tester their pay. If it disagrees with their answer, the studio sees a flag and checks the clip. If the original error is back in their logs, the answer does not count.

Discord, Slack and webhooks

In Setup > Alerts paste a Discord webhook, a Slack incoming webhook, or any https URL. Pick Important or Everything and press Send test.

Important events: report.needs_you, bug.confirmed, fix.posted, fix.verified, fix.reopened, fix.released, build.new, pool.empty, campaign.live, report.appeal. Everything adds Sage scores, payments and other activity.

Other URLs receive JSON:

{
  "event": "bug.confirmed",
  "campaignId": "lFMASksqDx",
  "campaign": "HORDE ROYALE · team test",
  "actor": "Sage",
  "text": "Confirmed BP-2311 as S2. Ticket: sent to Claude.",
  "ref": "BP-2311",
  "at": "2026-11-12T14:05:00.000Z",
  "link": "https://buggypay.com/app#/c/lFMASksqDx/reports"
}

GitHub issues

In Setup > GitHub enter owner/name and a fine-grained token limited to that repository with Issues: read and write. Then:

  • Each confirmed bug opens an issue titled [BP-2311] … with steps, expected, severity, build, device and Sage score, labelled buggypay and the severity.
  • When a fix is posted, the issue gets a comment with the test build and pull request.
  • When testers verify the fix the issue closes. If they reopen it, their notes are added.

The token is stored encrypted and is never shown again. Errors appear in Setup.

Community reports (Discord)

Your own bot can file a bug report from your community as a BuggyPay ticket, so it sits in the same lists and goes through the same confirm, Claude and fix flow. Use a studio token from Setup > Connect Claude.

curl https://buggypay.com/api/external \
  -H "Authorization: Bearer bp_live_..." -H "Content-Type: application/json" -d '{
  "game": "HORDE ROYALE",
  "source": "discord",
  "author": { "id": "123456789012345678", "name": "mossy_frog" },
  "title": "The worm goes through the canyon wall after the second wave",
  "steps": "1. Start round 2  2. Wait by the north wall",
  "expected": "The worm bursts out of the sand",
  "actual": "It slides through the wall",
  "device": "Windows 11, Chrome",
  "url": "https://discord.com/channels/111/222/333",
  "images": ["https://cdn.discordapp.com/attachments/222/444/shot.png"]
}'
FieldNotes
campaign or gameThe campaign id (Setup shows it), or the game name. With game, BuggyPay picks your live campaign whose name contains it; if none matches you get a 404, if several match a 409 that lists them.
sourceRequired. discord.
authorRequired. id and name of the person who posted it.
titleRequired, 8 to 200 characters.
steps, expected, actual, device, buildText. Longer text is cut (steps 1,500 characters, expected and actual 600, device 300).
urlRequired. The https link to the Discord post (https://discord.com/channels/...). Sending the same post again returns the same ticket.
imagesOptional. Up to 6 https links (the first 6 are kept). BuggyPay stores the links only, not the files.

Success returns { "ok": true, "ticket": "BP-1234", "url": "https://buggypay.com/app#/c/<campaign>/reports/BP-1234", "campaign", "status", "score", "existing" }. existing is true when the post was already filed. Errors return a status code and { error }: 400 a field is wrong, 401 the token is missing or revoked, 403 the campaign belongs to another studio, 404 no campaign matches, 409 the campaign is not live or several match, 413 the body is over 20 KB, 429 the campaign already got 60 community reports today.

Community reports are never paid. They have no BuggyPay tester behind them, so nothing is credited and your budget is not touched: no base pay, no bonus, no confirmation pay and no paid retests. Sage scores them so you see a score, but it never confirms them: your team decides. When a fix is posted, your team retests it and marks it verified (or Sage verifies it alone for the severities you allow). Your Discord, Slack and GitHub alerts work as for any ticket.

What testers see

Testers are 18+ and sign in with email. They see your mission with its prices, budget and brief, accept the NDA if the campaign is Private, then open the current build or copy their tester key. After a report they see Sage's score and reasons. They are paid in USDG on Robinhood Chain after a 48-hour hold. Testers who reported before get an email when you publish a new build, and the reporter is invited first to retest a fix.

Security and privacy

  • Hosted builds are sandboxed. They are served with Content-Security-Policy: sandbox without same-origin, so build code can never read BuggyPay sessions or act as the tester. BuggyPay adds an in-memory localStorage so saves work while the tab is open.
  • Hosted links are secret, not private. Anyone with the link can open the build. Private campaigns also bind testers with an NDA.
  • Evidence is private. Screenshots and clips are stored privately and shared through signed links that expire.
  • Keys: tester keys last 12 hours (web) or 7 days (native) and work on one campaign. Studio tokens can be revoked in Setup.
  • The SDK records only the game canvas and your page's console, never the tester's other tabs or screen.

Limits

WhatLimit
Hosted build400 MB, 4,000 files
Screenshot, clip3.5 MB each
Reports per tester15 per campaign per day
Webhooks5 per campaign
Builds kept in the listThe last 60

Questions: hello@buggypay.com