DiligenceOps · Checks over what your agent hands in

Read the fine print before your agent acts on it.

Thirty-eight checks for the moments an agent is about to accept new terms, believe a claim, take an action, pick a provider, post a job, sign off on work, ask for a refund or keep paying for something; for the vendor pages it relies on: changelogs, pricing, status, docs, licenses, SLAs, benchmarks and API responses; for what a seller or partner promises: warranties, shipping, privacy, certifications, testimonials, fees, translations and environmental claims; for what a vendor commits to: SLA credits, incident reports, subprocessors, guarantees, pricing tiers and data exports; for what a provider discloses: how to report a vulnerability, how long data is kept, how accessible a service is and where AI was involved; and for what a counterparty can show: its insurance, its audit reports, its data processing agreement and its NDA. Six briefs read a contract, a policy, an invoice, meeting notes, an escrow agreement or a support conversation into its key terms. Eight Commerce Assurance tools check the records behind a payment: the instruction, the invoice it settles, the settlements you expect, the month you close, the payout you approve, the counterparty you onboard, the vendor you pick and the renewal you might miss. Each one reads the material your agent sends and returns a signed report that quotes what it found.

See the checks Read the contract

Tool access: 0.10 USDC / call
Checks: Thirty-eight checks, six briefs, eight Commerce Assurance tools
Connection: /mcp
Result: Signed report

The eight checks.

`wever_contract-diff-check`

Reads: Two versions of a terms page or contract, as plain text or HTML.
The signed report states: Every clause added, removed or materially changed, grouped under fees, refund, cancellation, ownership, liability and term, each quoted briefly from both versions. A changed figure, obligation word or negation marks a change as material; wording edits are counted on their own.

`wever_claim-evidence-check`

Reads: A claim, such as a product, listing or diligence claim, and the evidence text or excerpts offered for it.
The signed report states: Each part of the claim marked supported, unsupported or contradicted, with the evidence lines quoted from their excerpt, and the terms or figures the evidence leaves out.

`wever_policy-fit-check`

Reads: A proposed agent action in plain language and the policy or mandate it has to fit.
The signed report states: Whether the action fits, needs a condition, needs a detail or is blocked, citing each clause that allows, limits or blocks it. Caps and approval thresholds are compared to the cent, and anything the policy leaves unaddressed is named.

`wever_quote-compare`

Reads: Two or more quotes for the same job, trip leg or purchase: price, fees, tax, what is included, cancellation and refund terms, timing and validity.
The signed report states: Each total and its gap to the lowest, a like-for-like total that prices in what other quotes include, the term differences that change the real price, and any quote missing terms the others state.

`wever_job-brief`

Reads: A job described in plain language, with a budget, deadline and milestone count if you have them.
The signed report states: Deliverables and acceptance criteria quoted from the description, the budget split into milestones to the cent with due dates, an escrow shape ready to quote with wever_escrow-quote, and the questions to settle before funding.

`wever_deliverable-check`

Reads: A job’s acceptance criteria and the delivered work’s text, metadata or both, with any supporting evidence.
The signed report states: A checklist marking each criterion addressed, missing or not met, with word counts, sizes and file formats measured where the delivery states them, and the claims in the deliverable the supplied material leaves unsupported.

`wever_refund-eligibility-check`

Reads: A purchase record and the merchant’s refund policy text, with the request date and the evidence on hand.
The signed report states: Whether the claim fits the policy as written, the deadline arithmetic step by step, the item conditions and exclusions that apply, any fees, the remedy offered and the evidence the policy expects attached.

`wever_subscription-audit`

Reads: A list of subscriptions or recurring charges: name, amount, cadence, last charge date, and prior amounts and charge dates when known.
The signed report states: Duplicate services, price increases against prior amounts, charges off their cadence or charged twice, and charges whose last date is stale, with annual and monthly totals per currency.

Eight evidence checks for the pages your agent relies on.

Before an agent depends on a vendor, it reads what the vendor publishes. These checks hold that material up against itself and against the claims made from it, and quote every match and every mismatch.

`wever_changelog-check`

