You built the agent. Now get expert user feedback.
Choose a specialist who understands your users' work. They test your app or agent and report what happened, where they found problems and what to change. You set the reward and approve each report before payment.
Runs on Openhands Network, the IXO chain's marketplace for checked work: the terms are pinned before the work, and every payment is recorded on the chain.
Start with your agent, in your own coding tool.
Paste the setup prompt into Claude Code (the Code tab in the Claude app) or Codex. It connects you to the network and sets up the review with you.
- 01
Describe what to review, and set the payment.
The version, who it serves, the scenarios to try, how the specialist gets in, what a report must contain, and what each report earns. Nothing posts until you approve the whole review and its total.
With your agent - 02
Invite the specialists you choose.
From the directory of specialists, or your own people by address. Only people on your list can enter. Their profile shows what they do, their rate and their record on the network.
Invite, on the web - 03
Review reports and approve payment.
Reports are checked against your published requirements. Read each report that passes, then approve it to release payment to the specialist. Reports that do not meet the requirements are not paid.
Approve a report
Findings supported by test results
A report follows one shape: the steps the specialist took, what they expected and saw, each finding with its severity and how to reproduce it, and what to change first.
Only the builder, the specialist who wrote it and the automated checks can open a report and its screenshots. Anyone can see that it was sent and how the automated checks went. Put only a public description of your product in the review, and send access details only in the invitation each specialist gets.
Qi Portal 2.3 · onboarding and the first project
- Reviewed by
- Ana Kovač, @ana-qa
- Tested
- 2.3.0 on Android 14 and iOS 18, 19 to 21 Oct
- Scenarios
- 4 of 4 tried · 1 blocker · 4 major · 6 minor
Invite link opens a sign-in loop on a phone that has no account
- Observed
- Tapping the invite opens Sign in; after the passkey prompt the page returns to Sign in. Three attempts, same result.
- Expected
- A first-time person lands in the project with the invite accepted.
- Reproduce
- Fresh Android profile, invite from a project owner, tap in WhatsApp.
Export says "done" before the file exists
- Observed
- The toast appears at once; the download starts 20 to 40 seconds later, with no sign that anything is happening.
- Change
- Say "Preparing your export" and show when it is ready.
The actual report names the specialist, the version tested, every step and every finding, and is signed by their account.
Set the scope and reward
Set the payment per report and the number of reports you will pay for. Reports are paid in IXO. The specialist reads the scope and the payment before entering.
- The version and the people you want it tested byyou choose
- The scenarios and what a report must containpinned before the work
- Steps, observations, findings with severity, recommendationsone report shape
- Payment per report, and how manyheld on chain when you post
- Final approval of each paymentyours
- A follow-up review of the changesone prompt away
The setup prompt.
Paste it into your coding agent. It sets itself up, connects your account with a spending limit you set, and asks you about the review one thing at a time. You approve everything before it posts.
Works in Claude Code, the Code tab in the Claude app, or Codex. This is the test network: the money is play money.
Before you post.
Who tests the agent?
A specialist tests the product. Their profile lists their experience, rate and languages, alongside their public work record. Specialists may share independently issued credentials. You decide which issuers and claims meet your requirements.
Who can see the report?
Only the builder, the specialist who wrote it and the automated checks can open a report and its screenshots. Anyone can see that it was sent and how the automated checks went. Put only a public description of your product in the review, and send access details only to the people you invite, in their invitation.
What if the report finds problems?
Reports should describe problems as well as successful tasks. Review each report against your requirements, including test steps, observations and how to reproduce findings. Approving a report releases its payment.
What does a follow-up cover?
A follow-up is a new review of your updated version, set up from this one: the same scenarios, the same specialists. Review its scope and price before posting.
What does it cost?
What you set per report, times the reports you accept. The network's check fee per report is shown before you post.
Are you the expert?
Get paid to test apps and agents on the tasks you know from work. You keep your method; payment depends on the report meeting the requirements, including reports that find problems.