Wever Labs Agent Products

Receipt Passport

wever_receipt-passport

Destructive

Paid URL: 0.10 USDC per call on Base; 10 signed-wallet free calls shared over rolling 30 days. Read the backend 402 body for x402 terms. Issue and verify signed receipt passports backed by completed, wallet-owned Wever computation records. Operating boundary: Issue and verify signed receipt passports backed by completed, wallet-owned Wever computation records. Fresh signed wallet proof is required even for paid calls. Handoff permissions require recipient enforcement. Stored evidence is not automatically verified. Scores are bounded evidence summaries, not global reputation. POST /api/receipt-passport. Existing product credentials, signed mandates, and single-use action grants remain required where applicable. This adapter grants no authority and never supplies server credentials. Wallet-authenticated durable trust service. Signed records attest only to the stated evidence and permission scope. See /api/trust-contract for the public verification key and bounded contract.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`work`	No
`usage`	No
`passport`	No
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 1, 2026

changedInput schema / additionalProperties
```
Previous value: -trueNew value: +false
```

removedInput schema / description

Removed value: -"The existing product POST body. Supply its documented mode, arguments, and required signed authority or grant. The product validates its full contract."

removedInput schema / maxProperties
```
Removed value: -64
```
removedInput schema / minProperties
```
Removed value: -1
```

addedInput schema / oneOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "idempotency_key": {
+        "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+        "type": "string"
+      },
+      "mode": {
+        "const": "issue"
+      },
+      "usage": {
+        "enum": [
+          "synthetic",
+          "operational"
+        ]
+      },
+      "work": {
+        "oneOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "kind": {
+                "const": "wallet_free_call"
+              },
+              "nonce": {
+                "pattern": "^[a-f0-9]{32,64}(?![\\s\\S])",
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "nonce"
+            ],
+            "type": "object"
+          },
+          {
+            "additionalProperties": false,
+            "properties": {
+              "kind": {
+                "const": "settled_payment"
+              },
+              "payment_id": {
+                "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+                "type": "string"
+              }
+            },
+            "required": [
+              "kind",
+              "payment_id"
+            ],
+            "type": "object"
+          }
+        ]
+      }
+    },
+    "required": [
+      "mode",
+      "idempotency_key",
+      "work",
+      "usage"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "mode": {
+        "const": "verify"
+      },
+      "passport": {
+        "maxLength": 24000,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "mode",
+      "passport"
+    ],
+    "type": "object"
+  }
+]

addedInput schema / properties / idempotency_key

Added value: +{
+  "pattern": "^[a-zA-Z0-9_-]{1,96}(?![\\s\\S])",
+  "type": "string"
+}

addedInput schema / properties / mode / enum

Added value: +[
+  "issue",
+  "verify"
+]

removedInput schema / properties / mode / maxLength
```
Removed value: -128
```
removedInput schema / properties / mode / minLength
```
Removed value: -1
```
removedInput schema / properties / mode / type
```
Removed value: -"string"
```

addedInput schema / properties / passport

Added value: +{
+  "maxLength": 24000,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / usage

Added value: +{
+  "enum": [
+    "synthetic",
+    "operational"
+  ]
+}

addedInput schema / properties / work

Added value: +{
+  "oneOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "const": "wallet_free_call"
+        },
+        "nonce": {
+          "pattern": "^[a-f0-9]{32,64}(?![\\s\\S])",
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "nonce"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "kind": {
+          "const": "settled_payment"
+        },
+        "payment_id": {
+          "pattern": "^[a-f0-9]{64}(?![\\s\\S])",
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "payment_id"
+      ],
+      "type": "object"
+    }
+  ]
+}

addedInput schema / required
```
Added value: +[
+  "mode"
+]
```

First observedSep 29, 2026

TDQS

C2.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, idempotentHint=false. The description adds pricing terms (0.10 USDC, free calls) and boundary notes (fresh wallet proof required, stored evidence not auto-verified). However, it does not disclose what 'destructive' means here: does issuing a passport consume a free call, invalidate prior records, or fail idempotently? The annotations already cover the safety profile, and the description doesn't enrich it significantly beyond payment details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the paid URL term, then the core action, then a dense block of boundary statements repeated twice ('backed by completed, wallet-owned Wever computation records' appears in both the first and second sentences). Some sentences like 'This adapter grants no authority and never supplies server credentials' are boilerplate that may not help the agent. Structure is somewhat redundant but not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, 5 parameters with 0% schema description coverage, and annotations carry the safety profile. The description does not explain the return values, the shape of a passport, or the result of verification. For a complex tool with branching modes and nested objects (work oneOf), this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, but it provides no meaning for any parameter (mode, work, usage, idempotency_key, passport). The schema only has patterns and enums without descriptions, so the agent is left to guess what 'work.kind' or 'usage: synthetic/operational' entail. This is a severe gap for a 5-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource: 'Issue and verify signed receipt passports backed by completed, wallet-owned Wever computation records.' This distinguishes it from siblings like proof-inbox or trust-scorecard. It is slightly muddled by the pricing preamble and DRM-like boundary language, but the core action is clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage via modes (issue vs verify) and mentions of paid vs free calls, but no explicit when-to-use guidance versus alternatives. It doesn't say when an agent should call this instead of wever_proof-inbox or wever_agent-trust-scorecard.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wever Labs Agent Products tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Receipt Passport

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources