Frequently Asked Questions

The Insumer Model™ is condition-based access infrastructure. It reads blockchain state and returns verified, privacy-preserving yes/no answers across 38 chains, without exposing wallet balances. You can check every result yourself without trusting us. Think of it as wallet auth: OAuth proves who you are, wallet auth proves what you hold. Learn more on our How It Works page.

OAuth proves identity: who you are. Wallet auth proves holdings: what you hold. The Insumer Model™ converts blockchain state into a signed attestation (a boolean or JWT) that any system can verify without touching a blockchain. Like OAuth, the downstream system never sees the underlying data. It just gets a trusted yes or no.

The API returns true or false: whether a wallet meets a condition or not. It never exposes the actual token balance, NFT inventory, or transaction history. A system learns “this wallet qualifies” not “this wallet holds 47,000 USDC.” This is privacy by design at the protocol level.

No. The Insumer Model™ is read-only condition-based access infrastructure. It reads blockchain state and returns signed attestations. It never moves funds, processes payments, or interacts with wallets. It is a verification layer, not a transaction layer.

38 blockchains: 32 EVM chains (Ethereum, Base, Polygon, Arbitrum, Optimism, BNB Chain, Avalanche, Sonic, zkSync Era, Linea, Gnosis, Mantle, Celo, and more), Solana (SPL tokens and NFTs), XRP Ledger (native XRP, trust line tokens like RLUSD and USDC, and NFTokens), and Bitcoin (native BTC, all address formats including Taproot). See the full list on our How It Works page.

Six primary use cases: AI Agents (wallet trust verification for autonomous agents: fact profiles, not scores), API Access (gate endpoints by wallet conditions), Compliance (KYC and eligibility checks via Coinbase Verifications and EAS attestations), Commerce (condition-based discounts for physical and online stores), Governance (verify voting eligibility), and Tokenized Assets (verify ownership of real-world asset tokens).

Yes. InsumerAPI is a REST API with 44 endpoints for developers and AI agents. The flagship endpoint is POST /v1/attest, which checks wallet conditions and returns a verified yes or no. Other endpoints include wallet trust profiles, batch trust, compliance checks, and credit management. See the developer documentation for details.

Enter your email on the homepage or call the self-serve key creation endpoint. You get an API key instantly, no credit card required. The free tier includes 100 daily reads and 10 verification credits. AI agents can also buy a key with USDC, USDT, or BTC via POST /v1/keys/buy, no email needed, the sender wallet becomes the key identity. Or skip the key entirely: attest and trust support x402 pay-per-call. Send a request with no credentials, get a 402 quote, sign a USDC authorization on Base, retry. $0.05 per attestation, settled on-chain.

Free tier: 100 daily reads, 10 verification credits, no credit card required. Pro and Enterprise tiers for production volume. Pay per call from $0.04, with volume discounts up to 50%. See full pricing →

Five runtime agent SDKs: MCP server (npx -y mcp-server-insumer, runtime agent access for Claude Desktop, Cursor, Windsurf), LangChain (pip install langchain-insumer), ElizaOS plugin (@insumermodel/plugin-eliza), LlamaIndex tool spec (pip install llama-index-tools-insumer), and OpenAI GPT (GPT Store). Plus a Claude Code skill (smithery skill add douglasborthwick/insumer-skill) that helps Claude Code write wallet auth into your project. Plus two framework adapters that package the wallet auth primitive into host-shaped surfaces: WDK protocol module (@insumermodel/wdk-protocol-wallet-auth) for Tether's Wallet Development Kit, and mppx condition-gate (@insumermodel/mppx-condition-gate) for Machine Payments Protocol routes. Attestations are independently verifiable with insumer-verify (npm install insumer-verify). OpenAPI 3.1 spec available at /openapi.yaml.

Yes. AI agents can create their own API keys, verify wallets, and purchase additional credits by sending USDC, USDT, or BTC on-chain via POST /v1/credits/buy, all programmatically with no human intervention. Agents can also skip keys entirely and pay per call over x402 (USDC on Base, $0.05 per attestation). Two condition types exist specifically for agents: erc8004_agent verifies ERC-8004 agent registration, and erc7710_delegation verifies that a principal really delegated authority to an agent, checked against live chain state. The MCP server and LangChain SDK make integration straightforward for agent frameworks.

