InsumerAPI
ChatGPT pluginWallet auth for AI agents
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.
Conditions 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.
Every 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.
This 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.
Not 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.
Documentation: https://insumermodel.com/developers/ OpenAPI: https://insumermodel.com/openapi.yaml Source for the MCP server (MIT): https://github.com/insumerapi/mcp-server-insumer
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
1 listing change logged · latest Oct 30: Version. See what changed
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools750th of 866 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 748 | #9006 | 1,082places down | |
| 749 | #9023 | 1,087places down | |
| 750 | #9041 | — | |
| 751 | #9113 | — | |
| 752 | #9114 | 1,116places down |
Example prompts
- “Check if wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 holds at least 1 ETH on Ethereum and show me the signed attestation.”
- “Build a trust profile for wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 and summarize each dimension.”
- “Is wallet 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 a registered ERC-8004 agent with agent ID 1 on Base?”
Skills
insumer-attest
Wallet auth via InsumerAPI: condition-based access with ES256-signed, JWKS-verifiable boolean responses (token balances across 37 chains, plus NFT ownership, EAS attestations, Farcaster IDs and other condition types). Use when the user wants InsumerAPI to give a "verified yes or no" on whether a wallet satisfies an on-chain condition, to gate a feature by what a wallet holds with InsumerAPI, or to compose an InsumerAPI wallet_state signal in a multi-issuer trust envelope. Read, evaluate, sign, in one call.
insumer-auth
InsumerAPI wallet auth: get an InsumerAPI key, configure INSUMER_API_KEY, check or top up InsumerAPI credits, or debug InsumerAPI 401/402/429 errors. Covers four key paths: free (email), paid (Stripe), an agent's first key paid on-chain, and an on-chain top-up of an existing key. The on-chain paths need the user's explicit approval of every payment.
insumer-discount
Token-holder discounts at InsumerAPI merchants: read a store's terms, check what a wallet qualifies for (free), optionally prove control of the wallet by signing an EIP-4361 message, and create a signed single-use discount code (INSR-XXXXX). Use when the user or agent wants a holder discount at a store in the InsumerAPI merchant directory, wants to know whether signing with the wallet gets a bigger discount, or needs a discount in ACP or UCP checkout format.
insumer-hosted-tools
How to use the InsumerAPI MCP tools this plugin connects to (the hosted server at api.insumermodel.com/mcp, no key needed). Use when the user asks to check if a wallet holds a token or an amount, whether a wallet owns an NFT, whether a wallet is a registered ERC-8004 agent, for a wallet trust profile, for InsumerAPI's signing keys or how to verify an attestation, for compliance templates, or for a merchant's discount, and the insumer MCP tools are available. Do not use for exact balances, prices, or sending transactions. Explains the shared daily allowance and when to switch to the REST skills with the user's own key.
insumer-jwks-verify
Offline ES256 verification of InsumerAPI signed responses against the public JWKS. Use when the user receives a signed attestation from /v1/attest, /v1/trust, or /v1/trust/batch and needs to verify the signature without trusting the JSON body. Covers both the JWT path (jose / PyJWT / go-jose) and the raw sig path (ES256 over the canonical attestation/trust object).
insumer-trust
InsumerAPI wallet trust profile: a curated multi-dimensional condition-based access bundle for a single wallet. 155 base checks across 27 chains in 10 dimensions (stablecoins, governance, NFTs, staking, institutional stablecoins, tokenized treasuries, stablecoin deposits, wrapped bitcoin, names, account), plus optional Solana, XRPL, Bitcoin and Tron dimensions (up to 176 checks across 29 chains in 14 dimensions). Use when the user wants an InsumerAPI trust profile, a pre-built signed wallet snapshot rather than conditions specified one by one (for example an InsumerAPI pre-transaction trust check). The profile is signed once, as a whole. Carry it unchanged: never re-sign or wrap it.
insumer-trust-batch
InsumerAPI batch wallet trust profiles: the same curated bundle as insumer-trust, for up to 10 wallets in a single call. Use when the user wants InsumerAPI trust profiles for a list of wallets (for example screening an airdrop or allowlist with InsumerAPI). Each wallet's profile is independently signed; the response supports partial success.
- Categories
- Made by
- InsumerAPI · Website
- Sign-in
- On Install
- Capabilities
- Read
- Availability
- Available
- Version
- 0.2.2
- Keywords
- insumer, insumerapi, wallet auth, check wallet balance, verify wallet, nft ownership, wallet trust profile, erc-8004, condition-based access, blockchain, attestation, web3, ai agents
- Created
- October 2, 2026
- More info
- Sponsorship
- Promote this plugin