Skip to content

Go live

Create the workspace's wallets, fund them with USDC and take the agent live, on Arc testnet or on Arc mainnet.

A workspace starts in sandbox. Going live gives it treasury wallets on its network and sets the agent to pay from them on its own schedule. On Arc testnet they are funded with testnet USDC from Circle's faucet. On Arc mainnet they hold real USDC, or the treasury can be a wallet you hold yourself, and On Arc mainnet says what differs there. This page takes you through it, from Settings to the confirmation.

Only an owner of the workspace can take it live. Everyone else sees the workspace's status in the same place, with the line "An owner can connect Circle and take this workspace live from here."

Watch it

Under a minute and a half: wallets created, funded with testnet USDC and taken live, then a workspace on Arc mainnet. The guide below goes through each part in full.

Take a workspace live on ArcLength: The live product on Arc testnet, with demo data in the team's own workspaces. The wallet setup and going live were recorded Oct 12; the last scenes show the team's Arc mainnet workspace, which moves real USDC. Recorded Oct 17, 2026.
Read the transcript

Go live.

Wallets on Arc, funded with USDC, and an agent that pays on its own.

A new test workspace starts as a sandbox: its payments are simulated until an owner takes it live.

On Arc testnet, the simplest choice is a Vestiarion testnet wallet: no Circle account is needed.

Vestiarion creates the workspace's treasury wallets in its own Circle account.

Fund the operating wallet with testnet USDC from Circle's faucet.

Here it holds forty USDC.

Then go live. It cannot be undone from here; pausing the agent stops it paying.

Live, the agent pays on its own, within its limits, whenever something changes and every six hours.

USDC can also come in from another chain.

And idle cash can earn in USYC, Circle's tokenized money market fund, until bills fall due.

On Arc mainnet the money is real, and the treasury can be a wallet you hold yourself.

Its contract caps what the agent may move: here, fifty USDC a day and a hundred and fifty in seven days.

Only your wallet can change those figures, or stop it.

Live means the agent pays on its own, inside limits only you can change.

vestiarion.xyz/docs/guides/go-live

The same video is on YouTube.

Before you start

Until the workspace has made its first payment on its network, Arc testnet or Arc mainnet, the console shows owners and admins a Get started checklist: Create the workspace, already ticked, then add a wallet, fund it with USDC, go live, add a payee with an Arc address, Add or import a first bill, Set or confirm the limits, and the first payment. On Arc mainnet, Check payees with the payee lock follows the payee. A sandbox on Arc testnet with no wallet simulates its payments, so its checklist starts with your first bill instead: Add a supplier, Add or import a first bill, See the agent's decision and Set or confirm the limits, then, under To pay on Arc, the wallet, its USDC, going live and the first payment. Each step ticks itself off from the workspace's own records, and the next one links to the page where it is done. Approvers and accountants see checklists of their own: see Your first steps, by role. Read the guide opens Your first payment while a sandbox with no wallet waits for its first decision, this page until the workspace is live and funded, and Your first payment after that. The checklist disappears once the workspace is live and its first payment has settled.

The next step is highlighted, and each step ticks itself off.

Open your workspace and go to Settings, at /o/<slug>/settings. Go live opens the Workspace group, and its badge shows where the workspace is. The section shows one step of three at a time:

  1. Choose where the wallets live.
  2. Create the treasury wallets.
  3. Fund the operating wallet, then go live.

On Arc mainnet, step 1 can make a wallet you hold the treasury instead. Path C has its own steps 2 and 3.

1.Choose where the wallets live

Step 1 depends on the deployment:

  • When the deployment has hosted wallets, step 1 is "Choose where the wallets live". It offers a hosted testnet wallet first (path A), and your own Circle account under "Connect your own Circle account" (path B).
  • On Arc mainnet, when the deployment offers your own wallet, step 1 is "Choose where the treasury lives". It offers your own wallet first (path C), and your own Circle account under "Connect your own Circle account" (path B).
  • Otherwise, step 1 is "Connect your Circle account" and shows only the form for your own account. Follow path B.
Step 1 with hosted wallets: the testnet wallet first, your own Circle account below it.

Path A: a Vestiarion testnet wallet

You don't need a Circle account for this path. The workspace's wallets are created in Vestiarion's own Circle testnet account, in a wallet set of their own.

  1. Under "A testnet wallet, no Circle account needed", choose Use a Vestiarion testnet wallet. The line under the button reads "Hosted by Vestiarion · Arc testnet".
  2. The page confirms: "This workspace will use a Vestiarion testnet wallet; create its treasury wallets next."

Until the wallets are created, you can still change your mind. Open Connect your own Circle account instead and follow path B. Once the wallets exist, the choice is fixed, and the page says "To use your own Circle account, start a new workspace."

Path B: your own Circle account

For this path you need two values from your account in the Circle developer console:

  • An API key. For a workspace on Arc testnet, create a testnet API key in the console, because the workspace's wallets are on Arc testnet. A workspace on Arc mainnet takes a live key instead: see On Arc mainnet.
  • An entity secret. The entity secret is the key that secures developer-controlled wallets. Generate it and register it in the Circle console first, as Circle's guide to registering an entity secret describes, and keep its recovery file safe. Vestiarion does not register it for you. The field asks for "The one registered for developer-controlled wallets."

Then, in Go live:

  1. Open Connect your own Circle account, if the step shows the hosted choice first.
  2. Paste the key into API key and the secret into Entity secret.
  3. Choose Connect Circle. Circle checks the API key before anything is stored. When it accepts the key, the page says "Circle is connected." Both values are then encrypted, and they are never shown again.
Path B: paste the API key and the entity secret, then choose Connect Circle.

The entity secret itself is checked in step 2, when the wallets are created. To change either value later, open Replace Circle credentials. The new values must belong to the same Circle account, because the workspace's wallets are in it.

Connecting also adds a webhook to your Circle account, at https://www.vestiarion.xyz/api/circle/notifications, for transfers out and in. You can see it under Webhooks in Circle's console. Circle uses it to tell Vestiarion when a transfer settles, so a payment it confirms after the agent stopped waiting is recorded within seconds instead of at the next cycle, while the agent runs. Vestiarion reads the transfer back from Circle before it records anything. Removing the webhook only slows that down: the agent's cycles still settle every payment.

Path C: your own wallet

On Arc mainnet, where the deployment offers it, step 1 can put the treasury in a wallet you hold, and you need no Circle account. The workspace's agent can then pay from your wallet only through a contract your wallet deploys and approves, within the daily and 7-day figures you set in it. Vestiarion never holds your USDC. Path C has its own steps 2 and 3, described here. Sections 2 to 4 below are for paths A and B.

Step 1 offers two kinds of wallet, and leads with the one your browser suits:

  • A wallet in your browser, such as MetaMask or Rabby. When the browser has one, Your own wallet comes first, and its button names the wallet when it says its name, as in "Connect MetaMask".
  • A passkey wallet, made in Go live with your face, fingerprint or device PIN: Face ID, Touch ID, Windows Hello, or your phone. When the browser has no wallet, Create a wallet with a passkey comes first, and a line says how to use MetaMask or Rabby instead. The passkey wallet is a smart account on Arc mainnet owned by your passkey, and Vestiarion holds no key to it.
Step 1 in a browser with a wallet: the wallet first, a passkey wallet below it.
Step 1 in a browser with no wallet: the passkey first, and no error.

With a wallet in your browser

You need a wallet in your browser holding USDC on Arc mainnet: 0.50 USDC for the agent's gas, a little for the gas of your own transactions, and what the workspace will pay. If your USDC is on another chain, such as Base or Ethereum, Add USDC from another chain brings it over, under each step. Each step that uses your wallet first asks it to switch to Arc mainnet, and to add Arc mainnet if the wallet does not know it yet.

  1. Prove the wallet is yours. Choose Connect your wallet. If your browser has several wallets, choose one first. Your wallet asks you to connect, then to sign a message that names the workspace, Arc mainnet and your wallet's address. Signing sends nothing. The page confirms: "Your wallet is this workspace's treasury." Vestiarion creates the agent's wallet at the same time.
  2. Step 2 of 3, "Set up your wallet as the treasury". It shows what is set up so far, read from the chain, then the next of four steps:
    • The agent's wallet. Vestiarion created it with your choice: the only wallet that can pay through your contract, in its own Circle account. It holds only gas, never your USDC. If Circle could not create it then, the page says "The agent's wallet was not created yet; create it below." Choose Create the agent's wallet.
    • Deploy your contract. Enter a Daily figure (USDC) and a 7-day figure (USDC), or leave either empty to use that figure of the agent's spending limit. Then choose Deploy from your wallet and confirm in your wallet. Once the chain shows the contract, Vestiarion checks that it is its spending limit contract for your wallet and the agent, then records it.
    • Approve your contract. Choose Approve from your wallet and confirm. This lets the contract move your wallet's USDC, and it still pays nothing past its figures. Leave Cap (USDC) empty to approve without a cap, or enter one.
    • Give the agent its gas. On Arc mainnet the agent pays its own gas in USDC. Choose Send 0.50 USDC for gas and confirm. Each payment costs it well under 0.01 USDC, and going live needs it to hold at least 0.10 USDC.
  3. Step 3 of 3, "Check your wallet, then go live". It shows your wallet and the USDC in it, the agent's wallet and its gas, your contract and its figures, and what the agent can move: your wallet's USDC, or the approval if that is less. Type mainnet in Type mainnet to confirm, then confirm Go live, as in step 4.
Step 2, at the contract: your wallet and the agent's, then the figures to deploy it with.

While Arc mainnet confirms a transaction, the page says "Sent. Waiting for Arc mainnet to confirm it…". If you reload or close the page before the deployment or the approval is recorded, it checks the same transaction when you come back, so you do not send it twice.

Step 3: everything read from the chain, then Go live.

With a passkey