Yes, on five endpoints: POST /v1/attest, POST /v1/trust, POST /v1/trust/batch, GET /v1/credits, and POST /v1/credits/buy. Agents that buy a key via POST /v1/keys/buy with USDC on an EVM chain receive an Insumer Access pass (soulbound ERC-721) minted to their wallet on Base. The same wallet can then sign requests with its private key and present them in an Authorization: Wallet header instead of X-API-Key. The signed message is SIWE (EIP-4361) scoped to api.insumermodel.com; the signature is EIP-191 personal_sign; single-use nonce; Issued At within the last 5 minutes. Other endpoints return 501 for this scheme. The five-endpoint coverage lets an SBT-holding agent run the full read-side lifecycle (attest, generate trust profiles, check balance, top up credits) without ever handling an API key. Drop-in middleware: @skyemeta/access on npm. See the full Authentication reference.

Every result includes a cryptographic signature and a key ID (kid). Fetch our public key from /.well-known/jwks.json or GET /v1/jwks, then verify the signature using insumer-verify (npm) or any standard crypto library. JWT-format results can be verified by standard JWT libraries. No callback to the API is required.

Sign up at the InsumerDashboard, choose which tokens and NFTs to recognize, and set discount tiers. Customers verify holdings via QR code or NFC tap. The system returns a signed attestation indicating their tier. Payment stays on your existing systems. You never touch cryptocurrency. See our getting started guide.

No. The Insumer Model™ is read-only verification. It checks what a wallet holds but never processes payments. Customers pay in whatever currency the merchant normally accepts. The merchant never touches crypto.

Yes. The API works from any country. For commerce, discounts are percentage-based, so they work in any currency. The blockchain infrastructure is already worldwide, and the verification process is the same everywhere.

API responses typically return in 1–3 seconds, even when checking multiple conditions across multiple chains. QR code scans verify in 2–3 seconds. NFC tap verifies in real time.

Yes. Developers can integrate InsumerAPI directly, or merchants can use the InsumerExtension for Chrome, which detects participating merchants and surfaces discounts at checkout with no code changes required.

Yes. InsumerAPI supports on-chain identity checks including Coinbase Verifications (KYC, country of residence, Coinbase One membership) and other verified records on Base. Pre-configured compliance templates let developers gate access to verified users without handling personal data. See the compliance docs.

Send a wallet address and one or more conditions (token balance thresholds, NFT ownership, on-chain identity records). The API checks state across 38 chains and returns a cryptographically signed yes or no for each condition. Optionally request format: "jwt" for a standard JWT, or proof: "merkle" for a blockchain-anchored storage proof. See How It Works for the full flow.

Adding format: "jwt" to an attestation request returns a standard ES256-signed JWT alongside the normal response. The JWT contains claims for pass/fail, condition results, and block context. It can be verified by any standard JWT library via the JWKS endpoint, making it compatible with Kong, Nginx, Cloudflare Access, AWS API Gateway, and similar systems.

Adding proof: "merkle" to an attestation request returns an EIP-1186 Merkle storage proof anchored to a specific block hash. This makes the attestation independently verifiable against the blockchain state trie without trusting the API. Available on 28 of 32 EVM chains. Costs 2 credits instead of 1.

The API returns only booleans: true or false for each condition. It never exposes wallet balances, token inventories, or transaction history. In commerce contexts, merchants see only the verification result (e.g. tier qualification), never the wallet address or holdings. Privacy is built in at the protocol level. Read our Privacy Policy for full details.

No. Verification is performed server-side against live blockchain data. Every result is cryptographically signed. You can verify any response yourself using our public signing key. Forged or tampered results are rejected by any system that checks the signature.

MetaMask, Phantom, and Coinbase Wallet. You can connect all three simultaneously, and holdings are aggregated across wallets. InsumerPass is a browser-based app, no download required.