Wallet Auth

Blockchain state →
signed credentials.

InsumerAPI reads wallet conditions across 32 chains and returns ECDSA-signed booleans or standard JWTs. No balances exposed. No Web3 libraries required.

OAuth proves who you are. Wallet Auth proves what you hold.

Try It Live View API Docs

100 free requests/day — no credit card

The primitive

Wallet

Any wallet address

32 chains supported

→

InsumerAPI

Verify conditions

Boolean, not balance

→

Credential

Signed JWT

Use anywhere

ECDSA P-256

The Primitive

Two endpoints. Signed output.

POST /v1/attest — Check any condition across 32 chains. Returns an ECDSA-signed boolean.

Request

{
  "wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
  "conditions": [{
    "type": "token_balance",
    "contractAddress": "0xA0b8...eB48",
    "chainId": 1,
    "threshold": 1000,
    "decimals": 6
  }]
}
                    

Response

{
  "ok": true,
  "data": {
    "attestation": {
      "id": "ATST-7F2K9",
      "pass": true,
      "results": [{ "met": true }]
    },
    "sig": "MEUCIQDx...base64...",
    "kid": "insumer-attest-v1"
  }
}
                    

POST /v1/trust — Aggregate 17 on-chain signals into a signed wallet trust credential. Built for AI agents.

Request

{
  "wallet": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045"
}
                    

Response

{
  "ok": true,
  "data": {
    "trust": {
      "id": "TRST-8K3M2",
      "dimensions": {
        "stablecoins": { "passCount": 5, "total": 7 },
        "governance": { "passCount": 2, "total": 4 },
        "nfts": { "passCount": 1, "total": 3 },
        "staking": { "passCount": 2, "total": 3 }
      },
      "summary": {
        "totalPassed": 10,
        "totalChecks": 17
      }
    },
    "sig": "MEQCIBk...base64...",
    "kid": "insumer-attest-v1"
  }
}
                    

ECDSA P-256 signed credentials 32 chains. One verification API. Optional JWT output Full docs →

Common Questions

What this isn't.

Not an oracle network

Unlike Chainlink or UMA, there's no token staking, no node network, and no gas fees. InsumerAPI is a server-side verifier. Responses are ECDSA-signed for independent verification, running on centralized infrastructure for speed and predictable costs.

Not a payment system

No crypto changes hands. Customers pay in regular currency. Businesses receive regular currency. We verify ownership. We don't move money.

Not DeFi

No smart contracts to deploy. No Web3 libraries required. Unlike on-chain gating with Lit Protocol or token-bound accounts, verification happens server-side via REST API. If you can call an endpoint, you can use this.

One System

Four layers. One pipeline.

Read

Check wallet conditions across 32 chains — tokens, NFTs, attestations

Sign

Produce ECDSA-signed attestations or standard JWT bearer tokens

Trust

Aggregate 17 on-chain signals into a signed wallet trust credential

Use

Commerce, compliance, access control, or agent trust

Use Cases

One primitive. Many applications.

Every use case is the same operation: read blockchain state, return a signed credential. The application determines what you do with it.

AI Agents

Agent-to-Agent Trust

Agents need privacy, signed signals, and deterministic answers — not raw wallets. POST /v1/trust returns a signed wallet trust credential. POST /v1/attest returns a JWT bearer token. Machine-readable trust without re-querying the chain.

Build with InsumerAPI →

API Access

Access Control

Gate premium features, content, or API access behind token ownership. Server-side verification. No wallet popup. No Web3 library in your frontend.

See developer docs →

Compliance

KYC & Identity Verification

Verify Coinbase Verifications and other EAS attestations on Base. Pre-configured compliance templates handle schema IDs and attester addresses. One API call confirms KYC without handling PII.

See compliance templates →

Commerce

Merchant Rewards

A coffee shop rewards SHIB holders. A restaurant recognizes Bored Ape owners on event week. Merchants attract pre-qualified communities via QR or NFC and only pay per scan.

See merchant use cases →

Governance