You need USDC on Arc mainnet to send to the new wallet: about 0.75 USDC for its setup at first, and what the workspace will pay once its recovery phrase is saved. It can come from a wallet on another chain: see Add USDC from another chain.

  1. Create the wallet. Choose Create with a passkey, and create the passkey when your browser asks. The page confirms: "Your passkey wallet is this workspace's treasury." Vestiarion creates the agent's wallet at the same time. If you made a passkey wallet for this workspace before, choose Use a passkey you made before instead.
  2. Step 2 of 3, "Set up your passkey wallet as the treasury". It shows what is set up so far, read from the chain, then the next of three steps:
    • Add USDC to your wallet. Send USDC on Arc mainnet to the address under Your wallet, from an exchange or another wallet, and not to the agent's wallet: setup pays the agent's gas from yours. Setup needs about 0.75 USDC: 0.50 for the agent's gas, and up to 0.25 set aside for the network fee, of which about 0.07 is spent. The rest stays with the wallet for its next confirmations. Add only this for now; send what the workspace will pay once the recovery phrase is saved. The page checks for it every 10 seconds. If your USDC is on another chain, choose Add USDC from another chain below Refresh: "From another chain, send a little more than this: Circle's fee comes out of what you send."
    • Set up with one confirmation. The Daily figure (USDC) and 7-day figure (USDC) start from the agent's spending limit; change them if you like, and enter a Cap (USDC) if you want one. Choose Set up with your passkey and confirm once. In one transaction your wallet deploys its contract, sets these figures in it, approves it, and sends the agent 0.50 USDC for gas, paying the network fee from its own USDC. If the agent's wallet holds its gas already, that part is left out. A passkey prompt shows no transaction, so before it is asked, the page builds the transaction itself from the figures it shows and checks that it matches what Vestiarion sent. Anything else is refused: "The setup Vestiarion sent is not the one this page expected; nothing was signed."
    • Save a recovery phrase. Choose Create a recovery phrase. The page shows twelve words, made in your browser and never sent to Vestiarion. They can sign for the wallet on their own: anyone who has them can move every USDC in it, so write them on paper and keep them offline. Vestiarion will never ask for them. Tick "I wrote these twelve words down and keep them offline.", and choose Register with your passkey. If this passkey is ever lost, the words let you add a new one and keep the wallet. You may instead choose Skip: I understand that losing this passkey loses this wallet. Going live needs one or the other.
    • Only when needed. If Circle could not create the agent's wallet with your choice, step 2 starts with Create the agent's wallet. If the agent holds less than 0.10 USDC of gas before you go live, step 2 shows Give the agent its gas: choose Send 0.50 USDC for gas and confirm with your passkey.
  3. Step 3 of 3, "Check your wallet, then go live", as with a wallet in your browser.
Step 2 before any USDC: the wallet's address, and what setup needs.
One confirmation deploys the contract, approves it and sends the agent its gas.
A recovery phrase before going live, or a deliberate skip.

Use your phone instead. On a computer, the passkey card and each step your passkey confirms have Use your phone instead under their button. It shows a code that opens the same page on your phone, so the passkey is made or used on the phone itself. It opens by itself on a computer with no passkey of its own, such as a Windows PC without Windows Hello. There the browser would ask your phone over Bluetooth, and can stay on "Connecting to your device". A passkey made on your phone confirms on that phone; from a computer, every confirmation goes through the same Bluetooth link, so scan the code and confirm on the phone.

On a computer with no passkey of its own, each passkey step shows the code to finish on your phone, already open.

If you reload or close the page while the setup is confirming, the page says "Your setup was sent" and checks the same setup when you come back, before anything else. If it was never recorded and you set it up again, perhaps from another browser, the same contract is used and the agent's gas is not sent twice: only one more network fee is spent. Your device or password manager keeps the passkey, and this browser keeps only its public part, so the next step signs without asking you to pick it first. In another browser the page asks you to choose the passkey, and refuses one that owns another wallet: "Use the passkey you made for it."

On either route, once the workspace is live, these points differ from What changes when you go live:

  • Every payment goes through your contract. That includes the agent's own and the ones people approve with Approve and pay or Pay now. A person's payment the contract would refuse is refused before anything is sent, with the reason, for example "Paying 30 USDC would pass the contract's daily limit of 50 USDC: 40 USDC paid so far."
  • USDC only, on Arc mainnet, Base or Arbitrum. A payment in EURC is refused: "Only USDC on Arc mainnet can be paid from your wallet's contract." A vendor on Base or Arbitrum is paid through CCTP by version 2 of your contract, which every setup deploys since Oct 19, 2026: the payment and its CCTP fee leave your wallet together, both count against the figures, and the vendor is paid in full on their chain. A version 2 contract deployed before Oct 22, 2026 pays Base only. See Pay a vendor on Base or Arbitrum from Arc mainnet. A contract deployed before then is version 1: it pays on Arc mainnet only, and refuses a payment to another chain with the same words, until you upgrade it.
  • The figures are your contract's, and your wallet changes them. In Go live, under Change what the agent may pay, enter the Daily figure (USDC) and 7-day figure (USDC), then choose Change with your passkey, or Change from your wallet with a wallet in your browser. Your wallet calls the contract's setLimits and pays its network fee. Once Arc mainnet shows the new figures, the agent's spending limit follows them, and a payment held under a lower figure is decided again. The console's agent spending limit shows them, with a link here. Each figure is USDC above 0, with up to 6 decimals. A field left empty keeps a figure the contract does not hold; this page never removes a figure the contract holds. If Arc mainnet does not answer for the figures, reload the page before you change them.
  • The console's cash is what the contract can move: your wallet's USDC, or the approval if that is less. Fund it with USDC on the Get started checklist ticks from the same figure, read from Arc mainnet when the console opens, so it is ticked as soon as the agent can move USDC.
  • To stop payments from your wallet, choose Stop the agent's payments in Go live and confirm. Your wallet sets its USDC approval for the contract to 0, so the contract can move nothing, and the agent is paused. Resume payments approves the contract again, without a cap or up to the Cap (USDC) you enter, and lifts that pause. Pausing the agent from the console works as in any workspace. Stop payments this way too before you delete the workspace: deleting it leaves your wallet's approval for the contract as it was.
  • A change waits for Arc mainnet. Once your wallet sends a change, Go live shows Your change was sent until Arc mainnet confirms it, and sends no other change until then. Choose Check again, or reload the page. The change is never sent twice.
