InsumerAPI

Overview Schema Source Related Servers Discussions Admin

Update merchant settings

insumer_configure_settings

DestructiveIdempotent

Configure owner-only merchant settings for discount stacking, caps, unproven-wallet limits, and stablecoin payments; optional fields replace current values.

Instructions

Update merchant settings: discount stacking mode, cap, the store's terms for wallets sent without proof of control, and stablecoin payment configuration. All fields optional; supplied fields replace their current values. discountCap is a whole number from 1 to 100. A wallet with proof gets the full discount their holdings earn, without the daily limit for unproven buyers. Owner only.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Merchant ID
`discountCap`	No	Maximum total discount percentage: a whole number from 1 to 100, no decimals
`usdcPayment`	No	USDC payment settings, or null to disable
`discountMode`	No	'highest' uses best single discount, 'stack' adds them together, 'capped' stacks up to discountCap
`maxUnprovenDiscount`	No	Most a wallet without proof of control can get, in percent: 0 = no discount, null = the same as a proven wallet
`maxDiscountsPerWalletPerDay`	No	Discount codes per UTC day for a wallet without proof of control; null = no limit

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	true when the API call succeeded
`data`	No	The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
`keys`	No	JWKS entries (insumer_jwks)
`meta`	No	Response metadata such as version and timestamp
`error`	No	Error details when ok is false
`items`	No	The result when the endpoint returns a JSON array
`message`	No	A plain-text result (insumer_setup), or a message from the API

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.17.1Oct 6, 2026

changedInput schema / properties / discountCap / description

Previous value: -"Maximum total discount percentage (1-100)"New value: +"Maximum total discount percentage: a whole number from 1 to 100, no decimals"

addedInput schema / properties / maxDiscountsPerWalletPerDay

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Discount codes per UTC day for a wallet without proof of control; null = no limit"
+}

addedInput schema / properties / maxUnprovenDiscount

Added value: +{
+  "anyOf": [
+    {
+      "maximum": 100,
+      "minimum": 0,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Most a wallet without proof of control can get, in percent: 0 = no discount, null = the same as a proven wallet"
+}

Changed5 schema fields changedv1.16.0Oct 4, 2026

addedInput schema / properties / id / maxLength
```
Added value: +100
```
addedInput schema / properties / id / minLength
```
Added value: +1
```
addedInput schema / properties / id / pattern
```
Added value: +"^[a-zA-Z0-9_-]+$"
```

changedInput schema / properties / usdcPayment / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "enabled": {
-        "description": "Enable or disable USDC payments",
-        "type": "boolean"
-      },
-      "evmAddress": {
-        "description": "EVM wallet for USDC (0x...)",
-        "type": "string"
-      },
-      "preferredChainId": {
-        "anyOf": [
-          {
-            "enum": [
-              "1",
-              "8453",
-              "137",
-              "42161",
-              "10",
-              "56",
-              "43114"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "integer"
-          },
-          {
-            "const": "solana",
-            "type": "string"
-          }
-        ],
-        "description": "Preferred USDC chain"
-      },
-      "solanaAddress": {
-        "description": "Solana wallet for USDC",
-        "type": "string"
-      }
-    },
-    "required": [
-      "enabled"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "enabled": {
+        "description": "Enable or disable USDC payments",
+        "type": "boolean"
+      },
+      "evmAddress": {
+        "description": "EVM wallet for USDC (0x...)",
+        "pattern": "^0x[0-9a-fA-F]{40}$",
+        "type": "string"
+      },
+      "preferredChainId": {
+        "anyOf": [
+          {
+            "enum": [
+              "1",
+              "8453",
+              "137",
+              "42161",
+              "10",
+              "56",
+              "43114"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "integer"
+          },
+          {
+            "const": "solana",
+            "type": "string"
+          },
+          {
+            "const": "tron",
+            "type": "string"
+          }
+        ],
+        "description": "Preferred USDC chain"
+      },
+      "solanaAddress": {
+        "description": "Solana wallet for USDC",
+        "pattern": "^[1-9A-HJ-NP-Za-km-z]{32,44}$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "enabled"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "description": "The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records"
+    },
+    "error": {
+      "description": "Error details when ok is false"
+    },
+    "items": {
+      "description": "The result when the endpoint returns a JSON array",
+      "items": {},
+      "type": "array"
+    },
+    "keys": {
+      "description": "JWKS entries (insumer_jwks)",
+      "items": {},
+      "type": "array"
+    },
+    "message": {
+      "description": "A plain-text result (insumer_setup), or a message from the API"
+    },
+    "meta": {
+      "description": "Response metadata such as version and timestamp"
+    },
+    "ok": {
+      "description": "true when the API call succeeded",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Addedv0.1.0Apr 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the owner-only authorization requirement and the replacement semantics of supplied fields, which matter for a destructive partial update.

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

Conciseness4/5

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

Front-loads the resource and field list, then the update rules and the discountCap constraint. Dense but each sentence carries information; only the wallet-proof sentence is slightly tangential to calling the tool.

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

Completeness4/5

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

With an output schema present, return values need not be described, and the annotations carry the safety profile. The description covers scope, permissions and update semantics adequately for a 6-parameter, owner-restricted mutation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the interplay of discountMode/discountCap and how proven versus unproven wallets are treated — semantics the enum and range descriptions alone do not fully convey.

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

Purpose5/5

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

States a specific verb and resource (update merchant settings) and enumerates the exact configurable domains — discount stacking mode, cap, unproven-wallet terms, stablecoin payments. This clearly separates it from siblings like insumer_configure_tokens and insumer_configure_nfts.

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

Usage Guidelines4/5

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

Gives a clear precondition ("Owner only") and the partial-update contract ("All fields optional; supplied fields replace their current values"), so the agent knows when and how to call it. It does not, however, name alternative tools or state when not to use it.

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