Can I limit what my agent is allowed to do with InsumerAPI?

Yes. For a gating agent, write a rule that allows only POST /v1/attest and GET /v1/jwks. The agent can check wallet conditions and fetch the keys to verify the answer, but it cannot buy credits, create keys, or change merchant settings, and every call it makes is logged. For a store assistant, allow PUT /v1/merchants/{id}/settings on your own merchant id only.

What authentication does InsumerAPI use?

Per its OpenAPI spec, most operations take an API key in the `X-API-Key` header, in the format insr_live_ followed by 40 hex characters. Five operations (POST /v1/attest, POST /v1/trust, POST /v1/trust/batch, GET /v1/credits, and POST /v1/credits/buy) also accept wallet-signed auth in the `Authorization` header as `Wallet <base64 SIWE message and signature>` from a wallet that holds the Insumer Access pass. Public reads such as GET /v1/jwks, GET /v1/compliance/templates, and GET /v1/health need no credential, and a few account operations such as POST /v1/keys/lookup take the key in the request body. Through Jentic, your key is stored encrypted by your own Jentic One instance and injected into the calls that need it.

Does InsumerAPI reveal a wallet's balance?

No. Per the spec, it returns signed booleans stating whether each condition was met and never returns raw balances or account code. A signed result shows that InsumerAPI read chain state and evaluated the stated conditions; it does not show who controls the wallet.

What are the rate limits for InsumerAPI?

The OpenAPI spec says each key has a daily request limit and returns 429 when it is exceeded, without stating a fixed number. GET /v1/credits returns your account's credit balance, tier, and daily rate limit; see https://insumermodel.com for plan details.

How many credits does an InsumerAPI attestation cost?

Per the spec, a standard POST /v1/attest call costs 1 credit and 2 credits with proof set to merkle. The erc8004_agent and erc7710_delegation condition types cost 1 credit.

How do I check a wallet's NFT ownership with InsumerAPI through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import InsumerAPI from the API Directory, and store your API key. Your agent searches for 'check whether a wallet owns an NFT', gets POST /v1/attest with its input schema, and calls it with the wallet and an nft_ownership condition naming the contractAddress and chainId. To run it on your own infrastructure, install Jentic One from its GitHub repo.