Once live, the wallet itself changes the figures, or stops the agent.
  • Keep the agent's gas topped up. The agent cannot pay without it. Send USDC on Arc mainnet to the agent's wallet, shown in Go live, before it runs out.
  • Money coming in is not read yet. A client's payment into your wallet reaches you, but Vestiarion does not match it to its receivable yet, so the receivable stays open. Leave payment reminders off for this workspace's receivables until it does.

Upgrade your contract to pay other chains

A contract deployed before Oct 19, 2026 is version 1 of Vestiarion's spending limit contract, which pays on Arc mainnet only. Version 2 does everything version 1 does, with the same figures, and also pays a vendor on Base, and since Oct 22, 2026 on Arbitrum, through CCTP. While your contract is version 1, Go live shows Pay vendors on other chains to an owner or admin, before the workspace goes live and after. Version 2 is not audited, as version 1 is not.

  • With a wallet in your browser, three steps, each confirmed in your wallet and recorded once Arc mainnet shows it:
    1. Deploy the new contract. Your wallet deploys version 2 with the figures your contract holds now. The agent still pays through version 1.
    2. Approve the new contract. Leave Cap (USDC) empty to approve without a cap, or enter one. From then on version 2 carries every payment. The page says: "The new contract carries the agent's payments now, to other chains too. Take the old contract's approval back next."
    3. Revoke the old contract. Your wallet sets its approval for version 1 to 0, so version 1 can move none of your USDC. Until you do, Go live shows Finish the upgrade.
  • With a passkey, one confirmation: choose Upgrade with your passkey. Your wallet deploys version 2, sets the figures version 1 holds, approves version 2, and takes version 1's approval back, in that order.
  • It waits for payments in flight. A payment still in flight through version 1 must settle before version 2 takes over: version 2 starts with no record of what version 1 paid. The page says "A payment is in flight through your current contract. The new contract takes over once it settles: check again in a few minutes." and keeps what your wallet sent, to record it then.
  • The day's count starts again on chain. Version 2 counts from the moment it takes over, but the agent's spending limit in Vestiarion still counts what it paid that day, so the agent pays no more than its limit on the day of the upgrade.
  • The ledger records it as spending_limit_deployed with version 2 and the contract it replaces, spending_limit_upgraded with both contracts, and spending_limit_revoked once version 1's approval is 0. The passkey's one confirmation records the revocation inside spending_limit_upgraded.

2.Create the treasury wallets

The step is headed "Create treasury wallets". On Arc testnet it creates one wallet for each of the workspace's accounts; on Arc mainnet it creates one wallet in your own Circle account, as On Arc mainnet says. With your own Circle account, it also proves the entity secret.

Step 2, before the wallets exist.
  1. Choose Create treasury wallets.
  2. The page confirms with "Treasury wallets created: n." and lists each account's wallet address, with a button to copy it. If every account already has one, it says "Every account already has a wallet."

Under the button, a note reads "Counterparties are paid only at a real address." Each counterparty needs its address on the workspace's network before the agent can pay it. Your first payment shows where to enter it.

3.Fund the operating wallet

The step is headed "Fund the operating wallet, then go live". The agent pays from the operating wallet, so this is the wallet to fund.

  1. Under Operating wallet, copy the address with the copy button beside it.
  2. Open faucet.circle.com. As the page says, "select Arc Testnet, and paste this address", then request testnet USDC.
  3. Come back to Go live. The balance beside "USDC on chain:" is read from the chain when the step opens, and again on each Refresh. While it is 0, the page also reads it again when you return to its tab, and every 30 seconds while the tab is open, for 15 minutes, so the USDC shows without a refresh.

Testnet USDC your wallet holds on another testnet, such as Base Sepolia, can come over with Add USDC from another chain instead: see Add USDC from another chain.

Arc mainnet has no faucet: there, with your own Circle account, step 3 asks you to send USDC on Arc mainnet to the operating wallet, keeping 0.10 USDC of it for gas, as On Arc mainnet describes.

Step 3 after one faucet request: the operating wallet holds 20.00 USDC.

4.Go live

  1. Choose Go live. The step warns you first: "Going live cannot be undone from here; pausing the agent stops it paying."
  2. A dialog asks "Take this workspace live?" and lists what changes:
    • "Real testnet USDC moves when the agent pays." On Arc mainnet, this line reads "Real USDC moves when the agent pays."
    • "The agent runs every 6 hours on its own."
    • "The workspace is no longer deleted when inactive."
    • "To stop it later, pause the agent from the console."
  3. Confirm with Go live. The page says "This workspace is live." and the badge changes to "Live · paying on Arc testnet", or to "Live · hosted testnet wallet on Arc" on path A, or to "Live · paying on Arc mainnet" on Arc mainnet.
The confirmation lists what changes before anything does.

Next, make your first payment.

What changes when you go live

  • The agent runs on a schedule. A live workspace's agent runs a cycle every 6 hours on its own, with no one pressing a button. It also runs one, usually within a minute, after anything that gives it a decision to make, such as a payable added or returned to it, and within about five minutes once a payee lock's wait on a changed address ends. A scheduled cycle the workspace missed runs within about 20 minutes of its time. An owner or admin can still run one at any time with Run cycle now on the console. The console is Treasury in the app's navigation.
  • Payments move USDC on Arc from the operating wallet, within the guardrails: testnet USDC on Arc testnet, real USDC on Arc mainnet. Anything the agent will not pay waits in Approvals.
  • The workspace is kept, however long it is inactive.
  • Going live is one-way. Nothing in the app switches a live workspace back to sandbox.
