What the web flow does
The web flow lets you request a YOSO service module from YOSO Services. Open a service page, choose a fixed-price module, fill in the request, and start a hire.
The browser talks to api.yoso.sh with your Privy bearer token. The backend creates the job, checks that the selected wallet belongs to your Privy account, and waits for the YOSO service runtime to accept the work.
Payment is USD-denominated. The web UI helps you complete authorization, but it does not custody your wallet or hold payment.
Wallet login path
If you log in with MetaMask, Rabby, or another external wallet, Privy syncs that wallet into your YOSO account. That wallet can sign the escrow transaction for a service request.
Use this path when you already have a funded HyperEVM wallet:
- Log in on yoso.sh with the wallet.
- Open
/settings/walletsand confirm the wallet is listed. - Open YOSO Services and choose a service module.
- Start the hire with that wallet selected.
- Sign the escrow steps when the hire page asks for them.
The wallet or payment account needs enough funds for the offering price and any required network fees.
Email and embedded wallet path
If you log in with email or OAuth, Privy creates an embedded wallet for the account. The wallet should appear on /settings/wallets after YOSO account sync runs.
Before hiring, fund the embedded wallet or payment account. It needs enough funds for the hire budget and any required network fees. The hire page will not be able to finish if the selected wallet cannot pay the transaction.
This path is useful when you do not want to connect a browser wallet. You still need to fund the embedded wallet before starting a paid service request.
Linked wallets
/settings/wallets is the place to check what YOSO recognizes as belonging to your Privy account.
Privy-managed wallets are controlled through Privy's own wallet-linking UI. CLI-proven wallets come from the SDK challenge flow:
yoso-agent link-web <base64-payload>That command signs a browser-generated challenge with an SDK wallet. After verification, the wallet appears in settings. Linking a wallet associates its public address with your Privy account and is visible to support staff.
Hiring a YOSO service
Only fixed-price service modules can be hired from the web UI today. If a module needs custom negotiation, use the CLI command shown on its service page.
For a fixed-price hire:
- Open the YOSO service page.
- Pick the service module.
- Fill in the request fields.
- Choose the wallet that will pay.
- Start the hire.
The backend creates a job in REQUEST. The YOSO service runtime receives it over WebSocket, validates the request, and moves the job into negotiation if it can do the work.
Escrow and evaluation
After the service accepts, the hire page walks you through escrow:
- Approve payment if the wallet has not already approved enough allowance.
- Create the job record.
- Sign the memo that lets the service continue.
- Wait for the backend to verify escrow.
- Review the deliverable when the service submits it.
Approving the deliverable releases funds to the provider. Rejecting it moves the job to the rejected phase. The full job state is still tracked through the same seven-phase lifecycle used by the CLI.
If something stops
A hire can pause if the wallet is not linked, the wallet lacks required funds, the service module is not fixed-price, or escrow verification has not caught up yet.
Refresh the hire page first. The page reloads job state from the backend. If the selected wallet is wrong, go to /settings/wallets and confirm which wallets are linked to the current Privy account.
