Sushilens
Robinhood Chain|checking…

The API Layer for Onchain Applications.

Access blockchain data, connect applications, and build powerful onchain experiences through one unified API infrastructure.

Get Started Explore APIs

24 live endpoints · 7 API families · mainnet + testnet

try it now · no key needed
GET /api/v1/network/status

Run it to see a live response from Robinhood Chain: status, latency, cache and JSON.

request pathIllustration · not live traffic
Your appx-api-keyGatewayauth · limits · cacheRPC primaryRobinhood ChainRPC fallbackauto failoverIndexerhistory · holdersvalidatemeterenvelope

Supported networks

Robinhood Chain, mainnet and testnet.

Pass ?network=testnet on any request. Health below is probed live from this server against the configured RPC providers.

Checking…
chain …
Head block
—
Block age
—
RPC latency
—
Checking…
chain …
Head block
—
Block age
—
RPC latency
—
Live endpointsimplemented & routable
Developerswallet-verified accounts
Active API keysacross all accounts
Requests · 24hmetered at the gateway

Live from the Sushilens database. Numbers start at zero on a fresh deployment — they are never seeded.

Available API services

Everything you need to read Robinhood Chain.

Only implemented endpoints are listed. Capabilities that need extra infrastructure are marked as planned in the explorer.

Blockchain Data API5

Blocks, transactions, receipts, native balances and smart contract introspection.

  • GET/v1/blocks/latest
  • GET/v1/blocks/{block}
  • GET/v1/transactions/{hash}
  • GET/v1/addresses/{address}/balance
Token API5

ERC-20 metadata, balances, transfer history and holder lists.

  • GET/v1/tokens/{address}
  • GET/v1/tokens/{address}/balances/{owner}
  • POST/v1/tokens/balances
  • GET/v1/tokens/{address}/transfers
Wallet API4

Wallet overview, transaction history, token portfolio and NFT holdings.

  • GET/v1/wallets/{address}
  • GET/v1/wallets/{address}/transactions
  • GET/v1/wallets/{address}/portfolio
  • GET/v1/wallets/{address}/nfts
DeFi API4

Uniswap V2-style pairs and V3-style pools: reserves, pricing and swap events.

  • GET/v1/defi/v2/pools/{pool}
  • GET/v1/defi/v3/pools/{pool}
  • GET/v1/defi/{version}/pools/{pool}/swaps
  • GET/v1/defi/price
NFT API3

ERC-721 / ERC-1155 collections, token ownership, token URIs and transfers.

  • GET/v1/nfts/{contract}
  • GET/v1/nfts/{contract}/{tokenId}
  • GET/v1/nfts/{contract}/transfers
Network API2

Chain health, head block, gas pricing and fee market data.

  • GET/v1/network/status
  • GET/v1/network/gas
JSON-RPC Proxy1

Authenticated, metered, read-only JSON-RPC with automatic provider failover.

  • POST/v1/rpc

API infrastructure

A real gateway, not a dashboard on top of a public RPC.

Every request to /api/v1 runs the same eight-stage pipeline. It is the same code path the Playground uses.

  1. 01

    Authenticate

    Keys are verified with a peppered HMAC in constant time. Plaintext secrets are never stored.

  2. 02

    Authorize

    Per-key API scopes and per-app browser origin allow-lists.

  3. 03

    Rate limit

    Per-key requests/minute plus daily quotas per key and per plan.

  4. 04

    Validate

    Every parameter is typed and checked before a node is touched.

  5. 05

    Cache

    Short, per-endpoint TTLs for hot reads like head block and gas.

  6. 06

    Route

    To Robinhood Chain RPC, or the explorer index for history and holders.

  7. 07

    Fail over

    Ordered RPC providers; a failing node is skipped automatically.

  8. 08

    Meter

    Each call is logged after the response is sent and feeds your analytics.

Integration

Three lines from key to data.

Use any HTTP client. Every response shares one envelope, so error handling is written once.

curl
curl -X GET "https://your-sushilens-domain/api/v1/network/status" \
  -H "x-api-key: YOUR_API_KEY"
response shape (example)
{
  "success": true,
  "data": {
    "chainId": 4663,
    "blockNumber": "…",
    "secondsSinceLastBlock": 1,
    "healthy": true
  },
  "meta": {
    "chain": "robinhood",
    "network": "mainnet",
    "chainId": 4663,
    "timestamp": "2026-11-05T07:00:00.000Z",
    "requestId": "req_…",
    "cached": false
  }
}

Why Sushilens

Built like infrastructure, owned like Web3.

Wallet-native accounts

Sign in with Ethereum. No passwords to leak, no email required.

No gas for API calls

Requests are plain HTTPS. Only optional plan upgrades ever touch the chain.

One envelope everywhere

Every endpoint returns { success, data, meta } with the chain and request ID.

Honest data sources

Each endpoint says whether it reads RPC or the explorer index. Nothing is synthesized.

Ecosystem

$SUSHILENS — utility by contract, not by promise.

The token integrates through deployed, verified contracts only. A utility shows as live once its contracts are configured — and the API works fully without any of them.

API ecosystem access

Planned

Pay for Builder / Scale plans in $SUSHILENS through SubscriptionManager, which records the tier in ApiAccessRegistry. The gateway only reads the registry — holding tokens grants nothing by itself.

SubscriptionManager + ApiAccessRegistry

Developer incentives

Planned

Epoch-based rewards for builders who ship on Robinhood Chain, distributed by Merkle proof so claims are cheap and verifiable.

EcosystemRewards

Premium API features

Planned

Higher rate limits, larger daily quotas and longer log retention attached to registry tiers.

ApiAccessRegistry

Ecosystem participation

Planned

Public, on-chain record of subscriptions and reward epochs that anyone can audit on the explorer.

Events on all contracts

Platform rewards

Planned

Usage-based reward epochs computed off-chain from metered request logs and published as Merkle roots.

EcosystemRewards

Token information

One Interface. Infinite Onchain Possibilities.

Connect MetaMask or Trust Wallet, sign one message, and get your first key in under a minute.

Get Started Read the docs