Wever Labs

Agent Treasury · Reports over the money records your agent holds

Know where the money stands before your agent spends it.

An agent that pays for things collects records: transactions, balances, upcoming commitments, quotes from rails and exchanges, invoices it is owed and the fees it was charged. Agent Treasury runs eight tools over those records: five checks that hold them against your rules, schedules and requirements, and three briefs that turn them into a forecast, an aging report and a spend breakdown. Your agent sends the records in the call, and each tool returns a signed report with every total, share, rate, date and flag computed from them.

See the toolsRead the contract
Tool access
0.10 USDC / call
Tools
Eight tools: five checks, three briefs
Connection
/mcp
Result
Signed report

The eight tools.

Each tool reads one kind of record and answers one question about it. Amounts are added up as exact decimals, so totals and shares match your books to the cent; USD and USDC are read one to one, and every other currency is kept on its own.

wever_spending-anomaly-check

Reads
A list of transactions (amount, asset, counterparty, timestamp, category where given) with your budget rules: a per-transaction cap, caps per counterparty or per category for a day, week, month or in total, and the counterparties or categories spend may go to.
The signed report states
Every transaction that breaks a stated rule, every group of duplicate-looking payments (one counterparty, one amount, minutes apart) and every amount that stands out from the rest of the set, each flag naming the rule or pattern and the transactions involved. Live wallet activity comes from the wallet statement.
Verdicts
rules_brokenpatterns_foundrules_unconfirmedno_flags

wever_budget-forecast-brief

Reads
A current balance with its date, your recurring commitments (amount, cadence, next due date), recent spend totals by period, a reserve floor and a forecast horizon in days.
The signed report states
Projected outflows by week or month, split into commitments and the recent spend run rate, the date the balance first falls below the reserve floor (or the balance at the horizon end) and every assumption the forecast makes, listed plainly. It is arithmetic on your figures, with no market data or price forecast.
Verdicts
floor_crossedfloor_held

wever_payment-rail-check

Reads
Two or more payment rails you are choosing between (networks or currencies, fee shape, minimum and maximum amounts, settlement time and stated limits) and one payment you need to make (amount, currency, destination type, network, deadline).
The signed report states
Fits, fits with caveats or does not fit for each rail, with the deciding facts itemized: the currency, network and destination, the amount against the range and limits, the settlement time against the deadline and the fee computed from its shape. It names the best-fitting rail and why.
Verdicts
no_rail_fitsfits_with_caveatsrail_fits

wever_exchange-quote-check

Reads
Two or more conversion quotes (from and to assets, amounts in and out, any stated rate, fee and fee percentage, and expiry).
The signed report states
The effective rate of each quote, the ranking, the spread between the best and each other quote as a percentage with the output it gives up, each stated fee reconciled with the amounts and the stated rate, and each expired quote. Live market prices come from the market data check and the fair value brief.
Verdicts
not_comparablefee_mismatch_foundranked

wever_treasury-policy-check

Reads
Your balances by wallet label, asset and chain, with a USD value where you have one, and your treasury policy: concentration caps per asset or per chain, a minimum reserve in a named asset, and assets or chains to avoid.
The signed report states
A verdict per rule with the computed shares, every breach named with the balances behind it, shares by asset and by chain, and each address read for its format on its chain. Wallet labels are read as you wrote them.
Verdicts
breaches_foundnot_computablecompliant

wever_invoice-aging-brief

Reads
Your open invoices (counterparty, amount, currency, issue date, due date) and today’s date.
The signed report states
Totals by bucket (current, 1 to 30, 31 to 60, 61 to 90 and over 90 days overdue), the overdue invoices oldest first, the total at risk with its share of everything open, and totals by counterparty. Invoices themselves are created on the invoice rail and matched to their payments by the invoice payment match.
Verdicts
overdue_over_90overdueall_current

wever_fee-reconciliation-check

Reads
The fees you were charged (date, payer or payee, amount, fee label and the transaction amount each was charged on) and the fee schedule you agreed to (percentage rates, flat fees, minimums and caps).
The signed report states
Each expected fee recomputed from the schedule, with every overcharge, undercharge and fee that has no schedule entry itemized and totalled. To weigh a provider’s public fee claims, use the fee evidence check.
Verdicts
discrepancies_foundreconciled

wever_spend-category-brief