Reads: A changelog or release notes, as text or a page address, and the version a vendor says has shipped.
The signed report states: Every entry with its version and date, whether the claimed version has an entry of its own, and the places the log disagrees with itself: a version listed twice or out of order, a higher version dated before a lower one, or a date that is in the future or unreadable.

`wever_pricing-evidence-check`

Reads: A pricing page, as text or a page address.
The signed report states: Each tier with its prices, period, seat basis and billing cycle, its limits and features, and any price or limit the page states two ways, such as a plan at $20 on its card and $25 in the comparison table.

`wever_status-evidence-check`

Reads: A status page, as text or a page address.
The signed report states: The uptime figures and whether each names its reporting window, the incident and maintenance entries with their dates and status words, and the date of the most recent entry.

`wever_docs-freshness-check`

Reads: Documentation, as text or a page address, and the product’s current version.
The signed report states: Every mention of an older or newer version, including /v1/ style paths, and each endpoint, parameter or function the docs themselves mark deprecated, counted and quoted wherever it still appears.

`wever_license-evidence-check`

Reads: A license text.
The signed report states: The license family its marker phrases match, with the markers quoted, and whether attribution, copyleft, patent and warranty-disclaimer passages are present, each quoted briefly.

`wever_sla-evidence-check`

Reads: An SLA or service terms text.
The signed report states: The uptime commitment and its period, the service-credit terms and bands, the exclusions and the notice requirements with their deadlines, each present or missing and quoted briefly.

`wever_benchmark-evidence-check`

Reads: A benchmark or performance claim and the source text it cites.
The signed report states: Every figure in the claim and whether the source states it, with time, size and rate units converted and rounding shown, and each figure the source leaves unsupported beside the source figures in the same unit.

`wever_api-change-check`

Reads: Two samples of the same API response, before and after.
The signed report states: Fields added, fields removed, fields whose type changed and fields whose value format changed, by JSON path, using the field analysis of the data evidence check.

Eight checks for what a seller or partner promises.

A warranty, a delivery date, a privacy promise, a certificate, a quote from a customer, a fee, a translated clause or a sustainability claim each has material that should back it. These checks set the promise beside that material and quote every match and every mismatch.

`wever_warranty-check`

Reads: A warranty claim (what failed, when it was bought or delivered, how it happened, the remedy wanted) and the warranty terms.
The signed report states: The period counted to its end date and whether the claim falls inside it, whether the coverage names what failed, the exclusions the cause or issue meets, and whether the remedy is offered, each mismatch quoted from the terms.

`wever_shipping-check`

Reads: A shipping promise, as quoted or as dispatch time, delivery window and cost, and the delivery evidence: order, dispatch and delivery dates or tracking events and the charge.
The signed report states: Each deadline worked out in calendar or business days, the days dispatch or delivery ran late, and any shipping charge that differs from the promise, free-shipping thresholds included.

`wever_privacy-evidence-check`

Reads: Privacy claims and the privacy policy or document offered for them.
The signed report states: Each claim tagged collection, sharing or retention and marked supported, contradicted or never mentioned by the document, with the sentences behind it, such as a 90-day retention against a promised 30.

`wever_certification-evidence-check`

Reads: Certification, compliance or license claims, such as ISO 27001 or SOC 2 Type II, and the certificate, audit letter or register entry.
The signed report states: Each claim supported, contradicted or never mentioned, with the standard, type or level the evidence names and any validity date that has passed.

`wever_testimonial-evidence-check`

Reads: Attributed quotes or endorsements and the transcripts, reviews or articles they come from.
The signed report states: Each attribution marked as matching, differing or without a source: verbatim, with elisions, or a close version with the changed words, and whether the named person, role and organization stand with the passage.

`wever_fee-evidence-check`

Reads: A fee schedule and a quote or invoice, as text or as lines.
The signed report states: The charges the schedule does not list and the listed fees charged at a different amount, rate or currency, with the expected amount and the difference to the cent.

`wever_translation-evidence-check`

Reads: The same passage in two languages, with language tags if you have them.
The signed report states: The figures, dates, names and obligation words (must, must not, may) that differ between the versions, each quoted beside its paired passage in the other language.

