Skip to content

Legal

Terms of use

Last updated

These terms cover your use of Vestiarion, an AI agent for bills and payments that pays invoices and contractors in USDC on Arc mainnet and Arc testnet. By using it, you accept them.

Arc mainnet and Arc testnet

Each workspace runs on one network, chosen when it is created, and never moves to the other.

  • Arc mainnet: the workspace pays in real USDC. Nothing moves until an owner takes it live, typing mainnet to confirm. From then on, every payment the agent makes, or a person approves, moves real USDC, and a transfer on chain cannot be taken back.
  • Arc testnet: the workspace pays in testnet USDC and EURC from Circle's faucet. Shadow mode, hosted wallets, the USYC reserve, milestone escrow and the EURC swap run here only. Payouts to other chains run here, and on Arc mainnet to Base and Arbitrum from a workspace's own Circle account.

On both networks, the agent's payments are sent through Circle Developer-Controlled Wallets.

Where the money is

Who holds a workspace's USDC depends on the treasury its owner chose:

  • Your own wallet or passkey wallet, on Arc mainnet: the USDC stays in a wallet you hold, and Vestiarion holds no key to it. The agent pays from it only through a spending limit contract your wallet deploys and approves, within the daily and 7-day figures set in it. Your wallet changes those figures, and stops the agent by setting its approval to 0. The agent's own wallet, which holds only its gas, is in Vestiarion's Circle account.
  • Your own Circle account, on either network: the wallets are in your Circle account, and Vestiarion moves their USDC with the API key and entity secret you connect, which it stores encrypted.
  • Hosted wallets, on Arc testnet only: the wallets are created in Vestiarion's own Circle testnet account, so Vestiarion holds them.

The contracts were written for Vestiarion and have not been audited.

The software

Vestiarion's code is released under the MIT License, and its source is public on GitHub. These terms cover the hosted service; the license covers the code.

Provided as is

The service is provided as is, without warranty of any kind. It may be unavailable, have bugs, or lose data, and it depends on Arc and on Circle, which can be unavailable too. As far as the law allows, its contributors are not liable for any loss that comes from using it, including a payment the agent made within the limits your workspace set, or one made to the address recorded for a counterparty.

Your responsibilities

You are responsible for:

  • the Circle credentials you connect: they are your own, so keep them safe, and rotate them if they leak;
  • on Arc mainnet, the wallet or passkey that holds your treasury, and its recovery phrase if you saved one: Vestiarion cannot recover either, and will never ask for the phrase;
  • your counterparties' wallet addresses: the agent pays the address recorded for a counterparty, and a transfer on chain cannot be taken back;
  • your workspace's guardrails: the payment limits, the two-approval figure and the agent's spending limit you set decide what the agent may pay on its own, and what it holds for a person;
  • who you invite to your workspace, and the role you give them;
  • the accounting tool you connect, such as a Xero organisation, a QuickBooks company or a Zoho Books organization: connect only one you may give a workspace access to;
  • the CRM you connect, such as a HubSpot account, a Pipedrive company or a Zoho CRM organization: connect only one you may give a workspace access to;
  • the work tool you connect, such as your Asana, Linear or Jira, and the acceptance criteria you write: a person in your workspace, never the work tool, accepts a contractor's work against them;
  • using the service lawfully where you and the people you pay are, including any rules on paying in stablecoins.

Connected accounting tools

When an owner or admin connects Xero to a workspace, they agree, for the workspace, that Vestiarion reads the bills, suppliers and chart of accounts of the Xero organisation they pick. It writes to Xero only the payments an owner, admin or accountant approves, each booked against the bill it paid, and books a payment on Arc testnet or in shadow mode only into a Xero demo company. The bills a person adds are shown to the workspace's members and to its agent; the agent's model provider (DeepSeek, on the hosted service) sees each bill's facts to decide on it, under DeepSeek's API terms and privacy policy.

Vestiarion never uses Xero data to train or improve any AI model, and never passes it to anyone else without the workspace's say. A bill approved in Xero is not a payment approved in Vestiarion: the agent decides it within the workspace's guardrails, as any other. Disconnecting stops the reading at once; the bills already added stay with the workspace.