A live workspace: its wallets, when it went live, and how to stop it.

To stop the agent, go to the console and choose Pause agent. You can give a reason, which is shown on every page and kept in the ledger. A paused agent runs no cycle and moves no money, and its scheduled runs are skipped. People can still pay or reject from Approvals. Owners, admins and approvers can pause the agent. Only owners and admins can start it again, with Resume agent.

On Arc mainnet

Real moneyA live workspace on Arc mainnet pays real USDC

Once it is live, the agent's payments, and the ones people approve, move real USDC within its limits. How payments are controlled says what stops a payment, and who can.

A deployment can open Arc mainnet to the people on its allowlist, or to everyone. Every other workspace stays on Arc testnet, and none moves between the two networks.

  • A workspace on Arc mainnet is chosen when it is created. On the workspaces page, a person Arc mainnet is open to chooses Arc mainnet under Network. The workspace starts with one empty operating account, and an agent spending limit of 50 USDC a day and 150 USDC in 7 days. On Arc mainnet a daily or 7-day figure always stays.
  • Two people above 100 USDC. A workspace on Arc mainnet starts with two approvals above 100 USDC, under Settings > Security. An owner can raise the figure but not turn it off there. With only one person who can approve payments, nothing above it is paid until the figure is raised or another approver is added.
  • The payee lock is on. A workspace on Arc mainnet starts with the payee lock on, with no wait: a payee's new address is paid only after someone records how they checked it, by a contact you had before, and whoever gave the address does not confirm it while someone else can. The Get started checklist adds Check payees with the payee lock, which ticks once someone confirms an address under the lock or changes it. An owner turns it off, or adds a wait, under Settings > Security.
  • It never simulates. It has no sample data and no simulated balance, and nothing moves until an owner takes it live.
  • Step 1 offers your own wallet, or takes a live key. Where the deployment offers it, your own wallet comes first, as path C describes. With your own Circle account, paste a live API key, which starts with LIVE_API_KEY, and the entity secret registered for it. They come from your Circle account once it is upgraded to production. A test key is refused there, as a live key is refused on Arc testnet. Hosted wallets do not run on Arc mainnet.
  • With your own Circle account, step 2 creates one wallet. It is an EOA on Arc mainnet, which pays its own gas in USDC, so the agent keeps 0.10 USDC of it aside for gas. A milestone release the rest cannot cover is held, and decided again once cash comes in.
  • A stuck payment holds back the ones after it. An EOA sends its payments in order, and one whose network fee was too low waits until it is resolved. Vestiarion tells you of a payment that has not confirmed 15 minutes after it was submitted to Circle, as Your first payment describes. When the console says "Circle shows it stuck.", look the transaction up in Circle's console by its hash, or contact Circle support. On path C the agent's wallet is in Vestiarion's own Circle account, so look the transaction up on Arc mainnet's explorer instead. Once it confirms or is cancelled, the later payments go out.
  • Step 3 has no faucet. With your own Circle account, send USDC on Arc mainnet to the address of the operating wallet, or bring it with Add USDC from another chain. On path C your wallet holds it already, and the same control tops it up. To go live, type mainnet in Type mainnet to confirm, then confirm Go live. From then on the agent's payments, and the ones people approve, move real USDC.
  • Every page and message names Arc mainnet. Emails to payees and clients, the pay link, the payee's page, receipts, Slack, Telegram and pull request comments name the workspace's network. The USYC reserve, escrow and Gateway, which Arc mainnet does not have, are not shown.
  • Each step needs a person Arc mainnet is open to. Anyone else is told "Arc mainnet is not open to this account yet."
  • Some features are not on Arc mainnet yet. Payouts to chains other than Base and Arbitrum, the USYC reserve, the EURC swap, escrow, enforcing the spending limit in a contract from your own Circle account, and paying in one batch each say so by name. On path C your contract carries every payment. Approving a payment from Slack is refused there: approve it in Vestiarion. The agent buys no payee history over x402 there, a payee's link offers no passkey wallet, and shadow mode runs on Arc testnet only.
  • When the deployment switches Arc mainnet off, every workspace on it holds: nothing moves, and the Go live section says "Arc mainnet is switched off on this deployment."

Add USDC from another chain

Few wallets hold USDC on Arc yet. Wherever Go live asks for USDC, Add USDC from another chain brings it from a chain where a wallet in your browser holds it: Base, Ethereum, Arbitrum, Optimism, Polygon, Avalanche, Linea, Unichain or World Chain for a workspace on Arc mainnet, and Base Sepolia, Ethereum Sepolia, Arbitrum Sepolia, Optimism Sepolia, Polygon Amoy or Avalanche Fuji for one on Arc testnet. It shows under the passkey route's Add USDC to your wallet step, under each step of setting up your own wallet, at step 3, and once the workspace is live. It sends to Your wallet on path C, and to the operating wallet on paths A and B.

