1. Introduction
  2. Basics
  3. Authorization
  4. Access to a shared Ethereum (Erigon) node

§ Introduction

RPI's API was built back heavily once we stopped actively maintaining the service. What was left is the Ethereum node that we're still running.

§ Basics

Here's a few data points about the API:

name value
root https://rugpullindex.com/api/v1/
structure RESTful

§ Authorization

Endpoints on this page require authorization in form of a HTTP Authorization header. For now, we're giving out API_KEYs (e.g. "Qab0cE") to anyone that manually contacts us for free. To use your key with methods of this API that require authorization add the following HTTP header:

Authorization: Bearer your-key

OR e.g. with a fake key:

Authorization: Bearer Qab0cE

§ Access To Our Ethereum Erigon Node

You're eligible to query our Ethereum Erigon full node RPC endpoints. The node is reverse-proxied, hence adding a HTTP Authorization: Bearer key header with your API_KEY is mandatory. To find out which json-rpc endpoints you can query and how, please refer to the reference documentation of geth, erigon or the Ethereum Wiki.

name value
url https://node.rugpullindex.com
authorization required? yes
rate limited? no
geth apis exposed eth,web3,net,txpool

Finally, an example using curl:

curl -X POST \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}' \