`wever_environmental-evidence-check`

Reads: Environmental or sustainability claims and the report, certificate or audit offered for them.
The signed report states: Each claim supported, contradicted or never mentioned, matching figures and units, labels such as FSC or LEED Gold, and baseline or target years, and flagging a share below 100 percent behind an unqualified claim.

Six checks for what a vendor commits to.

An SLA credit, an incident report, a subprocessor list, a guarantee, a pricing tier or a data export promise each comes with material that should bear it out. These checks set the commitment beside that material, work out the figures it implies and quote every match and every mismatch.

`wever_sla-credit-check`

Reads: SLA terms and an outage or service report, as text or as the month, outages, total downtime and stated uptime, with the monthly fee if you have it.
The signed report states: The uptime worked out exactly from the period minutes and the downtime the terms count, whether the commitment was missed and by how many points, and the credit band the terms prescribe with its percentage, any cap, the credit amount and the request deadline.

`wever_incident-evidence-check`

Reads: Incident claims about duration, scope, cause and resolution, and the timeline, status updates or postmortem offered for them.
The signed report states: Each claim supported, contradicted or never mentioned, with durations compared in any unit, clock times, regions and affected shares matched, and the stated duration and start or resolution time checked against the timeline itself.

`wever_subprocessor-evidence-check`

Reads: Subprocessor claims, as a statement, a list or entries with name, purpose and location, and the agreement or subprocessor list offered for them.
The signed report states: The processors claimed but missing from the evidence, the ones the evidence adds, and the ones whose purpose or location changed, with names matched across legal suffixes and short names such as AWS.

`wever_guarantee-evidence-check`

Reads: A guarantee as promised, such as a 30-day money-back or satisfaction guarantee, and the guarantee terms.
The signed report states: Every deadline, condition and exclusion in the terms that differs from the promise: a shorter or differently counted window, conditions such as proof of purchase or original packaging, exclusions, fees deducted from the refund and credit in place of money.

`wever_pricing-tier-check`

Reads: A pricing page’s tier descriptions, as text or as tiers with price, limits and features, and the plan terms.
The signed report states: Each tier’s price, limits and features beside the terms, and the ones that differ: another price, another limit or a cap on an unlimited one, and features the terms exclude, sell as an add-on or place in another tier.

`wever_export-evidence-check`

Reads: Data export or portability claims about formats, scope and timing, and the terms or help pages offered for them.
The signed report states: Each claim supported, contradicted or never mentioned, with formats such as CSV, JSON and XLSX matched by name and durations in any unit, such as a 30-day retention against a promised 90.

Round 6

Four checks for what a provider discloses.

A security policy, a retention policy, an accessibility statement and an AI disclosure each tell your agent something it can hold a provider to. These checks read the disclosure for the elements it should carry, quote each one they find and name each one it leaves out or states only vaguely. Before your agent pays, acts under a delegation, deals with another agent or relies on an operator, the agent preflight checks read the challenge, mandate, identity record or continuity plan in the same way.

`wever_security-disclosure-check`

Reads: A security or vulnerability disclosure policy, or a security.txt file.
The signed report states: The contact method for reporting, each response timeline with its stage (acknowledgement, triage, fix or disclosure), what is in and out of scope with the host names, the safe-harbor language and any line that reserves legal action, and the PGP key, fingerprint, reporting platform or encrypted form. A security.txt file is read field by field, with whether its Expires date has passed.

`wever_data-retention-check`

Reads: A data retention and deletion policy, or the retention section of a privacy policy.
The signed report states: Each data class the policy names with the period it is kept, a period stated only as as long as necessary, or none; the deletion method, such as deletion, anonymization or overwriting; the deletion timeline after a request; and the stated exceptions, such as legal obligations, tax records or backups.

`wever_accessibility-evidence-check`

Reads: An accessibility statement or conformance claim.
The signed report states: The standard and level claimed, such as WCAG 2.2 AA, with its conformance status, the date of the claim, the evaluation method, the known limitations and a feedback contact, each quoted, and full conformance claimed beside known limitations or a claim dated more than a year before the check.

`wever_ai-disclosure-check`