It uses Circle's CCTP. Your wallet burns the USDC on the chain it is on, and Circle's Forwarding Service mints it on Arc to the workspace's wallet itself, so that wallet needs no gas for it: a new passkey wallet can receive it while it holds nothing. Your wallet signs both transactions, and Vestiarion takes no part in them and holds nothing.

  1. Choose Add USDC from another chain. Under From, choose the chain your USDC is on, and enter the Amount (USDC), with a point for decimals, such as 12.50. If your browser has several wallets, choose one. Then choose Review.
  2. Your wallet asks to connect, then to switch to that chain. The page reads the wallet's USDC there and Circle's fee, and shows what happens: the wallet it comes from, the wallet it goes to, Circle's fee, and what Arrives, at least the amount less that fee. The fee is Circle's forwarding fee, about 0.02 USDC into Arc mainnet, plus its fast transfer fee, a few hundredths of a percent of the amount at most. It is read from Circle when you review, and again when you send more than a minute later: if it rose, the page shows it and sends nothing until you choose Send again.
  3. Choose the Send button, such as Send 25.00 USDC from Base. Your wallet asks you to approve the transfer, unless you approved enough before, and then to send it. It pays that chain's gas in its own currency, such as ETH on Base, so keep a little there.
  4. The page says the transfer is on its way, with a link to it on that chain, and checks every 5 seconds. Circle mints it on Arc, usually within a minute. The page then links the mint on Arc's explorer. Your wallet shows the new USDC at once; for the operating wallet, choose Refresh beside its balance.

If you reload or close the page, this browser follows the same transfer when you come back, and nothing is sent twice. After 30 minutes without a mint, the page says which of two cases it is. If Circle has the transfer, your USDC left the other chain and is not lost: Circle's attestation lets it be minted to the workspace's wallet later, and the page keeps checking. If Circle has not seen the transfer, for example because your wallet shows it failed or was dropped, choose Forget this transfer. Choose Add more to send again once one has arrived.

Add USDC from another chain, open: the chain your USDC is on, and how much to bring.
MessageWhat to do
Enter the USDC to send with a point for decimals, such as 25 or 12.50, and at most 6 decimals.Enter the amount in USDC, with a point and no comma: 12,50 is not read as twelve and a half.
Your wallet is not on Base yet. Choose Review again: it switches to Base first.Choose Review again, and accept the switch in your wallet.
Your wallet holds no ETH on Base to pay its gas. Add a little ETH there, then choose Review again.Send a little ETH on Base to that wallet, from an exchange or another wallet: on Base, a few cents of ETH pays for both transactions, and on Ethereum it costs more. Then choose Review again. Nothing was asked of your wallet.
Your wallet holds 4.50 USDC on Base: send at most that.Enter an amount the wallet holds on that chain, or choose another chain. Nothing was asked of your wallet.
Send more than Circle's fee, at most 0.02 USDC.Enter a larger amount: what arrives is the amount less the fee.
Circle did not answer for the fee from Base. Try again in a moment.Choose Review again in a moment.
Circle offers no fast transfer from Base to Arc mainnet just now. Try again later, or from another chain.Try again later, or choose another chain under From.
Your wallet is on another chain now. Choose Send again: it switches to Base first.Choose the Send button again. An approval already confirmed is not asked for again.
Circle's fee rose since you reviewed it. Check it above, then send again.Check Circle's fee and Arrives, then choose the Send button again.
Base refused the approval. Your USDC did not leave your wallet.Look at the transaction in your wallet, for example for too little gas, then try again.
Base has not confirmed the approval yet. Choose Send again in a minute: once it is confirmed, it is not asked for again.Wait a minute, then choose the Send button again.
Base refused the transfer. Your USDC did not leave your wallet.Look at the transaction in your wallet, then try again.
Your wallet does not hold enough ETH on Base for the gas. Add a little ETH there, then send again.Add a little ETH on Base to that wallet, then choose the Send button again.
You declined it in your wallet.Nothing was sent. Choose the button again when you are ready.

Earn on idle cash with USYC

Every cycle, the agent decides whether idle USDC should earn in a reserve or come back to the operating wallet before payments fall due. Until you turn the USYC reserve on, that reserve is simulated. Turned on, the agent buys real USYC, Circle's tokenized money market fund, on Arc testnet.

  1. Get the wallets allowlisted. USYC is permissioned: Circle allowlists the wallets that may hold it. Settings → USYC reserve shows the two addresses: the operating wallet, which buys USYC, and the reserve wallet, which holds and sells it. Ask Circle Support to allowlist both for USYC on Arc testnet.

  2. Turn it on. An owner or admin chooses Turn on. Vestiarion first checks on Arc testnet that both wallets are allowlisted, and names any that is not. It also refuses while the simulated reserve still holds anything, so no simulated balance is ever counted as USYC. The change is signed in the audit log as usyc_reserve_enabled. It cannot be turned off from the app.

  3. Let the agent decide. On its next cycles:

    • A sweep. The operating wallet approves USYC's Teller contract for the USDC, then deposits it, and the USYC goes to the reserve wallet.
    • A redemption. The reserve wallet sells the USYC it needs, and the USDC comes back to the operating wallet.

    Each move is a real transaction, linked from its decision card on the console.

Payments come first. Each cycle, before it decides any payment, the agent adds up the USDC payables due today and the verified milestones waiting to be paid, except one whose USDC is locked in escrow. When the operating wallet holds less, it sells the USYC the difference needs first, so those payments are made in that cycle rather than held. The audit log records the move as cash_brought_back. A payment still held because the cash was not there is decided again at the first cycle after cash comes in: from the faucet, from a redemption, or from Bring cash back. The model that decides sweeps and redemptions is told the same: every payment leaves from the operating wallet, and the reserve's cash counts toward a payment only once it is back there.

To bring cash back yourself, an owner or admin opens Settings → USYC reserve, enters an amount in Amount (USDC), or leaves it empty for everything, and chooses Bring cash back. The reserve wallet sells that much USYC at its latest price, at any hour, and the USDC comes back to the operating wallet. The audit log records it as cash_brought_back, by you. Vestiarion then runs a cycle, so payments waiting for cash are made within a minute, unless the agent is paused.

