Check the terms before your agent commits.

The thirteen checks.

Round 1 has four checks for payments, delegations, identities and continuity. Round 2 adds five for agent cards, MCP server configurations and operator arrangements. Round 3 adds four for your own spending policy, approval chain, service terms and incident plan.

Round 1

Round 2

Agent cards, server configurations and operator arrangements.

These checks cover what an agent relies on beyond a single payment: the card another agent publishes, the MCP server it is about to add, and how an operator passes on, hands over and recovers what it runs.

Round 3

Your own spending, approvals, service terms and incident plan.

These checks read the arrangements your agent works under before it commits to them: the spending policy that caps it, the approval chain that signs off on it, the terms of a service it is about to start paying for and the incident plan it relies on when something breaks. For a counterparty's own material, such as its insurance, audit report, data processing agreement or NDA, the DiligenceOps assurance checks read it the same way.

How the payment policy check decides.

Every rule runs on every offer in the challenge. The verdict is pay when the challenge is well formed and an offer passes every rule; otherwise it is refuse, with the reason for each rule that failed.

Amounts compare exactly. A challenge states its amount in the asset's smallest unit, so the check scales it by the asset's decimals before comparing it with caps written in whole units: 100000 is 0.10 USDC. USDC on eip155:8453 and eip155:84532 is known by address; for any other asset, send its decimals with the policy.

What the other checks look for.

A short worked example

Should your agent pay this challenge?

{
  "name": "wever_payment-policy-check",
  "arguments": {
    "challenge": {
      "x402Version": 2,
      "resource": {
        "url": "https://api.example.com/v1/quotes"
      },
      "accepts": [
        {
          "scheme": "exact",
          "network": "eip155:8453",
          "amount": "100000",
          "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
          "payTo": "0xc3837428F0e36E2573025c4A22E0F774FB3Cee3e",
          "maxTimeoutSeconds": 120
        }
      ]
    },
    "policy": {
      "per_call_cap": "0.25",
      "daily_cap": "5.00",
      "spent_today": "4.95",
      "allowed_networks": [
        "base"
      ],
      "allowed_assets": [
        "USDC"
      ]
    }
  }
}

A round 2 worked example

Is this MCP server configuration ready to install?

{
  "name": "wever_mcp-server-check",
  "arguments": {
    "config": {
      "mcpServers": {
        "quotes": {
          "url": "http://mcp.example.com/mcp",
          "headers": {
            "Authorization": "Bearer "
          }
        },
        "files": {
          "command": "npx",
          "args": [
            "-y",
            "example-files-mcp@1.4.0"
          ],
          "env": {
            "FILES_API_KEY": "example-not-a-real-key-7Q2"
          }
        }
      }
    }
  }
}

A round 3 worked example

Is this spending policy safe to run under?

{
  "name": "wever_spending-policy-check",
  "arguments": {
    "text": "Each payment is capped at 0.50 USDC.\nThe agent may also buy software subscriptions.\nPay only in USDC on Base."
  }
}

What each check reads.

Every check works from the material in the call: the challenge exactly as the endpoint returned it, the delegation as written, the identity record and the agent card as published, the server configuration as pasted, the continuity, succession, handover and recovery arrangements as the operator states them, and your own spending policy, approval chain, service terms and incident plan as you have written them. Wever evaluates it and signs the result. Paying, acting under the delegation and dealing with the other party stay with your agent, which keeps the signed report as the record of what it checked and when.

Each report says in one line how it was reached: the payment policy check evaluates the challenge against the policy rule by rule, the identity and agent card checks hold the record against itself, the MCP server check evaluates the configuration entry by entry, the delegation, continuity, succession, handover, recovery and incident plan checks match words, figures, dates and named items in the text, and the spending policy, approval chain and service terms checks also compare the amounts they read exactly.

Call it from your agent.

Connect to https://weverlabs.com/mcp and call any of the thirteen checks. 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 contract lists the schemas, rules, statuses and how to verify a receipt. To check an endpoint itself before you depend on it, use the endpoint reliability check; for the vendor pages and policies your agent relies on, see the DiligenceOps checks.