Reads: Content or product material, with the disclosure you want checked or on its own.
The signed report states: Whether AI involvement is disclosed, where the disclosure sits relative to the content (opening, body or closing, or outside the material), whether it names what was generated or assisted, such as the article, images or voice, and whether it says generated, assisted or both, with hedged wording quoted.

Round 7

Four checks for what a counterparty can show.

An insurance certificate, an audit report, a data processing agreement and an NDA each stand behind a counterparty's promises. Your agent pastes the material or sends it as fields, and these checks state what it establishes and where it falls short, quoting each element they find and naming each gap, limit or one-sided term. To read your own spending policy, approval chain, the terms you are about to accept or your incident plan, the agent preflight round 3 checks read them the same way.

`wever_insurance-evidence-check`

Reads: An insurance certificate or policy excerpt, as text or as fields: the insurer, the coverage types with their limits, the effective and expiry dates, the certificate holder and any additional insured, with the coverages, limits and work dates you require.
The signed report states: What the evidence establishes, coverage by coverage with its limits and dates, and each gap against your requirements: a required coverage type absent, a limit below your requirement, a policy expired or ending inside the work window, and a certificate holder or additional insured other than the one you name.

`wever_audit-evidence-check`

Reads: An audit or attestation report excerpt, such as SOC 2 or ISO 27001, as text or as fields: the standard, the auditor, the period covered or the single date, the opinion, and the exceptions and qualifications, with the summary you were given and when your engagement starts.
The signed report states: What the report actually covers and its limits named plainly: a single date presented as period coverage, exceptions left out of the summary, a report period that ended before the engagement starts, a qualified opinion, carved-out subservice organizations and controls left to your side.

`wever_dpa-evidence-check`

Reads: A data processing agreement or its key clauses, as text or as fields: the roles of the parties, purpose limits, sub-processor terms, the breach notification window, the transfer mechanism and deletion or return on termination.
The signed report states: Each element present, missing, ambiguous or one-sided, with quotes: processing for the processor’s own purposes, sub-processors added at its discretion with no right to object, a breach window longer than 72 hours, transfers anywhere with no mechanism and copies kept after termination.

`wever_nda-evidence-check`

Reads: A non-disclosure agreement, as text or as fields: mutual or one-way, the definition of confidential information, the carve-outs, the term and survival, any residuals clause and the governing law.
The signed report states: The shape of the agreement restated plainly, with the clauses that change its real effect named: a residuals clause that swallows the protection, a definition with no carve-outs or covering only marked information, survival far beyond the term or without end, and a non-solicitation obligation.

Commerce Assurance

Eight tools for the records behind a payment.

Before money moves, after it lands and at the end of the month, your agent holds records that should agree: an instruction and its invoice, an invoice and its payment, the settlements expected and the transfers received, a payout and its approvals, a new counterparty's packet, competing proposals and the renewal terms of a contract. Your agent sends the records in the call, and each tool returns a signed report with every figure, difference, total and deadline computed from them. For live wallet activity, the wallet statement reads the chain; for research on a counterparty, the counterparty brief; and for every dated obligation in a document, the deadline check.

`wever_payment-instruction-check`

Reads: A payment instruction as fields or text: the network, asset, recipient address, amount, currency, reference or memo and expiry, with the invoice or order it pays and your payer policy when you have them.
The signed report states: The instruction restated, with each element held against the others, the invoice and your policy: an address whose format does not fit the network, a token address that is not USDC on that network, a checksum that points to a mistyped character, an amount that differs from the invoice or passes your maximum, a missing reference and an expired instruction. Addresses are read for their format on the named network.

`wever_invoice-payment-match`

Reads: One invoice, one payment or transfer record and, when you have it, the receipt.
The signed report states: Exact, partial or mismatch, with each compared element itemized: the amount short or over and by how much, the currency, the payer and payee by name and account, the reference, and the payment date against the issue and due dates.

`wever_settlement-reconciliation-check`

Reads: A list of the settlements you expect and a list of the transfers you received.
The signed report states: Totals for each side and the net per currency, then every item tied to its reference: matched, missing, duplicate, short or overpaid with the amount, and each transfer that matches nothing.

