Skip to content
Vestiarion
For small businesses with work to do

Your AI agent for bills and payments

Every bill. A clear way through.

Vestiarion's agent reviews each invoice from your contractors and suppliers and tells you whether it's ready to pay, should wait, or needs you, and why. Within limits you set, it pays the ready ones in USDC.

Try it on your billsSee how it works

Start in shadow mode. Keep paying the way you do today while the agent decides on your real bills.

No wallet or funds needed.Email sign-in, no password.

How shadow mode works
Vestiarion team workspaceRead-only view
Bills & receivablesTeam payment

Loading this team's payment record

The product view stays here while its evidence is read.

View the bill's evidence
An application view of a real team bill. Only available recorded facts are shown.

The AI suggests.Your rules in code decide.

Capture invoices from Chrome

Send an invoice from any page to your workspace as a draft.

Learn about Invoice Capture
The bill's journey

The AI suggests. Your rules in code decide.

From the first read to a record you can check. These stages explain the process; the evidence below shows what was recorded for one real bill.

  1. 01 / Read

    A bill comes in.

    The agent reads the bill and its context: the amount, the supplier and the work agreed.

  2. 02 / Check

    Facts before a suggestion.

    It checks the available evidence and explains what it proposes, and why.

  3. 03 / Decide

    A reason needs permission.

    Your rules in code can hold a payment for a person. The model cannot override them.

  4. 04 / Pay

    Only within your limits.

    A ready bill can be paid in USDC when the required permissions and payment checks allow it.

  5. 05 / Record

    A trail you can check.

    Recorded decisions have signed entries. A confirmed payment has a transaction to inspect.

Loading the bill's recorded evidence

How it works

Evaluate first. Turn on payments later.

The first two steps need no wallet and no money. Most teams start in shadow mode, beside the way they pay today, and let the agent pay once its decisions match their own.

  1. Step 1

    Add your bills

    Type a bill in, drop in the PDF, import a list, or forward the email. Add the contractors and suppliers you pay.

  2. Step 2

    See what the agent decides

    For each bill: pay now, pay on a later day, hold it for a person, or ask for what's missing. Every decision comes with its reason and the checks it passed.

  3. Step 3

    Agree, then let it pay

    In shadow mode you agree or disagree with each decision and keep paying as you do today. Once you trust it, it pays in USDC within the limits you set, and holds the rest for you.

Who it's for

For small businesses that pay people for their work.

If you pay contractors, freelancers or suppliers and check each invoice by hand, the agent does the checking and shows its work.

A contractor invoices for a milestone: the checkout flow.

  1. Checks the work was delivered: its pull request merged on GitHub, or someone on your team marked it approved.
  2. Compares the amount with the milestone you agreed, and makes sure it was not paid before.
  3. Pays the contractor in USDC once it all holds. Someone new gets a link to say where they want to be paid.
How contractor payments work
Example decisionPaid

Northwind Dev

Milestone 2 of 3 · checkout flow

2,400.00USDC

What the agent checked
  • Pull request merged on GitHub: passed
  • Amount matches the milestone: passed
  • Not paid before: passed
  • Within the contractor's limit: passed

Decision: Every check passed, so the agent paid it in USDC, within the limits you set.

How the agent decides

A freelance designer sends the invoice for a campaign's assets.

  1. Matches it to the amount you agreed, and checks someone on your team approved the work.
  2. Holds it for a person when it is above that freelancer's limit, or when their payment address changed.
  3. Keeps a signed record of who approved what and when, so month end is not a hunt through chat threads.
Vestiarion for studios
Example decisionHeld for you

Kestrel Design

Campaign assets · October

6,500.00USDC

What the agent checked
  • Amount matches the fee you agreed: passed
  • Work approved by your team: passed
  • Above the freelancer's 5,000 USDC limit: failed

Decision: Blocked by code, not by the model. A person decides it in Approvals.

How the agent decides