When an owner or admin connects QuickBooks Online to a workspace, they agree, for the workspace, that Vestiarion reads the bills, vendors and bank accounts of the QuickBooks company they connect. It writes nothing to QuickBooks, though the access Intuit grants could. A QuickBooks company connects to one workspace at a time. The bills a person adds are shown to the workspace's members and to its agent; the agent's model provider (DeepSeek, on the hosted service) sees each bill's facts to decide on it, under DeepSeek's API terms and privacy policy. Vestiarion never uses QuickBooks data, or any data from Intuit, to train or improve any AI model, and never passes it to anyone else without the workspace's say. A bill open in QuickBooks is not a payment approved in Vestiarion. Disconnecting, here or in QuickBooks, stops the reading at once; the bills already added stay with the workspace.

When an owner or admin connects Zoho Books to a workspace, they agree, for the workspace, that Vestiarion reads the bills and vendors of the Zoho Books organization they pick, and the names of the organizations they can reach. It writes nothing to Zoho Books, and the access Zoho grants is read only. The bills a person adds are shown to the workspace's members and to its agent; the agent's model provider (DeepSeek, on the hosted service) sees each bill's facts to decide on it, under DeepSeek's API terms and privacy policy. Vestiarion never uses Zoho Books data to train or improve any AI model, and never passes it to anyone else without the workspace's say. A bill open or approved in Zoho Books is not a payment approved in Vestiarion. Zoho Books does not tell Vestiarion when a bill is deleted there, so a bill you added and then deleted in Zoho Books is yours to reject in Vestiarion. Disconnecting, here or in Zoho, stops the reading at once; the bills already added stay with the workspace.

When an owner or admin connects HubSpot to a workspace, they agree, for the workspace, that Vestiarion reads the companies, contacts and deals of the HubSpot account they connect: names, amounts, close dates, pipeline stages and each company's main contact email. It writes to HubSpot only once an owner or admin allows it: then, on each HubSpot deal planned in Vestiarion, what was collected from payments confirmed on Arc, what is still owed, the last receipt, the reconciliation status and a link to the deal in Vestiarion, in a Vestiarion property group, never HubSpot's own fields; and payments on Arc testnet or in shadow mode only to a HubSpot developer test account or sandbox. A field someone changed in HubSpot is not written over until a person in Vestiarion chooses to. They are shown to the workspace's members and to its agent; the agent's model provider (DeepSeek, on the hosted service) may see a deal's facts to decide on its collections, under DeepSeek's API terms and privacy policy. Vestiarion never uses HubSpot data to train or improve any AI model, and never passes it to anyone else without the workspace's say. A deal won in HubSpot becomes a deal in Vestiarion only when a person plans it, and a change made in HubSpot afterwards changes nothing in Vestiarion until a person does. One HubSpot account connects to one workspace at a time. Disconnecting stops the reading at once; the deals already planned stay with the workspace.

When an owner or admin connects Pipedrive to a workspace, they agree, for the workspace, that Vestiarion reads the deals of the Pipedrive company they connect, with their organizations and persons: titles, values, close dates, pipeline stages, organization names and each person's email, as far as the Pipedrive user who connects can see them. Pipedrive tells Vestiarion when a deal changes, and Vestiarion then reads it again from Pipedrive. It writes to Pipedrive only once an owner or admin allows it: then, on each Pipedrive deal planned in Vestiarion, what was collected from payments confirmed on Arc, what is still owed, the last receipt, the reconciliation status and a link to the deal in Vestiarion, in deal fields Vestiarion creates, never Pipedrive's own fields. Pipedrive does not say which of its companies are developer sandboxes, so only payments made on Arc mainnet outside shadow mode are written to Pipedrive. A field someone changed in Pipedrive is not written over until a person in Vestiarion chooses to. They are shown to the workspace's members and to its agent; the agent's model provider (DeepSeek, on the hosted service) may see a deal's facts to decide on its collections, under DeepSeek's API terms and privacy policy. Vestiarion never uses Pipedrive data to train or improve any AI model, and never passes it to anyone else without the workspace's say. A deal won in Pipedrive becomes a deal in Vestiarion only when a person plans it, and a change made in Pipedrive afterwards changes nothing in Vestiarion until a person does. One Pipedrive company connects to one workspace at a time. Disconnecting revokes Vestiarion's access, which, as Pipedrive documents it, uninstalls Vestiarion from the company, and stops the reading at once; the deals already planned stay with the workspace.

