For Agents
Generate Ethereum addresses, send ETH and ERC-20 tokens, read balances and transactions, and manage IPN webhook subscriptions through Chaingateway's hosted Ethereum bridge.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chaingateway.io, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: 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 | shStep 2: 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 instanceJentic 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.
What an agent can do with Chaingateway.io API.
Generate, import, list, export, clear, and delete Ethereum addresses inside the account
Read the ETH and ERC-20 token balance for any address
Send ETH and ERC-20 tokens from a managed address
GET STARTED
Use for: I need to generate a new Ethereum address inside my Chaingateway account, Send 0.05 ETH from my managed address to a customer, Send 100 USDT to a recipient address, Get the ETH balance of a wallet I imported
Not supported: Does not custody non-Ethereum chains, run smart-contract simulation, or provide on-chain analytics — use for hosted Ethereum wallet, ERC-20 transfer, and IPN webhook operations only.
Chaingateway.io is a REST bridge between an Ethereum node and an application, exposing managed wallet addresses, ETH and ERC-20 token balances, send-funds operations, transaction history, and IPN-based webhook notifications when subscribed addresses receive funds. Account holders authenticate with an API key issued from chaingateway.io and call POST endpoints to import existing addresses or generate new ones, send ETH or tokens, query balances, and replay failed IPN deliveries.
List recent transactions for an address
Subscribe and unsubscribe addresses for IPN webhook notifications when they receive funds
Replay failed IPNs and list those that have failed delivery
Look up the current gas price, latest block number, and a specific block by hash or height
Patterns agents use Chaingateway.io API for, with concrete tasks.
★ Hosted Ethereum Wallet
Run a hosted-wallet service that issues an Ethereum address per user without operating an Ethereum node. POST /newAddress generates an address inside the Chaingateway account, POST /getEthereumBalance and POST /getTokenBalance read state, and POST /sendEthereum and POST /sendToken move funds out. Used by checkout flows, payroll services, and on-ramp products that need ETH plumbing without node ops.
Call POST /newAddress to issue a deposit address per user, then POST /getEthereumBalance for that address to display the balance
ERC-20 Payouts
Programmatically pay users in stablecoins or other ERC-20 tokens from a single funded hot wallet. POST /sendToken executes a transfer from a managed address, and POST /getTokenBalance lets the system check liquidity before each batch. Useful for token-rewards programs, marketplace payouts, and stablecoin payroll.
Call POST /getTokenBalance to confirm the hot wallet has enough USDT, then POST /sendToken for each user payout in the batch
Incoming Payment Notifications
Notify backend systems the moment a customer deposit hits an Ethereum address by subscribing the address to Chaingateway IPNs. POST /subscribeAddress registers the callback URL, and POST /listFailedIPNs plus POST /resendFailedIPN cover delivery retry logic so a temporary outage doesn't lose a deposit signal. This avoids polling /getTransactions in a tight loop.
Call POST /subscribeAddress for the merchant deposit address with the callback URL, then nightly call POST /listFailedIPNs and POST /resendFailedIPN for each entry
AI Agent Crypto Treasury via Jentic
A treasury agent receives a user request 'send 0.1 ETH to this address from our hot wallet'. Through Jentic, the agent searches for a send-eth operation, loads the input schema, and calls /sendEthereum with credentials from the Jentic vault. The agent never sees the raw API key and the developer doesn't have to wire a custom Authorization header for each tool.
Use Jentic to search 'send eth to an address', load the operation backed by POST /sendEthereum, and execute it with the recipient and amount
21 endpoints — chaingateway.
METHOD
PATH
DESCRIPTION
/newAddress
Generate a new managed Ethereum address
/getEthereumBalance
Read ETH balance for an address
/getTokenBalance
Read ERC-20 token balance for an address
/sendEthereum
Send ETH from a managed address
/sendToken
Send an ERC-20 token from a managed address
/subscribeAddress
Subscribe an address to IPN notifications
/getTransactions
List recent transactions for an address
/getGasPrice
Read current Ethereum gas price
/newAddress
Generate a new managed Ethereum address
/getEthereumBalance
Read ETH balance for an address
/getTokenBalance
Read ERC-20 token balance for an address
/sendEthereum
Send ETH from a managed address
/sendToken
Send an ERC-20 token from a managed address
Three things that make agents converge on Jentic-routed access.
Credential isolation
Chaingateway API keys are stored encrypted in the Jentic vault and added to the Authorization header at execution time. Agents receive scoped access only — the raw key never enters the agent's context window or prompt history.
Intent-based discovery
Agents search Jentic by intent (e.g., 'create an ethereum address' or 'send eth to a recipient') and Jentic returns the matching Chaingateway operation with its input schema, so the agent posts the right body to the right endpoint without scraping the docs.
Time to first call
Direct Chaingateway integration: half a day for key handling, IPN callback verification, and retry logic. Through Jentic: under 30 minutes — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Chaingateway.io API through Jentic.
What authentication does the Chaingateway.io API use?
The API uses an API key passed in the Authorization header, issued after registration at chaingateway.io. Through Jentic, the key is held in the Jentic vault and added to outgoing requests at execution time so it never enters the agent's prompt or context window.
Can I send ETH or ERC-20 tokens from a server with the Chaingateway API?
Yes. POST /sendEthereum sends ETH and POST /sendToken sends an ERC-20 token from a managed address inside the account. Use POST /getEthereumBalance or POST /getTokenBalance first to confirm sufficient funds before each transfer.
How do I get notified when a Chaingateway address receives funds?
Call POST /subscribeAddress with the address and your IPN callback URL, and Chaingateway will POST a notification to that URL when the address receives ETH or tokens. POST /listFailedIPNs and POST /resendFailedIPN cover retry logic so temporary outages on the callback side do not lose events.
What are the rate limits for the Chaingateway.io API?
Rate limits are tied to your Chaingateway plan rather than published as a single number in this spec. Watch for 429 responses with Retry-After headers and keep IPN callbacks idempotent so a retry storm does not double-credit a deposit.
How do I generate a new Ethereum deposit address through Jentic?
Search Jentic for 'create a new ethereum address', load the operation backed by POST /newAddress, and execute it with the optional label. Jentic injects the Authorization header so the agent receives the typed address payload.
Does Chaingateway.io support importing an existing private key?
Yes. POST /importAddress imports an existing keypair into the account, and POST /exportAddress retrieves the corresponding key material later. Pair with POST /listAddresses to enumerate everything currently held by the account, and use POST /deleteAddress or POST /clearAddress to remove entries when no longer needed.
/subscribeAddress
Subscribe an address to IPN notifications
/getTransactions
List recent transactions for an address
/getGasPrice
Read current Ethereum gas price