Frequently asked
Paid product testing, answered
The short answer. A founder points Sage at a product URL with a budget. It browses the product in a real browser, designs testing missions from what it actually saw, and pays human testers in USDC for verified evidence. Nobody reviews submissions by hand, and every payout publishes a receipt anyone can check on-chain.
What is Sage at sagepays.xyz?
An AI agent that turns one product URL and one budget into paid user-testing missions, then pays human testers in USDC for verified evidence. It runs on GOAT Network and is registered on-chain as ERC-8004 agent #79.
How do I get paid to test products on Sage?
Open the Sage marketplace, pick a mission, do the short task it describes, and write what you actually saw. There is no application and no interview. Sage checks your account against what it observed exploring the product itself and pays in USDC.
Does Sage actually pay, or is it a claim?
Every payout is an on-chain transaction on GOAT Network and publishes a receipt page anyone can open and verify. The marketplace lists recent payouts with links to those transactions, so the total paid is read from settled transfers rather than typed in.
Who pays the testers?
The agent does, autonomously, out of a campaign vault the founder funded. Each payout is a transaction with a public receipt, and the founder never reviews a submission by hand.
What stops the AI agent from overspending?
The agent proposes, a smart contract disposes. Each campaign has an on-chain vault that derives the exact reward, enforces the per-mission cap and completion limits, and rejects anything outside them. No model output can move money by itself.
Do I have to review submissions?
No, and that is the product. Sage judges each report against its own first-hand observations and pays the genuine ones. Work it cannot verify is held for a human decision rather than guessed at.
Can I write my submission in my own words or my own language?
Yes. Sage matches your account against phrases from inside the product rather than requiring particular wording, so a genuine account written in your own voice or another language still verifies. One thing to keep: write the product's own words for what you saw on screen, such as button and heading labels, because those are what Sage matches against. Copying the mission description back scores nothing.
Do I need a crypto wallet to launch a campaign?
No. The Telegram bot @sagedeputybot runs the whole loop walletless: it creates a server wallet bound to a spending policy and funds the campaign from it, so you never connect anything or leave the chat. A browser wallet on sagepays.xyz works too if you prefer one.
What does a founder give Sage to start?
A product URL, what you want proven, who should test it, and a budget in USDC. Sage browses the product itself and designs the missions, so there is nothing else to fill in.
What if my product is behind a login or a Connect Wallet screen?
Sage inspects everything it can reach, and when a wall stops it, it reads the product's own documentation to understand what is behind it, then designs missions a tester who has their own account can genuinely perform. It will never ask a tester for credentials, a seed phrase or a private key.
How long does an inspection take?
Usually about ninety seconds to a plan you can read, and you watch the browsing happen on screen while it works, page by page.
What does Sage not do?
It is not a bug bounty, a generic agent platform, or a chatbot. It turns one product and one budget into paid, verified testing, and it is judged on whether the payouts hold up.