What authentication does the ApiDapp use?

ApiDapp uses an API key passed in the X-Api-Key request header. Through Jentic, the key is stored encrypted in your Jentic One instance and injected at execution time, so the raw key never appears in the agent's prompt or logs.

Can I read an ERC-20 balance with this API?

Yes. The /erc20 endpoints expose token metadata and balances by token contract address. For a specific holder, use the per-token balance endpoint with the contract address and the holder address - much shorter than encoding a balanceOf call into raw JSON-RPC.

Which Ethereum networks does the ApiDapp cover?

The base URL https://ethereum.apidapp.com/1 targets Ethereum mainnet (chain id 1). Other networks are not declared in the OpenAPI spec; check the ApiDapp website for any current testnet endpoints.

What are the rate limits for the ApiDapp?

The OpenAPI spec does not encode hard limits. Standard practice for REST gateways onto Ethereum is to throttle at the API key level and return HTTP 429 on overage, so agents calling through Jentic should retry with backoff on 429.

How do I look up a transaction status with the ApiDapp through Jentic?

Search Jentic for 'check ethereum transaction status', load the /transaction/{id} schema, and execute with id set to the transaction hash. The response surfaces the confirmation count and the receipt status, so the agent can branch on whether the tx is mined.

Can I limit what my agent is allowed to do with the ApiDapp API?

Yes. Because you run Jentic One yourself, you decide which ApiDapp operations your agent may call, so read-only calls like GET /account/{id} and GET /block/{id} can be permitted while write operations such as submitting signed transactions or creating wallets stay off unless you add them. Since the account and block id sit in the URL path, your own rules can pin the agent to a single account or block and nothing else. Your stored ApiDapp key is injected only at execution time, so the agent never sees or handles the raw credential.