`wever_expense-close-pack`

Reads: One period of payment, receipt and refund records.
The signed report states: A month-end close pack: totals by counterparty, by tool or service and by category, each net of its refunds; the exceptions, such as payments with no receipt, duplicate payments and refunds that tie to no payment; and a plain close summary. Live wallet activity for the same period comes from wever_wallet-statement.

`wever_payout-readiness-check`

Reads: A payout request with its invoice, supporting documents, approvals and approval policy.
The signed report states: Ready or not ready, with every missing or inconsistent element named: a recipient other than the invoice payee, a wallet in the wrong format, an amount above the invoice or the policy maximum, a vague purpose, a missing document, and approvals that do not count, such as a requester approving their own payout. The report is the readiness record for whoever runs the payout.

`wever_counterparty-onboarding-check`

Reads: A counterparty onboarding packet: legal or agent identity, contact, wallet or bank payment route, terms acceptance and the compliance fields you hold.
The signed report states: Complete, incomplete or inconsistent, element by element: email, phone and website formats, the wallet format or the IBAN, SWIFT/BIC and routing checks, an account holder other than the legal name, the terms version and date, and compliance statuses still open. Research on the counterparty itself comes from wever_counterparty-brief.

`wever_procurement-decision-brief`

Reads: Two or more vendor proposals as fields or text, with your priorities and budget when you have them.
The signed report states: A side-by-side comparison across price (annualized and over the term), term, service levels, security and data terms, liability, renewal and support; each vendor’s evidence gaps; and a recommendation with its rationale and the conditions that would change it.

`wever_renewal-notice-check`

Reads: Agreement text or renewal fields, with today’s date.
The signed report states: The renewal type, the current term rolled forward through any automatic renewals, the notice period and the notice deadline computed from the dates, price-change terms and the termination window, with ambiguous or missing renewal language flagged. Other document deadlines come from wever_deadline-check.

Six briefs for the documents your agent is about to rely on.

Each brief reads one excerpt and returns its working terms, every value quoted with where it sits, and lists the terms the excerpt leaves unstated. The invoice brief also checks the invoice’s arithmetic to the cent.

`wever_contract-brief`

Reads: One contract excerpt.
The signed brief states: The parties and their roles, the term with its dates and length, renewal with its kind, period and notice, termination with its grounds, notice, cure period and fees, and payment with amounts, due terms, frequency and late charges, each quoted, plus what the excerpt leaves unstated.

`wever_policy-brief`

Reads: One policy excerpt, such as an insurance, warranty or service policy.
The signed brief states: The coverage, the exclusions as a list, the limits by kind (per claim, aggregate, per item, deductible, copay) with their amounts, and the conditions a claim must meet with their time limits, each quoted, plus what the excerpt leaves unstated.

`wever_invoice-brief`

Reads: One invoice document.
The signed brief states: The parties, invoice number, dates, payment terms, line items and totals, with the arithmetic checked to the cent: quantity times unit price, the subtotal, tax at its rate, the total, the balance and the due date against the net terms.

`wever_meeting-brief`

Reads: Meeting notes or a transcript excerpt.
The signed brief states: The participants, the decisions, the action items with their owners and due dates, and the open questions, each quoted, plus the action items that have no owner or no due date.

`wever_escrow-brief`

Reads: One escrow agreement excerpt.
The signed brief states: The parties with their escrow roles, the amount held, the release conditions, how and when funds are released, the return of funds, the dispute path, the agent’s fee and dated deadlines, each quoted, plus what the excerpt leaves unstated.

`wever_support-brief`

Reads: One support conversation excerpt: a chat, email thread or ticket.
The signed brief states: Who speaks for support and who is the customer, the issue raised, the current status, every promise support made with its amount and deadline, and the stated next step with who owns it.

What each check reads.

Most checks work from the material in the call. The changelog, pricing, status and docs freshness checks also take a page address: Wever reads that one public page once, the same way the terms evidence check reads a terms page, and checks it exactly as it would pasted text. The job brief returns an escrow shape you can quote and fund through the rail, the quote comparison returns totals and term differences for the booking you make, and the refund check lists the evidence to attach when you file.

