Agent Operations · Reports over the material an agent holds about its own work

Settle the open question before your agent acts on it.

An agent at work keeps meeting the same questions: is this checkout clear enough to buy from, does an approval still cover the document in front of it, what actually happened in a job, are its earlier answers still true, may it share this context, which of its siblings need you, can this payout change go ahead, and what did it buy. Agent Operations answers them with eight tools: six checks and two briefs. Your agent sends the material in the call, and each tool returns a signed report with every status, match and verdict decided from it.

See the tools Read the contract

Tool access: 0.10 USDC / call
Tools: Eight tools: six checks and two briefs
Connection: /mcp
Result: Signed report

The eight tools.

Each tool reads one kind of operating material and answers one question about it. The report quotes the text or names the record behind every status, so your agent and you can see why it reads the way it does.

`wever_checkout-clarity-check`

Reads: Merchant page or checkout material as your agent pasted it: the product page text, the checkout summary, and the shipping and returns text.
The signed report states: For the final price with shipping and tax, the stock or availability, the delivery estimate and the return policy: whether the material alone settles it, marked determinable, ambiguous or absent, with the deciding text quoted and the question to ask for each open point. Live probing of an endpoint is the endpoint reliability check.
Verdicts: terms_absentterms_ambiguousall_determinable

`wever_approval-version-check`

Reads: One invoice, quote, agreement or order as it was approved, the approval record (who approved it and the version, amount, reference or digest it named) and the current version of the same document.
The signed report states: Whether the approval still covers the current version: unchanged, changed only in wording, spelling or layout (each listed), or materially changed in amount, parties, scope, dates or terms, with every material change itemized and re-approval required. Contract redlines are the contract diff check, and invoice payments the invoice payment match.
Verdicts: reapproval_requirednon_material_changesunchanged

`wever_trace-outcome-brief`

Reads: One job’s execution trace: its steps with their tool calls, the failures and recoveries recorded, which steps are required and which stand in for others, and the final outcome as recorded.
The signed report states: Every failure classified as recovered, worked around or fatal to its step, each with the record that decides it, tied to the recorded outcome, and every failure or outcome the trace leaves unexplained named. Per-job money is the job cost brief.
Verdicts: outcome_unexplainedfatal_failuresfailures_absorbedno_failures

`wever_answer-freshness-check`

Reads: Answers your agent gave earlier (the question, the answer, when, and its basis where recorded) and the policy or source change behind them, as old and new section text or a stated change.
The signed report states: Every answer whose basis the change touches, with the superseded basis quoted and each marked stale or unaffected with the reason, plus the answers it leaves untouched. Two full policy versions are compared by the terms change check.
Verdicts: stale_answerstouched_but_currentnone_touched

`wever_context-sharing-check`

Reads: One proposed sharing event (what context, with whom, in what setting and why), the owner’s sharing rules as structured rules and the consent records on file.
The signed report states: Covered by an existing consent, fresh consent needed first with exactly what changed (a new participant, a new setting, a wider scope, a new purpose, or an expired or revoked consent), or refused by a stated rule, pair by pair.
Verdicts: refused_by_rulefresh_consent_requiredcovered

`wever_agent-attention-brief`

Reads: A status list of your running agents or jobs: name, status, last activity, the pending question or blocker, the deadline and recent errors where stated, with the time of the snapshot.
The signed report states: A triage in priority order: which need you first and why (a passed deadline, an error loop, a stop on an error, a question waiting on you, a deadline at risk), which look stalled, which run fine and which finished.
Verdicts: human_neededstalled_or_unclearall_clear

`wever_payout-change-check`

Reads: One payout or fee configuration as agreed (destination, network, asset, fee rate, fixed fee, caps and scope), its approval record and change rules, a proposed change and any consent for it.
The signed report states: Change by change, whether it can take effect under the original agreement, needs the counterparty’s fresh approval first (a new destination, a higher fee, a wider scope) or falls outside the agreement. Payout readiness for one payment is the payout readiness check.
Verdicts: outside_agreementcounterparty_approval_requiredcan_take_effect

`wever_paid-access-check`

Reads: One purchase record for paid content or access (what was bought, the price, date and payment reference, the paying agent and the person it bought for) and the seller’s access terms.
The signed report states: What the buyer holds: whether access continues and until when, whether it extends to the person the agent bought for or stays with the paying agent, the conditions on it, and the proof to keep to re-establish access later.
Verdicts: access_endedterms_unclearaccess_limitedaccess_continues

How agents and people use it.

Your agent

Keeps the material its work produces: checkout pages, approved documents and their approval records, traces, earlier answers, sharing rules and consents, status lists, payout terms and purchase records.
Calls the tool that answers its question on https://weverlabs.com/mcp at the moment it matters: before it buys, pays an invoice, repeats an answer, shares context, applies a payout change or relies on something it bought.
Acts on the verdict and keeps the signed report with the work, so the next step starts from a record.

You

See at a glance which agents need you first and why, and which are running fine.
Know an invoice or agreement changed after you approved it, with each material change named, before anything is paid against it.
Verify any report against Wever's published trust key whenever you need to show where a verdict came from.

A worked example

Does the approval still cover this invoice?

The request

{
  "name": "wever_approval-version-check",
  "arguments": {
    "document_kind": "invoice",
    "approved": {
      "reference": "INV-0042",
      "version": "v1",
      "text": "Bill to: Northwind Traders\nWebsite redesign, 40 hours at $120.00 per hour.\nTotal due: $4,800.00\nDue date: 2026-12-01.\nPay to account ending 4417."
    },
    "approval": {
      "approved_by": "Dana Ortiz",
      "approved_at": "2026-10-02",
      "version": "v1",
      "amount": "4800.00 USD"
    },
    "current": {
      "reference": "INV-0042",
      "version": "v2",
      "text": "Bill to: Northwind Traders\nWebsite redesign and hosting setup, 40 hours at $120.00 per hour.\nTotal due: $5,350.00\nDue date: 2026-12-15.\nPay to account ending 9921.\nThank you for your business."
    }
  }
}

What the report returns

Verdict: reapproval_required.

Scope	"redesign" became "redesign and hosting setup"
Amount	4800.00 USD became 5350.00 USD
Dates	2026-12-01 became 2026-12-15
Terms	"4417" became "9921"

Invoice INV-0042: the approval by Dana Ortiz on 2026-10-02 does not cover the current version: 4 material changes (amount 1, scope 1, dates 1, terms 1). Re-approval is required.

The approval record names version v1 and 4800.00 USD, and both match the invoice Dana approved, so the approval itself is sound. The current invoice then moves the total, the due date and the payout account, and widens the work to hosting: four material changes, each enough on its own to need a fresh approval. The added thank-you line is listed as a wording change and needs none.

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 Operations contract lists the schemas, limits, verdicts and signing details. To probe a live endpoint, the endpoint reliability check; for a contract redline, the DiligenceOps checks; to match an invoice with its payment or ready a single payout, Commerce Assurance; for one job's money or two full versions of a policy, Job Records.

Browse all tools