Skip to content

Financial infrastructure for AI agents

Trust and accountability. Without surveillance.

Give an agent a job, not unrestricted access to your money. Vaultfire connects permissions, treasuries, payments, escrow, bonds, accounting and recovery around rules people can inspect.

Start here: how it works Explore the financial system

Read and inspect without a wallet. V3 is available for source review and local evaluation; public V3 payments, activation and partner funds remain disabled. V2 availability is separate and operation-specific.

A concrete example · not a live service

A shop gives its agent a job, not a blank cheque.

Read one approved inventory file and deliver Friday’s stock report by 17:00 UTC. The agent may not buy stock, access a bank account or message customers. Completion needs the report’s fingerprint and the named owner’s signed review.

The company backs the agreement with 100 protected example units and a separate 20-unit objective-remedy reserve; a sponsor separately offers up to 10 reward units. The agreed settlement, claim and recovery rules decide what happens next, not a score alone.

Follow the agreement and its funding rules ↗

Illustrative Accountability terms, not real-money funding or guaranteed interest. Partnership Bonds use mutual settlement and have no unilateral slash.

How the parts fit

One financial system. Six connected responsibilities.

Money needs more than a payment button. It needs clear ownership, bounded permission, accountable commitments, balanced records and a way out.

  1. Bring money in

    Start with approved deposits and top-ups in an owner-controlled treasury. Decide which network and asset are allowed.

    Treasury and incoming funds

  2. Set the agent’s limits

    Name the agent, recipient, action, amount, fee ceiling and expiry. A useful assistant does not need unlimited access to money.

    Permissions before approval

  3. Pay or hold for a task

    Make an exact authorized payment, or use escrow to hold funds under agreed completion and refund rules.

    Payments and escrow

  4. Back commitments with bonds

    Accountability and Partnership Bonds define funded commitments, evidence and exits. Principal, remedies and sponsor rewards have different jobs.

    How the bonds work

  5. Keep the books balanced

    Track what is available, reserved, pending, spent, refunded or paid in fees. A receipt alone is not the whole financial record.

    Accounting and receipts

  6. Stop access and recover

    Revoke permissions, pause affected actions and follow the supported refund or withdrawal path. Inspect an interrupted operation before retrying.

    Revocation and recovery

The connected local journey brings invoices, treasury, payments and escrow into the same chain as invoice-linked bonds, separate rewards and recovery. Other module and network lifecycles retain their own evidence; this is not one live, cross-chain service. See exactly what is implemented, integrated and still unavailable.

The flagship: bonds

Money can back a commitment. The rules still matter.

Bonds are Vaultfire’s accountability layer, not the entire financial system and not a promise of investment returns. Both families keep protected principal separate from sponsor-funded rewards; metrics cannot debit protected principal.

A

Accountability Bond

Back a clearly defined obligation.

A company funds protected principal plus a separately funded objective-remedy reserve. Only the agreed objective-breach path may use that additional, capped reserve; the protected principal is refunded in full.

Separate sponsor-funded rewards depend on the policy, approved evidence, timing and available funding. They are not guaranteed interest.

Consent, evidence and exit rules

The exact signed configuration determines the obligation, evidence source, maximum remedy, deadlines and recovery path. A poor score is not automatically a breach; a signature does not prove a real-world report is true.

Understand the three funding pots
P

Partnership Bond

Make a commitment together.

Each party signs its own terms and funds its own contribution. Principal transfers require both parties’ exact signed consent; there is no unilateral enforcement slash.

Rewards come from separate sponsor funding, never participant principal. Separate addresses do not by themselves prove independent people.

Consent, settlement and recovery rules

Activation needs the required consent and funding. Settlement, cancellation, expiry and force-exit have their own timing and withdrawal rules; money is not always immediately claimable.

Compare the two bond families

These descriptions refer to revised V3 source. Historical versions do not inherit later protections, and Base and Solana qualification must be checked separately.

Your next step

People, agents and builders have different starting points.

People

Understand it, then inspect it.

No setup, wallet or payment. Start with the plain-English guide, then save a browser-only inspection record. A failed read is safe to retry; it is never a reason to send funds.

Read the guide Try the browser check
Agents

Discover without signing.

Use a compatible MCP client for five read-only tools. No wallet is needed or authorized. If the connection fails, use the public brief and documents, not an execution or payment workaround.

Connect your assistant Read the system brief
Builders

Run the exact local journey.

Use the pinned developer tools and disposable test assets. Preserve the operation ID and private journal for recovery. Local compute and setup are your costs; no public-chain funds are required.

Run locally Evaluate a partner integration

Inspect the details

Clear explanations. Verifiable implementation.

Go deeper when you need the evidence, rather than learning the whole protocol before taking your first step.

Explore all of Vaultfire Availability and remaining gates APIs and operation-specific pricing Security and privacy boundaries
Current review source and exact download identity

Protocol source and website publication are separate identities. The source archive and sidecar identify the distributed code; neither is a security certification or authorization to handle funds.

Commit
a96486bc798f…
Tree
5f2b9856fbee…
Archive SHA-256
721da3d13e2b…
Archive bytes
62,721,050
Download current source Open sidecar inventory Website publication identity
Vaultfire

Morals over metrics. Privacy over surveillance. Freedom over control.

Inspect before you trust