When an owner or admin connects Zoho CRM to a workspace, they agree, for the workspace, that Vestiarion reads the deals of the Zoho CRM organization they connect, with their accounts and contacts: deal names, amounts, currencies, closing dates, pipelines and stages, account names and each deal's contact email, and the organization's name and currency, as far as the Zoho CRM user who connects can see them. It writes nothing to Zoho CRM, and the access Zoho grants is read only. They are shown to the workspace's members and to its agent; the agent's model provider (DeepSeek, on the hosted service) may see a deal's facts to decide on its collections, under DeepSeek's API terms and privacy policy. Vestiarion never uses Zoho CRM data to train or improve any AI model, and never passes it to anyone else without the workspace's say. A deal won in Zoho CRM becomes a deal in Vestiarion only when a person plans it, and a change made in Zoho CRM afterwards changes nothing in Vestiarion until a person does. Several workspaces may connect the same organization. Disconnecting, here or in Zoho, stops the reading at once; the deals already planned stay with the workspace.

When an owner sets a workspace up for bank payouts, they accept BlindPay's own terms, on BlindPay's page, for the workspace, and BlindPay pays the bills of the vendors given a bank account in Mexico to that account in pesos over SPEI, from the workspace's USDC. In this version a workspace is set up on BlindPay's development instance with BlindPay's test business values: payouts are tested, and no pesos reach a bank. A person approves every bank payout, after seeing BlindPay's quote of what the vendor receives; the rate and BlindPay's fees are BlindPay's. A payout BlindPay has made cannot be called back from Vestiarion.

When an owner or admin connects Asana to a workspace, they agree, for the workspace, that Vestiarion reads Asana as them: the workspaces, projects and tasks a member opens to link a task to a milestone, and for each linked task whether and when it was completed and by whom, its assignee, and the links in its description, attachments and comments. Vestiarion makes a webhook on each linked task and deletes it when the task is unlinked or Asana is disconnected; it writes nothing else to Asana. A task completed in Asana is never by itself a reason to pay: a person in the workspace accepts the work against the milestone's criteria, an acceptance by a member Vestiarion can tell is the payee is refused, and the agent then decides the payment within the workspace's guardrails. Nothing from Asana sets an amount or a payee, and a task reopened or changed after it was accepted is held for review when Vestiarion reads that before the payment is sent; keeping anyone else from accepting their own work stays the workspace's. Vestiarion never uses Asana data to train or improve any AI model, and never passes it to anyone else without the workspace's say. Disconnecting stops the reading at once; acceptances already recorded stay with the workspace.

When an owner or admin connects Linear to a workspace, they agree, for the workspace, that Vestiarion reads Linear as them, with read access only: the name of the Linear workspace, and for each issue linked to a milestone its status, whether and when it was done and by whom, its assignee, whether it was archived or deleted, its attachments and the links in its description and comments. Vestiarion writes nothing to Linear. Anyone in a Linear workspace can mark an issue done, so an issue done in Linear is never by itself a reason to pay: a person in the workspace accepts the work against the milestone's criteria, an acceptance by a member Vestiarion can tell is the payee is refused, and the agent then decides the payment within the workspace's guardrails. Nothing from Linear sets an amount or a payee, and an issue reopened, canceled or changed after it was accepted is held for review when Vestiarion reads that before the payment is sent; keeping anyone else from accepting their own work stays the workspace's. Vestiarion never uses Linear data to train or improve any AI model, and never passes it to anyone else without the workspace's say. Disconnecting stops the reading at once and revokes Vestiarion's access at Linear; acceptances already recorded stay with the workspace.