Reads
One period of transactions (amount, asset, counterparty, category where given, timestamp), with the period bounds when you have them.
The signed report states
Totals and shares by category, the top counterparties by spend, the largest single payments and how many transactions arrived uncategorized, for any period you choose. The month-end close pack with receipts, refunds and exceptions is the expense close pack.
Verdicts
partly_uncategorizedfully_categorized

How agents and people use it.

Your agent

  • Gathers the records it already holds: its transactions, its balance and commitments, the rails or quotes in front of it, the invoices it is owed and the fees it was charged.
  • Calls the tool that answers its question on https://weverlabs.com/mcp, with your rules, schedule or policy alongside.
  • Acts on the verdict: pauses a duplicate payment, picks the rail that fits, takes the better quote or chases the oldest invoice, and keeps the signed report as its record.

You

  • State the rules once: your budget caps, reserve floor, treasury policy and agreed fee schedule.
  • Read the report your agent brings back, with each flag naming the rule and the transactions behind it.
  • Verify any report against Wever's published trust key whenever you need to show where a number came from.

A worked example

Which of these payments needs a second look?

The request

{
  "name": "wever_spending-anomaly-check",
  "arguments": {
    "asset": "USDC",
    "rules": {
      "per_transaction_cap": "500",
      "counterparty_caps": [
        {
          "counterparty": "Example Cloud",
          "cap": "120",
          "period": "month"
        }
      ]
    },
    "transactions": [
      {
        "id": "t1",
        "amount": "49.00",
        "counterparty": "Example Cloud",
        "category": "Infrastructure",
        "timestamp": "2026-10-02T09:00:00Z"
      },
      {
        "id": "t2",
        "amount": "49.00",
        "counterparty": "Example Cloud",
        "category": "Infrastructure",
        "timestamp": "2026-10-02T09:12:00Z"
      },
      {
        "id": "t3",
        "amount": "120.00",
        "counterparty": "Data Feeds Ltd",
        "category": "Data",
        "timestamp": "2026-10-05T10:00:00Z"
      },
      {
        "id": "t4",
        "amount": "52.00",
        "counterparty": "Example Cloud",
        "category": "Infrastructure",
        "timestamp": "2026-10-16T09:00:00Z"
      },
      {
        "id": "t5",
        "amount": "2400.00",
        "counterparty": "GPU Rentals",
        "category": "Compute",
        "timestamp": "2026-10-21T15:30:00Z"
      },
      {
        "id": "t6",
        "amount": "60.00",
        "counterparty": "Data Feeds Ltd",
        "category": "Data",
        "timestamp": "2026-10-26T10:00:00Z"
      }
    ]
  }
}

What the report returns

Verdict: rules_broken.

  • over_transaction_capTransaction t5: 2400.00 USDC to GPU Rentals is over the 500.00 USDC per-transaction cap by 1900.00 USDC.
  • counterparty_cap_exceededExample Cloud totals 150.00 USDC in 2026-10, over its 120.00 USDC monthly cap by 30.00 USDC; transaction t4 crossed it.
  • possible_duplicate2 payments of 49.00 USDC to Example Cloud within 12 minutes: transaction t1, transaction t2.
  • outlier_highTransaction t5: 2400.00 USDC to GPU Rentals is above the 333.00 USDC upper fence for these 6 transactions, whose median is 56.00 USDC.

Six transactions, four flags: the 2400.00 USDC payment breaks the per-transaction cap and stands out from the set, Example Cloud passes its monthly cap on its third payment, and the first two Example Cloud payments look like one charge made twice. Raise the cap to 150 and the counterparty flag clears; the duplicate and the outlier stay until the payments themselves change.

Call it from your agent.

Connect to https://weverlabs.com/mcp and call any of the eight tools. Each call costs 0.10 USDC on Base. Eligible calls share 10 free calls per wallet over a rolling 30 days with the other paid tools. For free access, send X-Wever-Wallet-Proof signed over the exact JSON arguments and the tool route. The payment challenge supplies the x402 terms for a paid call.

Every report comes with an Ed25519 receipt signed with Wever's published trust key. The Agent Treasury contract lists the schemas, limits, verdicts and signing details. For live wallet activity, the wallet statement reads the chain; for live prices, the market data check and the fair value brief; to create and collect invoices, the invoice rail; and for invoice payment matching, the month-end close pack and public fee claims, the Commerce Assurance and DiligenceOps checks. To set the spending policy your agent runs under, start with the agent preflight checks.

Browse all tools