The agent then sweeps nothing back into USYC for 24 hours, so the cash stays in the operating wallet for what you brought it back for. The written policy's reasoning says so, for example "A person brought 152.211756 USDC back from the reserve at 2026-10-05 09:05 UTC, so the agent sweeps nothing until 2026-10-06 09:05 UTC." A sweep the model chooses anyway is not made, and its decision says why. Redemptions for what falls due go on as before.

A person's payment draws on the reserve too. When Approve and pay, or Pay now on a held milestone, needs more than the operating wallet holds, it brings the difference back from the reserve first, then pays. You do not need to bring cash back yourself for it.

With the reserve on, an owner or admin can bring cash back to the operating wallet at any hour.

What to expect:

  • When USYC can be bought. Only between its daily price update, around 08:30 New York time, and 14:00 New York time, on business days. Outside that window the agent is told it cannot sweep. A sweep it decides anyway is not made, and the decision says why. Redemptions are possible at any time.
  • What the reserve is worth. Every cycle reads it from the chain: the reserve wallet's USYC at the latest price. The reserve no longer shows "simulated", and its yield is the fund's own over the last days, which is what the agent weighs a sweep against.
  • When a sweep pays. The agent sweeps only when the yield beats what the two transfers cost. It counts the yield over how long the swept cash would stay, up to 30 days: what falls due is paid from the operating wallet first, and only what it cannot cover comes back from the reserve, on its day.
  • Bounded moves. Code sets how much the agent may move. A sweep never takes the operating wallet below its buffer for what falls due within 7 days. A redemption brings back at most what falls due within 14 days needs, with a 15% cushion, and at least what the written policy redeems. The model is told these bounds. A move outside them is brought within them, and its audit log entry keeps what the model chose, as boundedByCode.
  • The contracts. USYC, its Teller and the allowlist's Entitlements contract, with their addresses, are on Contracts on Arc.
  • Fees. Buying and selling cost nothing for these wallets on Arc testnet, and Circle's Gas Station pays the network fee. The price rises day by day as the fund earns, about 3.4% a year at the end of September 2026.

When something fails

A failed step shows one of these messages under its button. You can repeat any step. Wallets created before a failure are kept, and creating the wallets again adds only the missing ones.