The evidence checks work by matching words, figures, dates and named items between the texts your agent submits. Each report says so in one plain line beside what it read, so the reader knows exactly how every finding was reached.

The report is the whole output. Your agent decides what to do with it, and the receipt lets anyone confirm later that the report is the one Wever signed.

A short worked example

Is this refund still in time?

The request

{
  "name": "wever_refund-eligibility-check",
  "arguments": {
    "purchase": {
      "item": "Wireless headphones",
      "amount": "129.99",
      "currency": "USD",
      "purchased_at": "2026-10-08",
      "delivered_at": "2026-10-10",
      "condition": "unused"
    },
    "policy": "You may return unused items within 30 days of delivery for a full refund. Please include your order number and receipt.",
    "claim": {
      "requested_at": "2026-11-04",
      "evidence_available": [
        "order number",
        "receipt"
      ]
    }
  }
}

What the report returns

Verdict: fits the policy as written.
Arithmetic: delivery on 2026-10-10, plus 30 days, is a deadline of 2026-11-09; the request on 2026-11-04 is 25 days after delivery, with 5 days to spare.
Conditions: the policy asks for unused items, and the purchase record says unused.
Evidence: the order number and receipt the policy expects are both on hand.

The same request after the deadline returns the days it is late, and a used item returns the condition it misses.

A second worked example

Does the benchmark say what the claim says?

The request

{
  "name": "wever_benchmark-evidence-check",
  "arguments": {
    "claim": "v2 serves 3,600 rps with a 220 ms p99 latency, 3x the throughput of v1.",
    "source": "Throughput rose from 1,200 rps on v1 to 3,600 rps on v2. The p99 latency was 219.6 ms on v2.",
    "source_label": "October benchmark"
  }
}

What the report returns

Verdict: some figures are unsupported.
Figures: 3,600 rps appears in the source, in the throughput sentence; 220 ms rounds from the source’s 219.6 ms p99 latency.
Unsupported: the source does not state 3x. It states 1,200 rps and 3,600 rps, and the comparison between them is left to your agent.
Basis: one line in the report says it matches words, figures, dates and named items between the submitted texts.

Send the full benchmark report as the source and the same check quotes the sentence behind every figure the claim uses.

A third worked example

Did the delivery keep the promise?

The request

{
  "name": "wever_shipping-check",
  "arguments": {
    "promise": {
      "text": "Orders ship within 1 business day and arrive in 3-5 business days. Free shipping on orders over $50."
    },
    "evidence": {
      "ordered_at": "2026-10-30",
      "order_total": "64.00",
      "charged": "5.99",
      "currency": "USD",
      "events": [
        {
          "at": "2026-11-03T09:00:00Z",
          "status": "Picked up by carrier"
        },
        {
          "at": "2026-11-11T15:00:00Z",
          "status": "Delivered"
        }
      ]
    }
  }
}

What the report returns

Verdict: mismatches found.
Dispatch: an order on Friday 2026-10-30 was due out by 2026-11-02; the carrier picked it up on 2026-11-03, 1 business day late.
Delivery: the 3-5 business day window closed on 2026-11-06; delivery on 2026-11-11 came 3 business days past it.
Cost: the order total of 64.00 is over the 50.00 threshold, so shipping was promised free; 5.99 was charged.

Business days run Monday to Friday, and the report shows each deadline it computed, so the arithmetic can be checked line by line.

A fourth worked example

Does the outage earn a service credit?

The request

{
  "name": "wever_sla-credit-check",
  "arguments": {
    "terms": "Uptime commitment: 99.9% monthly uptime.\nService credits: less than 99.9% but at least 99.0%, 10% of the monthly fee; less than 99.0%, 25% of the monthly fee.\nScheduled maintenance is excluded from downtime.\nCredit requests must be submitted within 30 days of the end of the month.",
    "report": {
      "month": "2026-10",
      "outages": [
        {
          "started_at": "2026-10-14T09:12:00Z",
          "ended_at": "2026-10-14T11:40:00Z",
          "description": "API outage"
        },
        {
          "started_at": "2026-10-21T02:00:00Z",
          "ended_at": "2026-10-21T04:00:00Z",
          "kind": "maintenance"
        }
      ]
    },
    "monthly_fee": "1200.00",
    "currency": "USD"
  }
}

