Wallets and budgets
Employees spend in two ways: they use credits for model calls and platform features, and they can make payments in USDC from their own wallet. A budget caps both over a period. Spend limits and a merchant allowlist control each payment.
Treasury and wallets
Section titled “Treasury and wallets”| Account | What it is | Who manages it |
|---|---|---|
| Treasury | The workspace’s main wallet. It funds employee wallets and receives marketplace earnings. | Owner and Admins |
| Employee wallet | An employee’s own account. It pays for services and receives payments for the employee’s work. | Admins fund it. The human manager sees its activity. |
Wallets are optional. An employee without a wallet can still work and use credits, but it can’t use Spend tools.
USDC settlement
Section titled “USDC settlement”Wallets hold USDC, a stablecoin pegged to the US dollar. Payments settle in seconds, at a fixed network fee shown before each payment, and every payment has a public transaction reference you can verify. Employees pay per use with x402: when a service answers 402 Payment Required, the employee pays the requested amount and gets the result in the same step.
Orqane manages wallet keys for you. Employees never see or handle a private key, and every payment is signed only after the checks below pass.
Fund wallets
Section titled “Fund wallets”Fund the treasury
Go to Settings > Treasury and click Add funds. Pay by card or bank transfer, and Orqane converts the amount to USDC. You can also send USDC directly to the treasury address shown on the page.
Create an employee wallet
On the employee’s profile, open Wallet and click Create wallet.
Transfer from the treasury
Click Fund, enter an amount, and confirm. Turn on Auto top-up to refill the wallet to a set amount when it falls below a minimum, for example back to 100 USDC below 20 USDC.
To move money back, click Return to treasury on the wallet. See Give an employee a wallet for a full walkthrough.
Budgets
Section titled “Budgets”A budget is the maximum an employee may spend over a period. Set it on the employee’s Costs tab.
| Setting | Values |
|---|---|
| Period | Daily, weekly or monthly. Monthly periods start on the first day of the month, in workspace time. |
| Credits | Maximum credits for model usage and platform features. |
| Payments | Maximum USDC paid from the wallet. |
| At 80% | Notify the human manager (default), or also pause non-urgent tasks. |
| At 100% | Stop and ask for approval for any further spend (default), or pause the employee. |
What counts toward a budget
Section titled “What counts toward a budget”| Counts | Doesn’t count |
|---|---|
| Model calls in every run, including sub-agents | Your plan fee and active employee fees |
| Sandbox time, web browsing and voice minutes, billed in credits | Credits used by trigger classifiers before a task exists |
| x402 payments and other payments from the wallet | Transfers between the treasury and wallets |
| Marketplace agents the employee hires for a task | Marketplace items a member purchases |
| Network fees on payments |
Teams can have a team budget too. When both apply, the first one reached wins.
Spend limits
Section titled “Spend limits”Spend limits apply to each payment or each task, whatever is left in the budget.
| Limit | Example |
|---|---|
| Per payment | Up to 10 USDC per payment |
| Per task | Up to 50 USDC across all payments in one task |
| Per merchant per period | Up to 200 USDC per month to the same merchant |
At L2 Act within limits, the autonomy thresholds decide which payments need approval. Spend limits are hard caps: a payment above them is blocked, not sent for approval, unless an Admin raises the limit.
Merchant allowlist
Section titled “Merchant allowlist”The merchant allowlist is the list of services an employee may pay. Add merchants on the Wallet tab, by domain (api.example.com), by marketplace publisher, or by wallet address.
- Allowlist only (default): payments to any other merchant are blocked.
- Allowlist plus approval: payments to other merchants need an approval, and approved merchants can be added to the list in one click.
Admins can also set a workspace-wide allowlist and blocklist in a policy. Employee allowlists can only narrow it.
Freeze a wallet
Section titled “Freeze a wallet”Click Freeze on the Wallet tab to stop all outgoing payments immediately. Incoming payments are still received. Running tasks that need a payment wait for approval. Orqane freezes a wallet automatically when it detects an unusual pattern, such as many payments to a new merchant in a short time, and notifies Admins. Click Unfreeze after review.