MessageWhat to do
Paste both the API key and the entity secret.Both fields are required. Paste each value in full.
Circle did not accept this API key.Check that you copied the whole key and that it is still active in the Circle console. It must be for the workspace's network: a test key on Arc testnet, a live key on Arc mainnet.
This Circle API key is for Arc mainnet (LIVE_API_KEY). This workspace is on Arc testnet: paste a test key (TEST_API_KEY).A workspace on Arc testnet takes a test key. In the Circle console, copy an API key from the testnet side: it starts with TEST_API_KEY.
Could not reach Circle; try again.Circle did not answer in time. Try the step again in a moment.
This workspace's wallets belong to the connected Circle account; use its credentials.The credentials belong to a different Circle account from the one that holds the wallets. Use that account's API key and entity secret.
Connect Circle first.Step 1 is not done. Choose the hosted wallet, or connect your Circle account.
Circle did not accept the entity secret; reconnect with the right one.The entity secret is not the one registered to the API key's account. Open Replace Circle credentials, paste the registered secret, then choose Create treasury wallets again.
Create the treasury wallets first.Complete step 2, then go live.
This workspace is already live.It went live already, from another tab or by another owner. Reload the page.
The stored Circle credentials cannot be read; reconnect.Paste the API key and entity secret again under Replace Circle credentials.
The Circle credentials changed while going live; try again.Someone replaced the credentials while this step was running. Reload the page and repeat the step.
This workspace has no operating wallet; it cannot take new credentials.This appears when replacing the credentials of a live workspace. The new ones cannot be proven without an operating wallet, so the stored credentials stay.
Hosted testnet wallets are not available on this deployment.Connect your own Circle account (path B). A workspace that already uses a hosted wallet pays nothing until hosted wallets are available again.
A workspace with its own Circle account or wallets cannot switch to a hosted wallet.This workspace already has Circle credentials or wallets. Continue with your own account.
All hosted testnet wallets are taken; connect your own Circle account instead.Follow path B with your own Circle account.
A hosted wallet does not run on this workspace's network yet.Hosted wallets run on Arc testnet only; a workspace on another network connects its own Circle account.
This Circle API key is for Arc testnet (TEST_API_KEY). This workspace is on Arc mainnet: paste a live key (LIVE_API_KEY).A workspace on Arc mainnet takes a live key from your Circle account's production side: it starts with LIVE_API_KEY.
Arc mainnet is not open to this account yet.Arc mainnet is open only to the people the deployment allows, while it is switched on. Use a workspace on Arc testnet, or ask to be added.
Type mainnet to confirm that this workspace pays real USDC.Type the word mainnet in Type mainnet to confirm, then choose Go live again.
This workspace pays from its owner's own wallet; it takes no Circle account.The workspace pays from a wallet its owner holds, through its spending limit contract. It never takes a Circle account of its own. To use a Circle account, start a new workspace.
Save a recovery phrase for the passkey wallet, or skip it, first.A passkey wallet asks for its recovery before it goes live. Save the recovery phrase, or choose to skip it, then choose Go live again.
Finish setting up the wallet first: its contract must be approved and its agent must hold gas.Complete step 2 of path C, Set up your wallet as the treasury: deploy the contract from your wallet, approve it, and send the agent its gas.
Paying from your own wallet is not available for this workspace on this deployment.The deployment has no agent account on Arc mainnet. Connect your own Circle account (path B).
No wallet was found in this browser. Install a wallet such as MetaMask or Rabby, then reload the page.Path C needs a wallet in your browser. Install one, add your account to it, then reload.
You declined it in your wallet.Your wallet asked, and the request was declined. Choose the step's button again and confirm in your wallet.
The signature is too old; sign again.Choose Connect your wallet again and sign within 10 minutes.
The message was signed by another wallet.Sign with the account you connected.
That address is a contract, not a wallet in your browser. Use a wallet such as MetaMask or Rabby.A smart contract account, such as a Safe, cannot be the treasury. Connect an ordinary wallet account.
Switch your wallet to the treasury's address first: it is this workspace's treasury.Your wallet is on another account. Switch it to the address under Your wallet, then choose the step again.
Set a daily figure, a 7-day figure, or both, above 0 USDC. The 7-day figure cannot be below the daily one.Correct the figures. While you set up, leave both empty to use the agent's spending limit. Once live, the contract keeps at least one figure.
That deployment was not sent from this workspace's wallet.Another account sent it. Deploy again from the wallet under Your wallet.
The chain could not be read just now; nothing was recorded. Try again in a moment.Arc mainnet did not answer for a while. Reload the page: a transaction your wallet already sent is checked again.
Circle did not create the agent's wallet; nothing was recorded. Try again in a moment.Choose Create the agent's wallet again.
No passkey was created. Nothing changed.The browser's passkey prompt was closed. Choose Create with a passkey again.
The passkey was not used. Nothing changed.The passkey prompt was closed. Choose the step's button again, and confirm with your passkey.
This browser cannot use passkeys. Use one that can, such as Chrome or Safari, or connect a wallet instead.Open Settings in a browser with passkeys, or use a wallet in your browser.
Passkeys for Vestiarion wallets work only on www.vestiarion.xyz.Open Settings at www.vestiarion.xyz, then try again.
This passkey owns another wallet (…), not this workspace's treasury (…). Use the passkey you made for it.Choose the passkey you created for this workspace's wallet.
The wallet does not hold enough USDC for this. Add a little more, then try again. Nothing was sent.Send a little more USDC on Arc mainnet to the address under Your wallet.
The wallet could not carry out the setup with what it holds. Add a little more USDC, then try again. Nothing was sent.The setup's fee is set aside before its calls run. Send a little more USDC on Arc mainnet to the address under Your wallet.
Arc mainnet did not carry out the setup; nothing was set up, and only its network fee was spent.Choose Set up with your passkey again.
The setup was sent, but it could not be recorded: …Read the reason after the colon. The setup reached Arc mainnet; if the reason is a passing one, reload the page to check it again.
Recovery is not available in this browser.Open Settings in a browser with passkeys, then choose Create a recovery phrase again.
Give the cap in USDC, above 0, or leave it empty.Enter a cap above 0, or leave Cap (USDC) empty to resume payments without one.
That transaction failed, or this workspace's wallet did not send it; nothing was recorded.The change did not come from the treasury's own wallet, or failed on chain. Do it again from Go live, with that wallet.
That transaction is not this change on the contract; nothing was recorded.The transaction did something other than the change you chose. Make the change again from Go live.
That transaction is recorded already as another change; nothing was recorded.The transaction was recorded before, as the setup or as another change. Make the change again from Go live.
Enter a daily figure above 0 USDC. The contract holds one now, and this page does not remove it.An empty field would remove that figure from the contract. Enter a figure above 0 USDC in it.
Arc mainnet did not answer for the contract's figures; reload this page to change them.Reload the page. The figures can be changed once Arc mainnet answers for them.
Arc mainnet did not carry it out; only its network fee was spent.The change failed on chain. Choose it again.
The setup could not be checked just now; it is kept and not sent twice. Check again in a moment.Arc mainnet or Vestiarion did not answer while the page checked a setup it sent. Choose Check again in a moment, or reload the page.
That did not work. Nothing was sent. Try again in a moment. The reason given: …Something unforeseen stopped the step before anything was sent; what follows "The reason given" is what Circle or the browser said. Choose the step's button again. If it happens again, reload the page or try another browser, and send that reason to support.
The setup Vestiarion sent is not the one this page expected; nothing was signed.Reload the page and try again. Nothing was signed.
Passkey wallets are not set up on this deployment.The deployment has no Circle mainnet client key. Use a wallet in your browser.
The setup failed on chain; nothing was set up.Choose Set up with your passkey again.
The wallet has not approved its contract; nothing was recorded.Choose Set up with your passkey again: it approves the contract in the same confirmation.
Going live does not run on this workspace's network yet.A network takes workspaces live only once it is opened; Arc testnet and Arc mainnet are. You can still connect Circle, create the wallet and fund it.
This workspace's wallets are hosted by Vestiarion; start a new workspace to use your own Circle account.The hosted wallets exist, so the choice is fixed. Create a new workspace to use your own account.
Could not read the balance from Circle; try again.The balance could not be read. Choose Refresh again.
Remove the sample data first. It exists only to try the agent with simulated payments.Open the console and choose Remove sample data, then connect Circle or choose a wallet host.
Something went wrong; try again.An unexpected error. Try the step again.

Edit this page on GitHub (opens in a new tab)