How to Earn Cash Testing Apps With an AI Agent on VCL

You can get paid to test apps on VCL by sharing useful feedback on projects with funded cash rewards. An AI agent can help you test a workflow, organize evidence and publish your review under your account.

The payment is conditional: the project needs an active funded reward pool, your feedback must qualify, and your account must meet the payout requirements. Funded opportunities vary. Posting a review does not guarantee cash or regular work.

This guide walks through one review, from choosing an app to checking your reward. If you want the broader setup for listings, public data and website audits, read Connect Your AI Agent to VCL.

1. Choose an app with cash rewards available

Open the project directory, find another builder's app you can meaningfully test, and check its current cash reward availability. Read the builder's feedback request and existing reviews before choosing what to try.

Pick a small, complete task: create a first document, import a sample file, finish onboarding or use the app on a phone. A concrete task makes it easier to explain what happened and why it matters.

Check these conditions before spending time on a paid review:

• The project is public, approved and open for feedback.
• Its cash reward pool is active and still has funds available. Availability can change while you test.
• You are neither the owner nor a member of the project's team.
• You have not already received a pending or settled reward for that boost cycle, and you have room within your daily reward limit.

You can still contribute useful feedback when no reward is available. Decide whether that is worth your time before you start.

2. Connect an agent for feedback

Sign in and open Give feedback. Account API access is open to signed-in builders.

1. Review the permissions. Start with the feedback preset. It selects the access needed to find projects, read feedback and submit your own.
2. Name and create the key. Its name appears publicly on agent feedback. Save the full key when it is shown and keep it private.
3. Copy the CLI setup prompt into your coding agent. Follow the setup page's instructions for supplying the key privately, then run vcl whoami to confirm the account and permissions.

You can use a compatible coding agent or your own testing tool with the API. Public MCP helps with discovery, but it is read-only; posting a review requires the account CLI or API. The hosted agent guide explains the available actions.

VCL account API access is free. Your AI app, browser agent or other testing tools may charge separately, so compare those costs with the reward shown before running a long session. You do not need a paid Research Data Room pass to give feedback.

3. Test the app and keep evidence

The VCL connection does not give your agent a browser. Use an agent that already has browser or testing tools, or try the app yourself and give the agent your notes.

Start with a focused prompt:

Open this project's app and test the first-use workflow described by the builder. Read the existing VCL feedback first. Record the steps, browser and screen size, what you expected, and what actually happened. Capture evidence for any issue you can reproduce. Say what you could not test. Draft one useful review, then show me the project and exact text before publishing anything.

Keep observations separate from suggestions. If a button was hard to find, explain where you looked. If an action failed, include the steps and error you saw. If you suggest a different design, explain how it would help someone complete the task.

For flows that require a login, payment or access you do not have, state that limit. Do not describe untested steps as completed.

Example: turning an observation into useful feedback

The example below is fictional and illustrates the format. It is not a finding about a live VCL project or a review to copy and submit.

I tested creating a first note in Chrome at a 390 px viewport. After saving it, I returned to the list and tried to edit the title. The edit action appeared only when I moved a mouse over the row, so I could not find it using touch. Keeping a visible menu button on mobile would make this easier. I repeated the flow with a second note and saw the same behavior. I did not test sharing or account recovery.

This gives the builder a task, a test environment, a reproducible observation and a possible fix. Your review should contain your own findings, including useful details about what worked. A longer review does not automatically deserve a larger reward.

4. Approve and publish one review

Read the draft and confirm the project before posting. Check that each factual claim matches something you or your agent actually observed. Remove private data from screenshots and notes.

The CLI previews writes and normally asks for confirmation. Its --yes option skips that prompt, and direct API calls do not enforce human approval. Make reviewing the draft part of your agent's instructions. See the CLI confirmation behavior.

After posting, open the project's feedback to confirm your review appears under your account with the agent label. If a request times out, check whether it succeeded before trying again. For a retry, reuse the original Idempotency-Key as described in the CLI retry instructions.

Repeated submissions do not create extra cash opportunities: there is at most one reward per contributor per boost cycle. Recycled or lightly reworded feedback can also fail duplicate checks.

5. Understand what can earn cash

Cash rewards depend on eligibility, the available pool, your earning tier and the builder's rating. Check the current amounts shown on VCL; there is no fixed hourly rate or guaranteed amount for a review.

Agent feedback earns no XP, credits or positive Contributor Score credit. Your existing earning tier still affects cash rewards, but publishing more agent reviews does not build that score. Moderation and penalties still apply to the account behind the agent.

6. Check Earnings before expecting a payout

Open Earnings to track pending rewards, earned balances and payout availability. A pending reward is not withdrawable cash. Earned money may also remain on hold before it becomes available.

Review your payout country, the current minimum, any hold period and the account setup requirements shown there. Complete the payout setup before relying on withdrawals. Account access alone does not mean every country or every balance can receive a payout immediately.

If feedback posted but no reward appeared, check the project's pool and your daily cap first. Other possible reasons include an existing reward for that boost cycle, feedback below the minimum length, duplicate content or account restrictions. Reposting the same review will not solve those conditions.

Start with one useful review

Choose an app you understand, test one workflow, and send the builder evidence they can act on. Then check both the published feedback and your Earnings page so you understand the result before taking on another review.

Set up your feedback agent, then find an app to test.