teckel: Ethereum RPC Services

→ View the detailed Ethereum RPC pricing chart

Developer-grade Ethereum JSON-RPC access — mainnet and Sepolia testnet — pay-as-you-go, with no subscription. Authenticate with your account address and API key (see teckel Account & Identity).

Same private account model as every teckel service: no IP logging, no KYC. You pay per call in teckel credits.

teckel offers Ethereum RPC services, without subscription, on a utilization-based pricing model, resulting in up to a 75% savings. See our pricing...

Bulk discounts: larger teckel credit top-ups earn graduated discounts — up to 12.5% — see Pricing.

Ethereum RPC Servers

teckel hosts a suite of ethereum nodes located in Western Europe. To help ensure the decentralized integrity of the ethereum network, these nodes are not hosted in cloud data-centers but in small clusters located in dedicated data-centers. The teckel nodes are “full sync” nodes meaning that they contain data for only the last 128 blocks. They are not “archive” nodes and so cannot be used for interrogating the blockchain back to the genesis block.

These nodes have their json-rpc endpoints enabled, facilitating access from external developers on a pay-as-you-go basis. Access to these endpoints is protected by API keys which are allocated to the developers’ ethereum addresses. Developers can manage their API keys via the teckel App. Developers pay for API usage via teckel credits (tc), purchased via the teckel App.

API Service Status

The current status of the API service is available via the teckel App, updated in real-time. In the App, navigate to Settings → API Status.

Example Usage

To use the teckel Ethereum endpoint API, do the following:

1. Install the teckel App and create (or import) an Ethereum Account.

2. Navigate to the Accounts page by tapping on the wallet icon in the upper right corner of the App home screen. Access the API Key Manager for the created or imported Ethereum Account by tapping "Manage API Key" on the Accounts page as seen below:

3. For illustrative purposes, we will use the following fake key d1e12345-c234-45a6-9b76-1234567891ff in the examples presented below. You would substitute your actual API key in place of this fake key.

Ethereum MAINNET Example Call

How to use the API (in both http and wss flavors) to call the net_peerCount method against the Ethereum MAINNET node suite:

HTTP via curl (on linux):

content_copy check

Call:

curl --location 'https://api.tkllabs.io/rpc_eth/mainnet/full?APIKEY=d1e12345-c234-45a6-9b76-1234567891ff' \
--header 'Content-Type: application/json' \
--data '{
 "jsonrpc":"2.0",
 "method":"net_peerCount",
 "params":[],
 "id":74
}'

Response:

{"jsonrpc":"2.0","id":74,"result":"0x31"}

WSS via wscat (on linux):

content_copy check

Call:

wscat -c wss://api.tkllabs.io/ws_eth/mainnet/full?APIKEY=d1e12345-c234-45a6-9b76-1234567891ff

Response:

Connected (press CTRL+C to quit)
>

content_copy check

Call:

{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":74}

Response:

< {"jsonrpc":"2.0","id":74,"result":"0x32"}

Ethereum SEPOLIA TESTNET Example Call

How to use the API (in both http and wss flavors) to call the net_peerCount method against the Ethereum SEPOLIA TESTNET node suite:

HTTP via curl (on linux):

content_copy check

Call:

curl --location 'https://api.tkllabs.io/rpc_eth/sepolia/full?APIKEY=d1e12345-c234-45a6-9b76-1234567891ff' \
--header 'Content-Type: application/json' \
--data '{
 "jsonrpc":"2.0",
 "method":"net_peerCount",
 "params":[],
 "id":74
}'

Response:

{"jsonrpc":"2.0","result":"0x1d","id":74}

WSS via wscat (on linux):

content_copy check

Call:

wscat -c wss://api.tkllabs.io/ws_eth/sepolia/full?APIKEY=d1e12345-c234-45a6-9b76-1234567891ff

Response:

Connected (press CTRL+C to quit)
>

content_copy check

Call:

{"jsonrpc":"2.0","method":"net_peerCount","params":[],"id":74}

Response:

< {"jsonrpc":"2.0","result":"0x1d","id":74}

Note on API Key Security

The Ethereum-RPC endpoint calls have the API key embedded in the query-string. We accept that this is not best practice from a security perspective — it is preferable to use headers, etc. — since the key can become compromised more easily. However, we have adopted this pattern to provide maximum compatibility with third-party Ethereum code libraries which still expect this format.

Should you have concerns that your API key has been compromised (and someone else may be consuming your teckel credits by using your key), simply replace the key via the API Key Manager → "Replace API Key" in the teckel App. The old key will then be immediately disabled.

n8n Community Node

For users of n8n, a subset of the teckel Ethereum JSON-RPC functions is also available as an n8n community node, n8n-nodes-teckel-ethereum, published on npm by teckel-io. This enables no-code/low-code automation builders to query the Ethereum mainnet and Sepolia testnet directly inside n8n workflows. Install via Settings → Community Nodes → Install in your n8n instance. See the teckel AI page for full installation instructions.

Errors

If the API call fails due to user error resulting in a 4xx error code, the user is charged one Base Call Fee. If the API call fails due to server error resulting in a 5xx error code, the user is not charged.