When an owner or admin connects Jira to a workspace, they agree, for the workspace, that Vestiarion reads Jira as them, on the one Jira site they connect: the site's name and address, and for each issue linked to a milestone its key, title, project, status and resolution, when it was done, and once it is done its attachments' names, its web links and the links in its description and newest comments. Vestiarion writes nothing to Jira but one webhook on the site, which only tells it that a linked issue changed, and keeps no Atlassian account ID, name or email. Anyone on a Jira site can move an issue to Done, so an issue done in Jira is never by itself a reason to pay: a person in the workspace accepts the work against the milestone's criteria, an acceptance by a member Vestiarion can tell is the payee is refused, and the agent then decides the payment within the workspace's guardrails. Nothing from Jira sets an amount or a payee, and an issue reopened, resolved as not done or changed after it was accepted is held for review when Vestiarion reads that before the payment is sent; keeping anyone else from accepting their own work stays the workspace's. Vestiarion never uses Jira data to train or improve any AI model, and never passes it to anyone else without the workspace's say. Disconnecting stops the reading at once and deletes the webhook and Vestiarion's tokens; Atlassian gives apps no way to end their own access, so the person who connected removes Vestiarion from Connected apps in their Atlassian account settings to end it there. Acceptances already recorded stay with the workspace.

When an owner or admin connects Google Sheets to a workspace, they agree, for the workspace, that Vestiarion makes spreadsheets in the Drive of the Google account they connect and writes to them the close packs an owner, admin or accountant exports, with Google's access to the files it makes only. Vestiarion never shares a spreadsheet and reads nothing from one back; who sees it is up to that Google account. Vestiarion never uses Google data to train or improve any AI model, and never passes it to anyone else without the workspace's say. Disconnecting revokes the access at Google, unless another workspace uses the same Google account, and deletes the tokens; the spreadsheets already exported stay in that Drive.

When an owner or admin connects Google Drive to a workspace, they agree, for the workspace, that Vestiarion reads the Drive of the Google account they connect with read-only access, which Google gives to every file that account can see, and reads only the one folder an owner or admin chooses: its files' names, types, sizes and dates and who last changed them, and each file added after the folder was chosen, once, to read it into a draft bill. Vestiarion writes nothing to the Drive. Anyone who can add a file to the folder can put a bill in the review list, so a file there is never by itself a reason to pay: a person in the workspace adds each bill, and the agent then decides it within the workspace's guardrails; who can add files to the folder stays the workspace's to decide. Vestiarion never uses Google data to train or improve any AI model, and never passes it to anyone else without the workspace's say. Disconnecting deletes the tokens and forgets the folder, and revokes the access at Google unless the same Google account is still connected elsewhere in Vestiarion; files already read stay in the review list.

How the agent decides

The agent's decisions are automated, within the guardrails your workspace sets. A first payment to a new address, a payment above the two-approval figure, and any payment the guardrails hold wait for a person, and some for two. A member who can approve it pays, rejects or returns it, and nobody can approve an invoice they created. Every decision is signed into the workspace's ledger with its reasoning.

A workspace on Arc mainnet starts with two approvals above 100 USDC, and an agent spending limit of 50 USDC a day and 150 USDC in 7 days. Both can be changed later, but on Arc mainnet two approvals above a figure cannot be turned off, and a daily or 7-day figure always stays.

Any member who can approve payments can pause the agent. The service can also stop payments for every workspace on Arc mainnet, or for every workspace, while their wallets and USDC stay where they are.

Acceptable use

Do not:

  • use hosted wallets or Circle's faucet for anything but running your workspace, such as collecting testnet USDC, or opening workspaces to hold more hosted wallets;
  • use the service to pay or collect money for anything unlawful;
  • try to reach another workspace's data, wallets or keys, or anyone else's account;
  • overload or attack the service, or work around its limits.

A workspace that breaks these rules may be deleted.

Changes

The service and these terms can change. When the terms change, the date at the top of this page changes with them.

Contact

Questions go to GitHub Issues. How your data is handled is on the Privacy page.