Your hosting provider's monthly invoice arrives.

  1. Checks it against the purchase order, and that the service was received.
  2. Flags a bill that repeats one you already paid.
  3. Picks the day to pay: the last day of an early-payment discount, or the due date, never later.
When the agent pays
Example decisionScheduled

Halcyon Hosting

Servers · October

1,180.00USDC

What the agent checked
  • Matches purchase order PO-2210: passed
  • Service received: passed
  • Not a repeat of a bill already paid: passed

Decision: Set to pay on the discount's last day, to take 2% off, and never after the due date.

How the agent decides

A contributor's pull request with a bounty on it is merged.

  1. You attach the bounty with a comment on the pull request: /bounty 250.
  2. Once it is merged, the agent pays its author in USDC, within your daily limit.
  3. The payment's transaction is posted on the pull request, for anyone to check.
Bounties from GitHub
Example decisionPaid

mira-dev

Bounty on pull request 184

250.00USDC

What the agent checked
  • Bounty attached: /bounty 250: passed
  • Pull request 184 merged: passed
  • Within your daily limit: passed

Decision: Paid to its author in USDC. The transaction is posted on the pull request.

How the agent decides

It also handlesRetainers and subscriptionsBills in EURCPayees on other chainsGetting paid by clients

Payees and amounts are examples. The steps are what the agent does today.

Safety and control

The AI suggests. Your rules in code decide.

A model reads each bill and proposes what to do. Rules in code check every proposal before money moves, and can refuse it. In shadow mode nothing is paid until a person agrees, unless you let the agent pay vendors that earned it; in a live workspace the agent pays on its own only what passes every check.

Set by your team

You set the rules

Your team controls spending limits, permissions and approval requirements.

  • Limits per payee, per day and per 7 days on what the agent pays on its own.
  • Owners, admins and approvers decide what the rules hold. Whoever entered a bill approves it only if no one else can.
  • Two approvals above a figure you choose, 100 USDC by default on Arc mainnet. Pause agent stops its cycles and payments at once.

Enforced by code, and on Arc mainnet by a contract

Code enforces them

Every payment must pass deterministic checks before execution, whatever the model proposed.

  • Three-way match, screening, duplicates and every limit, checked before anything is signed or sent.
  • A first payment to a new address waits for a second person. The model cannot override a rule.
  • On Arc mainnet it pays from your wallet only through a spending-limit contract that wallet deploys. Vestiarion never holds your USDC.

Kept in the signed ledger

Every action is recorded

Decisions, approvals, holds and payments leave a traceable record.

  • Each entry is signed and linked to the one before, with the facts and reasons behind it.
  • A refusal is kept with the rule that made it, beside what the model argued.
  • Anyone in the workspace can verify the chain in the browser, or an export offline.

What happens when a rule fails?

A historical team decision · Arc testnet · shadow mode · Vestiarion team workspace ·

  1. 1 · The AI proposes

    Pay a 50.00 USDC bill today, on its early-payment deadline.

    Purchase order on file, goods received, supplier screened clear, within its limit, no duplicate.

  2. 2 · A rule checks it

    It would pass the agent's 15.00 USDC daily spending limit.

    The spending-limit contract on Arc would refuse it too (OverDailyLimit). workspace.outflow_budget

  3. 3 · The payment is held

    Refused before anything was signed or sent.

    No transaction went out. The bill waits for a person, with the reason in plain words.

Signed as ledger entry #3710 in that workspace. The limit moves only when an owner or admin changes it, never because of what a bill or the model says. View the historical case source (opens in a new tab)

What happens when a payment address changes?

A historical team payment · Arc testnet · live · Vestiarion team workspace ·

The payee lock. With it on, a changed payment address is paid only after a person confirms it, recording how they checked it with the vendor, and after any wait you set. Whoever entered the address cannot confirm it while someone else can.