What the report returns

Verdict: the commitment was missed.
Uptime: October has 44,640 minutes; less the 148-minute API outage, 44,492 minutes were up, an uptime of 99.6685%. The 2-hour maintenance window is set apart because the terms exclude scheduled maintenance.
Threshold: 0.2315 points short of the 99.9% commitment.
Credit: the band from 99.0% to below 99.9% applies, 10% of the 1,200.00 USD fee, a credit of 120.00 USD.
Deadline: the request is due within 30 days of the end of the month, by 2026-11-30.

Send the outages as a status page history or an incident report instead and the same check reads the times from the text.

A fifth worked example

Does the disclosure say what AI made?

The request

{
  "name": "wever_ai-disclosure-check",
  "arguments": {
    "material": "Five ways to cut your cloud bill\n\nRight-size instances before you buy reserved capacity, and turn off idle environments at night.\n\nSome content may have been created with AI.",
    "disclosure": "Some content may have been created with AI."
  }
}

What the report returns

Verdict: disclosed, not specific.
Placement: the disclosure sits after the content, in paragraph 3 of 3, so a reader meets the advice before the disclosure.
Wording: it refers only to "content", so it names nothing that was generated or assisted; "created" reads as generated.
Hedging: "may have been" leaves open whether AI was used at all.

Send a disclosure such as "The header image was generated with Midjourney." at the top of the material and the same check returns disclosed and specific, in the opening, naming the image.

A sixth worked example

Does the audit report cover what the summary says?

The request

{
  "name": "wever_audit-evidence-check",
  "arguments": {
    "report": "SOC 2 Type 1 report on controls as of June 30, 2026.\nIn our opinion, the controls were suitably designed as of June 30, 2026.\nService auditor: Northbridge Assurance LLP.",
    "context": {
      "summary": "SOC 2 Type II covering the past year.",
      "engagement_starts": "2026-12-01"
    }
  }
}

What the report returns

Verdict: limits_found.
Establishes: SOC 2 Type 1, auditor Northbridge Assurance LLP, controls as of 2026-06-30, unqualified opinion.
point_in_time_presented_as_period: the summary presents the report as covering a period, but the report covers a single date.
period_ended_before_engagement: the report is dated 2026-06-30, 154 days before the engagement starts on 2026-12-01.

Send a Type 2 report for a period that runs up to the engagement and the same check returns what that period covers, with any exceptions it notes.

A seventh worked example

Does the payment settle the invoice?

The request

{
  "name": "wever_invoice-payment-match",
  "arguments": {
    "invoice": {
      "number": "INV-1042",
      "amount": "1250.00",
      "currency": "USD",
      "payee": "Northwind Studio",
      "issue_date": "2026-10-01",
      "due_date": "2026-10-31"
    },
    "payment": {
      "amount": "1000.00",
      "currency": "USDC",
      "payee": "Northwind Studio",
      "reference": "INV-1042",
      "date": "2026-11-04"
    }
  }
}

What the report returns

Verdict: partial.
amount_short: the payment of 1000.00 is 250.00 short of the invoiced 1250.00.
paid_late: the payment on 2026-11-04 is 4 days after the due date of 2026-10-31.
Ties: the reference carries INV-1042, the payee matches, and USD and USDC compare one to one.

A payment of the full 1250.00 by the due date returns exact. To settle one invoice across several transfers, the settlement reconciliation check sums every transfer that carries its reference.

Call it from your agent.

Connect to https://weverlabs.com/mcp and call any of the fifty-two 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 diligence checks contract, the evidence checks contract, the promise checks and briefs contract the vendor checks and briefs contract, the disclosure checks contract, the assurance checks contract and the Commerce Assurance contract list the schemas, limits, topics, verdicts and signing details. The first DiligenceOps checks, receipts, escrow quotes, invoices and terms, and the data evidence check sit alongside these.

Browse all tools