Update to InsumerAPI

Changed files

Choose a file to see its text changes. Binary or large files show metadata only.

README.md →

SKILLS_SOURCE →

plugin.json →

skills/insumer-x402-recipes/SKILL.md →

plugin.json

− removed · + added

--- before
+++ after
@@ -1,8 +1,8 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "insumer",
-  "version": "0.2.2",
-  "description": "Check what a wallet holds, with a signed yes or no. InsumerAPI wallet auth for AI agents: token balances, NFTs, EAS attestations, ERC-8004 agents and trust profiles across 37 chains, never the balance. Seven skills plus the hosted MCP server at api.insumermodel.com/mcp.",
+  "version": "0.2.3",
+  "description": "Check what a wallet holds, with a signed yes or no. InsumerAPI wallet auth for AI agents: token balances, NFTs, EAS attestations, ERC-8004 agents and trust profiles across 37 chains, never the balance. Eight skills plus the hosted MCP server at api.insumermodel.com/mcp.",
   "author": {
     "name": "InsumerAPI",
     "email": "support@insumermodel.com",
@@ -31,7 +31,7 @@
       "interface": {
         "displayName": "InsumerAPI",
         "shortDescription": "Wallet auth for AI agents",
-        "longDescription": "Ask ChatGPT things like \"check if this wallet holds at least 100 USDC on Base\", \"does this wallet own an NFT from this collection\", \"is this wallet a registered ERC-8004 agent\", \"build a trust profile for this wallet\", \"verify this wallet attestation offline\" or \"what discount does this wallet get at this merchant\". InsumerAPI answers each one with a signed yes or no: does this wallet satisfy this condition right now? The balance itself is never returned.\n\nConditions cover token balances, NFT ownership, EAS attestations (including Coinbase Verifications and Gitcoin Passport templates), Farcaster IDs, ERC-8004 agent registration, ERC-7710 delegations and account code state (plain key, EIP-7702 delegation or contract), across 37 chains: 31 EVM chains plus Solana, XRP Ledger, Bitcoin, Tron, Stellar and Sui. Send a wallet address and up to ten conditions in one request. A wallet trust profile runs 155 checks across 27 chains in ten dimensions and reports what is held or not held, with no score and no opinion.\n\nEvery response is signed twice, with ES256 and with a post-quantum ML-DSA-65 signature, and carries a hash of the evaluated condition and the block it was read at. Anyone can check a result without calling InsumerAPI again, using the open-source insumer-verify package on npm and PyPI.\n\nThis plugin connects to the hosted InsumerAPI MCP server, which needs no account and no key. It serves ten tools: the public signing keys, condition attestation, compliance templates, wallet trust profiles (single and batch), the merchant and token directories, a discount check, and discount-code validation. The hosted server is shared, so the tools that produce signed results are rate limited per day; when the limit is reached, calls are declined until 00:00 UTC. Six of the seven included skills cover the same work through the REST API with your own key, which adds key management, discount codes and the merchant tools.\n\nNot for: exact balances, portfolio values, price data, sending transactions, or trading. InsumerAPI holds no secrets, requires no identity, issues no static credentials, and stores no wallet addresses or conditions from verification requests. It is condition-based access infrastructure, and wallet auth is how it works: read the wallet's on-chain state, evaluate it against the condition, sign the answer.\n\nDocumentation: https://insumermodel.com/developers/\nOpenAPI: https://insumermodel.com/openapi.yaml\nSource for the MCP server (MIT): https://github.com/insumerapi/mcp-server-insumer",
+        "longDescription": "Ask ChatGPT things like \"check if this wallet holds at least 100 USDC on Base\", \"does this wallet own an NFT from this collection\", \"is this wallet a registered ERC-8004 agent\", \"build a trust profile for this wallet\", \"verify this wallet attestation offline\" or \"what discount does this wallet get at this merchant\". InsumerAPI answers each one with a signed yes or no: does this wallet satisfy this condition right now? The balance itself is never returned.\n\nConditions cover token balances, NFT ownership, EAS attestations (including Coinbase Verifications and Gitcoin Passport templates), Farcaster IDs, ERC-8004 agent registration, ERC-7710 delegations and account code state (plain key, EIP-7702 delegation or contract), across 37 chains: 31 EVM chains plus Solana, XRP Ledger, Bitcoin, Tron, Stellar and Sui. Send a wallet address and up to ten conditions in one request. A wallet trust profile runs 155 checks across 27 chains in ten dimensions and reports what is held or not held, with no score and no opinion.\n\nEvery response is signed twice, with ES256 and with a post-quantum ML-DSA-65 signature, and carries a hash of the evaluated condition and the block it was read at. Anyone can check a result without calling InsumerAPI again, using the open-source insumer-verify package on npm and PyPI.\n\nThis plugin connects to the hosted InsumerAPI MCP server, which needs no account and no key. It serves ten tools: the public signing keys, condition attestation, compliance templates, wallet trust profiles (single and batch), the merchant and token directories, a discount check, and discount-code validation. The hosted server is shared, so the tools that produce signed results are rate limited per day; when the limit is reached, calls are declined until 00:00 UTC. Six of the eight included skills cover the same work through the REST API with your own key, which adds key management, discount codes and the merchant tools. Another holds recipes for agents that check a wallet before they pay another x402 service.\n\nNot for: exact balances, portfolio values, price data, sending transactions, or trading. InsumerAPI holds no secrets, requires no identity, issues no static credentials, and stores no wallet addresses or conditions from verification requests. It is condition-based access infrastructure, and wallet auth is how it works: read the wallet's on-chain state, evaluate it against the condition, sign the answer.\n\nDocumentation: https://insumermodel.com/developers/\nOpenAPI: https://insumermodel.com/openapi.yaml\nSource for the MCP server (MIT): https://github.com/insumerapi/mcp-server-insumer",
         "developerName": "InsumerAPI",
         "category": "Developer Tools",
         "capabilities": [