ApiDapp

Name: ApiDapp API
Brand: ApiDapp
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsPackage RegistryapiKey30 EndpointsREST

For Agents

Read Ethereum accounts, blocks, transactions, ERC-20 balances, and contracts over REST without running a node or speaking JSON-RPC.

Connect the ApiDapp to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ApiDapp, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with ApiDapp API.

Fetch account balances and transaction history for any Ethereum address over REST

Read block headers and the transactions inside a block by index or hash

Read and write ERC-20 token balances and transfers without crafting raw RPC calls

Call read-only contract methods and submit signed transactions via HTTP

GET STARTED

Start building with ApiDapp API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ApiDapp, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ApiDapp, keeping it validated and agent-ready. ApiDapp is a REST gateway for Ethereum that lets clients read accounts, blocks, blockchains, contracts, ERC-20 tokens, transactions, and wallets without running a full node or speaking JSON-RPC. The API exposes 30 operations across 26 paths so a developer can list block transactions, read an ERC-20 balance, deploy or call a contract, and manage an embedded wallet through plain HTTP. It targets dapp builders who want a hosted Ethereum read/write surface and prefer REST over the standard web3 RPC interface.

Use Cases

Patterns agents use ApiDapp API for, with concrete tasks.

★ Wallet Balance Display

Show the ETH and ERC-20 holdings for a user-supplied address inside an app without running an Ethereum node. ApiDapp's /account/{id} endpoint returns the ETH balance and /erc20 endpoints return token balances for the same address. This pattern is common for portfolio trackers and wallet UIs that want to onboard in hours rather than provisioning Geth or paying for an RPC subscription up front.

GET /account/0xAbC123... to read the ETH balance and then GET /erc20/{contract}/balance/0xAbC123... for the USDC balance

Block and Transaction Indexing

Walk the chain block by block to build a custom index of transactions, contract calls, or token transfers. ApiDapp's /block/{id} endpoint returns block content and /block/{id}/transaction lists the transactions inside that block, so a small worker can ingest data without parsing raw RLP or running a full archive node.

GET /block/18000000/transaction to list the transactions in block 18000000 and store the from/to/value tuple for each

Smart Contract Interaction

Call read-only functions on a deployed Ethereum contract or submit a signed transaction without writing web3.js or ethers boilerplate. ApiDapp's /contract endpoints accept the contract address and method name and return the decoded result. For state-changing calls, the API accepts a signed transaction so private keys can stay in a hardware wallet or signer service.

POST to /contract/{address} with the method name 'balanceOf' and an address argument to read the holding without sending a transaction

AI Agent On-Chain Queries

Give an AI agent a tool to answer on-chain questions like 'what's the ETH balance of vitalik.eth?' or 'is this transaction confirmed?'. Through Jentic, the agent searches for an intent and gets the matching ApiDapp operation. The agent can answer without the developer wiring a JSON-RPC client or running a node.

Search Jentic for 'get ethereum account balance', load the /account/{id} schema, and execute with id=0xAbC... to return the current ETH balance

Key Endpoints

30 endpoints — jentic publishes the only available openapi specification for apidapp, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/account/{id}

Fetch ETH balance and metadata for an address

GET

/block/{id}

Read a block by number or hash

GET

/block/{id}/transaction

List transactions inside a block

GET

/contract

List or look up deployed contracts known to ApiDapp

GET

/blockchain

Read chain metadata and latest state

GET

/wallet

List server-side wallets

GET

/account/{id}

Fetch ETH balance and metadata for an address

GET

/block/{id}

Read a block by number or hash

GET

/block/{id}/transaction

List transactions inside a block

GET

/contract

List or look up deployed contracts known to ApiDapp

GET

/blockchain

Read chain metadata and latest state

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The X-Api-Key header is stored encrypted in the Jentic vault and attached to outgoing requests at execution time. The agent only ever sees the operation result, not the raw key.

Intent-based discovery

Agents search by intent (for example 'get ethereum account balance' or 'list block transactions') and Jentic returns the matching ApiDapp operation with its input schema, so the agent can call the right endpoint without browsing the 30-operation reference.

Time to first call

Direct ApiDapp integration: half a day to a day to wire up the API key and define request/response shapes. Through Jentic: under 1 hour - search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Alchemy API

Production-grade Ethereum and multi-chain node infrastructure as a service

Choose Alchemy when the agent needs production reliability, archive data, enhanced webhooks, or multi-chain coverage that ApiDapp's REST layer does not provide

Alternative

QuickNode API

Hosted Ethereum and multi-chain RPC with a managed dashboard and add-on marketplace

Choose QuickNode when the agent needs low-latency RPC, dedicated endpoints, or chain coverage beyond Ethereum mainnet

Alternative

Ankr API

Decentralised RPC service across Ethereum and many other chains

Choose Ankr when the agent needs broad multi-chain support and a free tier for prototyping rather than a single-network REST surface

FAQs

Specific to using ApiDapp API through Jentic.

Why is there no official OpenAPI spec for ApiDapp?

ApiDapp does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ApiDapp via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

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 the Jentic vault 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.