An owner turns it on in Settings, with a wait of 4, 24, 48 or 72 hours, or none. A wait gives the real vendor time to notice a change they did not make. A workspace created on Arc mainnet starts with it on, with no wait.

  1. 1 · The address changes · entry #4839

    The vendor's payment address changed to a new wallet.

    The payee lock was already on, with a 4-hour wait after a change. The new wallet held 0 USDC. Then a 3.00 USDC bill from the vendor came in.

  2. 2 · Code holds it · entry #4843

    The AI decided to pay the bill. Code held it.

    No one had confirmed the new address. counterparty.address_unconfirmed

  3. 3 · A second person confirms · entry #4863

    The member who entered the address could not confirm it. A second member did.

    The first was told: "You entered or asked for this address, so someone else confirms it." The second recorded how they checked it.

  4. 4 · Code holds it again · entry #4866

    The AI decided to pay again. Code held it for the 4-hour wait.

    The address was confirmed by then, but it had changed at 11:14:01 UTC, less than an hour earlier. counterparty.cooling_off

  5. 5 · Paid · entry #4919

    After the wait, the agent paid 3.00 USDC to the confirmed address.

    The bill reopened once the wait was over, and the new wallet went from 0 to 3 USDC.

Proof on Arc testnet

3.00 USDC from the workspace's wallet to the confirmed address. Transaction 0x4978…0551 (opens in a new tab)

Block
68200055
Confirmed on chain
Recorded in the ledger

Vestiarion's code and your people hold the lock, not a contract. The transaction shows what followed: the payment settled only after both holds ended, to the confirmed address, for the bill's amount.

Each time is when that workspace's signed ledger recorded the step. The lock was turned on at 11:12:39 UTC, as entry #4832. The refused confirmation is not a ledger entry. View the payee lock case source (opens in a new tab) · How the payee lock works

Explore all safety controlsHow a decision is made, step by stepWhen the model and the policy disagree
Proof, not promises

Don't take our word for it.

Real agent decisions. Onchain payment receipts. Publicly verifiable records.

Customer activity

Businesses outside our team, never mixed with our own.

Loading customer activity

Agent decisions

Each one signed; rules in code check every payment.

Loading the agent's decisions

Loading the agent's latest decision

Payments settled

Confirmed on Arc, each network apart.

Loading the payments settled

Explore the public proof
Integrations

Keep your tools. Vestiarion connects to them.

Your accounting, CRM and team tools stay in place. Bills, won deals and finished work come in from them, nothing is paid until it passes your rules, and the tools that support it get the outcome back.

From your existing tools to a controlled payment.

With Xero · the supported workflow

  1. 1A bill comes inApproved in Xero, it waits for review. You add the ones to pay.
  2. 2Your rules check itThe agent proposes; code checks your limits and approvals. What fails waits for a person.
  3. 3It is paid on ArcIn USDC or EURC, with a transaction anyone can check.
  4. 4Xero is updatedOnce you approve the entry, the payment is booked against the bill.

Payments in shadow mode and on Arc testnet are booked only into a Xero demo company.

More of the tools your team already uses

The same checks apply whichever tool a bill comes from. Nothing a tool sends is a reason to pay by itself.

Built on Arc, with Circle

Not tools you connect: where every payment is made, and the wallets that send it.

Explore all integrations

Intuit and QuickBooks are trademarks of Intuit Inc. Zoho, Zoho Books and Zoho CRM are trademarks of Zoho Corporation Pvt. Ltd. Arc, Circle, Slack, Telegram, Xero, HubSpot, Pipedrive, Asana, GitHub and Chrome are trademarks of their respective owners. Their names and marks show what Vestiarion is built on and connects to, not an endorsement.

For developers

Runs where you already work.

For builders: connect your own applications through the REST API, the TypeScript SDK or the MCP server, with the same payment controls as the console.

  • Build on the APIRead invoices, the treasury and the ledger, or add bills, counterparties and milestones, with a workspace API key.
  • Controls still applyWhat a key adds gets every check one typed into the console gets. No key, SDK call or MCP tool approves or pays.
  • Every action on recordEach write is signed into the ledger with the key that made it, and the chain can be verified from code.
