InsumerAPI

Overview Schema Source Related Servers Discussions Admin

Add credits to the store owner key from a payment

insumer_buy_merchant_credits

Destructive

Instructions

Kept for compatibility: a store has no credit balance of its own, so a payment submitted here adds regular credits to the API key that owns the store, at a flat rate (the regular credit purchase, with volume tiers, is the usual way to top up). Submits a USDC, USDT, BTC, or USDT-TRC20 payment the caller has already sent. This tool does not move funds: it submits the transaction hash. USDC/USDT on EVM and Solana (auto-detected), USDT-TRC20 on Tron, BTC on Bitcoin (converted at market rate, 1 confirmation required). Non-refundable. Owner only. The first purchase registers the sender wallet to the API key; updateWallet: true replaces it. Current prices and volume discounts: https://insumermodel.com/pricing/

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Merchant ID
`amount`	No	Stablecoin amount sent (minimum 5). Not required for BTC.
`txHash`	Yes	Transaction hash proving payment
`chainId`	Yes	Payment chain: 1, 8453, 137, 42161, 10, 56, 43114, 'solana', 'bitcoin', or 'tron'. EVM/Solana accept USDC and USDT (auto-detected). Bitcoin accepts BTC (converted to USD at market rate). Tron accepts USDT-TRC20.
`updateWallet`	No	Set true to replace the registered sender wallet

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.

Changed9 schema fields changedv1.16.0Oct 4, 2026

changedInput schema / properties / chainId / anyOf

Previous value: -[
-  {
-    "enum": [
-      "1",
-      "8453",
-      "137",
-      "42161",
-      "10",
-      "56",
-      "43114"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "integer"
-  },
-  {
-    "const": "solana",
-    "type": "string"
-  },
-  {
-    "const": "bitcoin",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "enum": [
+      "1",
+      "8453",
+      "137",
+      "42161",
+      "10",
+      "56",
+      "43114"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "const": "solana",
+    "type": "string"
+  },
+  {
+    "const": "bitcoin",
+    "type": "string"
+  },
+  {
+    "const": "tron",
+    "type": "string"
+  }
+]

changedInput schema / properties / chainId / description

Previous value: -"Payment chain: 1, 8453, 137, 42161, 10, 56, 43114, 'solana', or 'bitcoin'. EVM/Solana accept USDC and USDT (auto-detected). Bitcoin accepts BTC (converted to USD at market rate)."New value: +"Payment chain: 1, 8453, 137, 42161, 10, 56, 43114, 'solana', 'bitcoin', or 'tron'. EVM/Solana accept USDC and USDT (auto-detected). Bitcoin accepts BTC (converted to USD at market rate). Tron accepts USDT-TRC20."

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_-]+$"
```
addedInput schema / properties / txHash / maxLength
```
Added value: +100
```

addedInput schema / properties / txHash / pattern

Added value: +"^(?:0x[0-9a-fA-F]{64}|[0-9a-fA-F]{64}|[1-9A-HJ-NP-Za-km-z]{43,90})$"

changedInput schema / properties / updateWallet / description

Previous value: -"Set true to update the registered sender wallet"New value: +"Set true to replace the registered sender wallet"

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.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: it does not move funds, it only submits a transaction hash; payments are non-refundable; owner-only; the first purchase registers the sender wallet and updateWallet replaces it; BTC requires 1 confirmation and market-rate conversion. This goes well past the destructive/openWorld hints.

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?

A dense paragraph, but front-loaded with the most important fact (compatibility status) and nearly every clause carries distinct information. It is slightly long for a single tool, though no sentence is clearly wasted.

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

Completeness5/5

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

For a destructive, open-world mutation with an output schema, the description covers what matters: auth requirement, non-refundability, no fund movement, wallet-registration side effect, per-chain handling, and a pricing link. Return values are handled by the output schema, so nothing essential is missing.

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 adds real meaning: EVM/Solana assets are auto-detected, Tron is USDT-TRC20 only, BTC is converted at market rate and amount is not required, and updateWallet's wallet-registration effect is explained. This enriches several parameters beyond the schema text.

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: a submitted payment 'adds regular credits to the API key that owns the store.' It immediately distinguishes itself from siblings by noting a store has no credit balance of its own and that this is 'Kept for compatibility,' routing the agent toward the standard credit purchase.

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 clear context: it is a compatibility path, the 'regular credit purchase, with volume tiers, is the usual way to top up,' and it is 'Owner only.' The alternative is described by function rather than by tool name, so the agent must map it to insumer_buy_credits itself, and there is no explicit when-not-to-use clause.

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