Payments and networks

How a payout settles

Once work is approved, Sage asks the job's vault to pay. The vault works out the reward, checks its limits, and either pays the person in USDC or records a refusal. That record on chain is the source of truth: Sage reads the outcome from the vault's own events, never from whether a transaction went through.

Sending money safely takes care. Sage:

• adds a margin to every gas estimate, and uses a safe fixed amount if the estimate fails
• retries a payment the network turned away, as a fresh transaction
• counts a payout as made only when the vault's own event for that exact payout appears
• never pays a submission twice: one that already carries a payout transaction is done
• holds automatic payouts while its view of the chain looks out of date

If something fails halfway, the submission goes back to waiting and the next pass picks it up. A request that dies never loses anyone's payout. See the vault's limits for what the vault checks before it pays.

Networks

Sage pays in USDC on two primary networks, Metis and GOAT Network. It also settles on Arc, under More networks, and on Starknet, for private payouts. Test networks are never shown.

On Arc, USDC is also the gas, so funding an account with USDC is all the setup there is. Jobs keep the network they were created on, and their receipts keep working.

Your account

Your account is a wallet Sage keeps for you, held by Privy, one per network. It opens on Sage's default network when you create your workspace, and you can add others from the Account page. Fund it by sending USDC to its address, from any wallet or exchange; there's a QR code to scan. The balance and activity you see are read from the chain.

Sage launches your jobs from it, inside spending rules the wallet provider enforces: no single job can be funded above your per-job cap, $50 unless you change it, anywhere from $1 to $10,000. That holds for jobs you post and for Autopilot alike.

Withdraw any amount to any address, at any time. Each withdrawal gets a one-time permit for that address and that amount, and the account locks back to its rules straight after. Stopping a job returns what's left to wherever the job was funded from.

Signed in with a Starknet wallet? You fund each job from your own wallet, and payouts settle through the Starknet vault. A Starknet sign-in can't hold a Sage account, because the account needs an Ethereum address to send leftovers back to. You can also fund any job straight from a wallet you sign in with.

Receipts

Every payout gets a public receipt at /proof/<transaction>. It shows:

• the transaction, with a link to the network's explorer
• who was paid, how much, and on which network
• the job, the mission, and the vault with its limits
• the judge's decision: its recommendation, confidence and reasons, the quotes it relied on, and any fraud signals

The evidence itself isn't published, only a fingerprint of it (a hash), so a receipt proves what was judged without exposing someone's work. Anyone can check the transaction on the explorer without asking Sage. Starknet payouts get their own receipt, which names the vault that paid.

On GOAT, Metis and Arc, when a vault refuses a payout on chain, its receipt says so: payout blocked, no funds moved. Most refusals happen before anything reaches the chain. Those are counted in public, and their reasons go to the person who submitted and to the job's owner.

Every payout also lands on the person's record of verified work, at /record/<wallet>, with each line linked to its receipt. The ledger lists them all.

Fees and gas

• No fee on payouts. The vault pays the exact reward. Sage takes nothing from your budget, or from what people are paid.
• Sage pays the payout gas. Its operator signs every payout and pays the network fee, on every network.
• Launching uses a little gas. Creating and funding a job takes a few small transactions from your account, paid in the network's own token: BTC on GOAT, METIS on Metis, USDC on Arc.
• Your first launch is covered. If your account holds the USDC for a job, or for a plan, but no gas yet, Sage sends it enough gas to go ahead, once per account.
• Collecting a private payout is free. On Starknet, Sage sends the collection and pays its fee.

How plans are billed

Free runs one live job at a time, up to $50 of work a month, with real money. Pro is $29 a month and Team $149. Programs is set up with you. People who get paid never pay.

• Pay in USDC on Metis or GOAT Network: in one click from your Sage account, or from any wallet that's yours.
• Sage reads the payment on chain and starts your plan at once. No card is needed.
• A plan runs 30 days. Paying again before it ends adds the new days on top, so paying early never loses a day.
• Upgrading starts the new plan now and credits the days left on the old one.
• A smaller plan starts when your current one ends.
• Limits count real money only: how many jobs are live, and the budget of the jobs you launched in the last 30 days, on any network.
• Limits decide what you can launch next, never what gets paid. A live job keeps paying its people, whatever happens to your plan.
• A plan belongs to a workspace. Its owner or an admin can change it.

Pricing compares the plans.