Read developer docsView on GitHub (opens in a new tab)

Also: Webhooks, CLI, GitHub app.

bash · REST API

# What the agent held, and why: each invoice carries its reasoning.curl "https://www.vestiarion.xyz/api/v1/invoices?status=held&limit=5" \  -H "Authorization: Bearer $VESTIARION_API_KEY" # The treasury: accounts, reserve, obligations and the latest forecast.curl https://www.vestiarion.xyz/api/v1/treasury \  -H "Authorization: Bearer $VESTIARION_API_KEY"

A read-only key reads the whole workspace. Adding records needs a read-and-write key, and the API never approves or pays.

QuickstartAPI reference

Questions

Everything you need to know.

From your first bill to your first payment, here's how Vestiarion works.

Explore the docs

Still have questions?

Talk to the founder on GitHub(opens in a new tab)

Can I try Vestiarion without real money?

Yes. In shadow mode you keep paying the way you do today and agree or disagree with each of the agent's decisions on your real bills: nothing is paid until a person agrees, unless you let the agent pay vendors that earned it under your rule, on Arc testnet. No wallet or funds are needed. A workspace runs on Arc testnet, where test USDC has no market value, or on Arc mainnet, where payments move real USDC. See your first decision in five minutes

Who controls the money and approves payments?

You do. The AI proposes each payment, rules in code check it against your limits before anything moves, and what they stop waits for a person in Approvals; a first payment to a new address always needs two people. You can pause the agent at any time, and on Arc mainnet money leaves only through a spending-limit contract your own wallet deploys. How payments are controlled

Can Vestiarion pay bills and contractors automatically?

Yes, in a live workspace: a bill, or a contractor milestone whose work is verified, that passes every check and fits your limits is paid on its own, on the day the agent picks. Anything else, such as a bill above its payee's limit or a first payment to a new address, waits for a person in Approvals. In shadow mode nothing is paid until someone agrees, unless the owner lets the agent pay vendors that earned it under their rule, on Arc testnet.

What happens if a payment fails?

Nothing is paid twice. Before anything is sent again, Vestiarion checks the earlier transfer with Circle, only a person can send a new one, and the bill's card says who acts and what to do next. A transfer confirmed on Arc is final and cannot be reversed: a refund is a new payment back from the payee. When a payment does not go through

Does Vestiarion work with my existing tools?

Yes. Bills come in from Xero, QuickBooks Online or Zoho Books for you to review, or by form, PDF, a bill list from your spreadsheet, email, Telegram or the API. Won deals come in from HubSpot, Pipedrive or Zoho CRM to plan their collections. Contractor work delivered in Asana is paid once a person accepts it against its criteria. Your team sees the agent's decisions in Slack or Telegram.

Do I need crypto or a wallet to get started?

No. Shadow mode needs no wallet and no USDC. A wallet and USDC matter only once you want the agent to pay bills itself; the people you pay then need an address on Arc, and someone new gets a one-time link to add theirs, with no account to make.

What does Vestiarion cost?

Trying it is free, and there is no published price yet. Shadow mode needs no wallet and no funds. Once the agent pays bills itself, each payment carries only its network fee, in USDC: on Arc, less than a cent. A payout to another chain carries that chain's transfer fee too.

Who can see our bills?

The members of your workspace. To decide on a bill, the agent sends its facts to the AI model provider this deployment uses. Public pages count workspaces and payments, never a workspace's name, a bill or a payee. What we store and who sees it

Start with one bill

See what the agent decides on your next bill.

Sign in with your email, open a workspace in shadow mode and add a bill. Its decision and the reason arrive within about a minute. No wallet or funds needed to start.

Try it on your billsSet it up with us on a call
  1. 1.Sign in by email link
  2. 2.Open a workspace, shadow mode on
  3. 3.Add one of your bills
  4. 4.Read the agent's decision and why

Already have a workspace? Sign in