Run your bills and payments with the agent, or build on it.
Guides for a business, from its first decision to live payments, and the API, SDK and webhooks for developers.
How a bill moves
A bill comes in
From a form, a PDF, your accounting tool, email, Chrome or the API.The agent decides
Pay now, pay later, hold it or ask for what is missing, and says why.Rules in code check it
Limits, duplicates and the payee. Code can refuse what the model proposes.Paid, or held for you
In USDC on Arc, within your limits, or a person decides.
Popular workflows
Add a supplier and one of your bills, and read what the agent decided and why. No wallet, no USDC, about five minutes.
Shadow mode: keep paying as you do, and agree or disagree with each of the agent's decisions on your real bills.
Create the workspace's wallets, fund them with USDC and take the agent live, on Arc testnet or on Arc mainnet.
The checks in code, the limits, who approves, how to stop the agent, and where money can move.
Connect Xero, QuickBooks Online or Zoho Books: open bills come in for review and become payables only when you add them.
Send an invoice from a page or a file to your workspace as a draft, for an owner or admin to add. It never pays.
Explore by topic
Every guide, by what you are doing. The sidebar holds each section's full list.
Get started
Pay bills
- Your first payment
- Pay a contractor for delivered work
- Pay early for a discount
- Ask a supplier for more time
and 8 more in the sidebar
Plan and report
- Plan the next two weeks of payments
- Plan for clients paying late
- Give each project its own budget
- Work in your own currency
and 2 more in the sidebar
Get paid
- Turn a signed deal into a collection schedule
- Share a statement with a customer
- Chase what customers owe
- Get paid sooner when cash is short
and 2 more in the sidebar
Trust and controls
- How payments are controlled
- Try a limit before you change it
- Why a payment was paid
- Share the evidence pack and receipts
and 4 more in the sidebar
Connect your tools
- Every integration at a glance
- Bring bills in from Xero
- Bring bills in from QuickBooks Online
- Bring bills in from Zoho Books
and 12 more in the sidebar
Developers
and 11 more in the sidebar
Developer resources
Create a workspace API key and make your first two requests.
Every v1 endpoint with its parameters, response and errors.
A typed client for the API and its webhooks: every page, safe retries and signature checks.
Each ledger entry pushed to your HTTPS endpoint, signed.
Markdown views, llms.txt, the OpenAPI document and an MCP server for coding agents.
The code, the contracts on Arc and these docs, open to read.
How Vestiarion works
Vestiarion is an AI agent for bills and payments, for small businesses. It reads each bill your team adds, decides whether to pay it now, pay it on a later day, hold it for a person or ask for what is missing, and writes down why. Rules in code check every payment before money moves, within limits you set, and every decision is signed into a ledger you can verify. Payments are in USDC on Arc: Arc testnet to try everything, Arc mainnet for real money.
NoteTestnet and mainnet
A workspace is on Arc testnet or on Arc mainnet, chosen when it is created. On Arc testnet nothing has market value and a new workspace simulates its payments until you take it live. On Arc mainnet, a live workspace pays real USDC. See Where money can move.
Watch it work
Short walkthroughs, recorded in the live product on Arc testnet with demo data, one for each main way of working; the Quality Lab's is of its public page. Each card opens the video at the top of its guide.
Under two minutes: a supplier and one of its bills added in shadow mode, the agent's decision and why, and a verdict.
Under two minutes: a bill the agent pays on its own, one that waits for a second person, and the record of both.
Under two minutes: shadow mode on, test USDC for your real amounts, a mirror address, and a verdict on each decision.
Under a minute and a half: a payment code refused, the limits, the people who approve, and the pause.
Under a minute and a half: wallets created, funded with testnet USDC and taken live, then a workspace on Arc mainnet.
About a minute: an invoice to a customer, its pay link and pay page, and the agent's next step on Collections.
About a minute: the bills worth paying early, an offer the agent made and the supplier accepted, and a counter.
About a minute: a freelancer paid through a one-time link, released by the agent, and milestone escrow.
About a minute: open bills from QuickBooks and Zoho Books, reviewed and added, then decided by the agent.
Under a minute and a half: an invoice PDF read into the form, a pasted list of bills, and the email and Chrome intake.
About a minute: bank payouts set up with BlindPay, the vendor's bank account, and a payout followed to the end.
Under a minute: why a payment was made, how each fact is known, and the audit log's chain check.
Under two minutes: bills come in from the Xero Demo Company, one paid in Xero is caught before it is paid twice, and one is paid on Arc testnet.
Under two minutes: a deal won in a HubSpot test account is planned, its deposit is paid and matched, and the receipt is written back to HubSpot.
Under four and a half minutes: the nodes installed from npm, a credential tested, a bill added for the agent, its decisions read, and the node as an n8n AI agent's tool.
About a minute: the lab's scenarios and what they expect, why a wrong payment fails CI, the real decisions replayed, and the quiz.
About a minute: a month's payments on one page, each with its approval, its checks and its signed entry, and the downloads.
Under a minute: vendor requests turned on, and a bill whose vendor sent its document, checked by Vestiarion and waiting for a person.
Under a minute and a half: your verdicts by decision and by vendor, the vendors that earned your rule, and a payment the agent made on its own to one.
What you can build
- A bot that reports held payments. List invoices and milestones with
status=held, and post each one with itsagentReasoning: the agent's own account of why it did not pay. - An accounting sync. Page through invoices with
direction=payableordirection=receivable, and copy each one's status, amount, counterparty, settlement time andtxHashinto your books. - An audit mirror. Copy the ledger once, keep it current with webhooks, and check each entry's signature yourself. Verify the ledger to compare your result with Vestiarion's.
- An invoice feed. Add invoices from your own system, such as an accounting tool or a billing script, and let the agent decide each one. For bills kept in Xero, QuickBooks Online or Zoho Books, bring them in from Xero, from QuickBooks or from Zoho Books with no code. For deals won in HubSpot, Pipedrive or Zoho CRM, bring them in from HubSpot, from Pipedrive or from Zoho CRM and plan their collections. For contractor work delivered in Asana, Linear or Jira, accept it from Asana, from Linear or from Jira against the criteria you agreed, and the agent pays it once a person has.
- A treasury dashboard. Show the treasury's account balances, reserve position, obligations due within 7 and 14 days and the latest liquidity forecast. Read status first, so the dashboard shows whether payments are live or simulated.
What the API is
Every endpoint is under https://www.vestiarion.xyz/api/v1. Most read; four add records, with a key given write access: a counterparty, an invoice, a milestone or a payee link. No request moves money, approves a payment, or changes or removes a record: the agent decides what is added as it decides anything typed into the console. Each request carries a workspace API key and reaches only that key's workspace. The endpoint overview lists every endpoint, and data delivery methods compares pulling with the API to receiving webhooks.