Nnodevera
API Documentation

nodevera RPC API documentation

A managed merchant RPC access service for TRON, Ethereum and Solana queries and signed transaction broadcasting. Customer API keys are bound to IP allowlists and monthly request quotas. All business RPC calls count toward the active plan.

Integration path Sign up -> buy a plan -> configure IP allowlist -> call with API Base URL + API Key.
Guides

Chain and payment workflow guides

TRON USDT API

TRC20 payment monitoring, transaction info checks and signed transaction broadcasting.

Ethereum RPC API

ERC20 receipt checks, block queries and raw transaction broadcasting through JSON-RPC.

Solana RPC API

Transaction lookup, latest blockhash reads and signed transaction broadcasting.

USDT payment API

Merchant deposit, withdrawal and fund collection workflow guidance.

Service scope

Plans are not priced as raw RPC resale. They include merchant onboarding, allowlist setup, payment-flow troubleshooting, broadcast support and deposit query assistance. Starter fits low-volume merchants, Growth fits production traffic with priority support, and Enterprise is customized by route, capacity and SLA target.

  • Unified TRON, Ethereum and Solana query and broadcast access
  • API key, IP allowlist, usage statistics and quota control
  • Automatic plan activation after verified USDT payment
  • Integration support for payment, deposit and fund collection workflows

Responsibility boundary

nodevera provides gateway access, upstream routing, request examples, on-chain payment verification and plan activation. Private key management, transaction signing, business risk control and fund security policies stay inside the customer system. Never submit private keys or seed phrases to the gateway.

Authentication

After plan activation, copy the API Base URL and API Key from the customer console. The caller's public IP must be in the allowlist.

X-API-Key: <your_api_key>
Content-Type: application/json

Bearer compatible You may also use Authorization: Bearer <your_api_key>.

Base URL

The API Base URL is shown only to paid users. Replace <api_base_url> in examples with the private API domain displayed in your console.

<api_base_url>/tron/*
<api_base_url>/eth
<api_base_url>/solana
Billing

USDT activation flow

1. Create orderSelect a plan and USDT network in the console. The system generates a random order ID, deposit address and exact payable amount.
2. Pay on-chainSend funds only to the address shown for the same network. Do not cross-chain transfer and do not underpay.
3. Submit txidCopy the transaction hash or Solana signature from your wallet. The system checks status, recipient and amount on-chain.
4. Auto activateAfter verification, nodevera creates or updates your API key and adds the current access IP to the allowlist.

TRON HTTP API

TRON uses TronGrid-compatible paths. Append the TronGrid path after /tron.

POST /tron/wallet/getnowblock 
curl -X POST <api_base_url>/tron/wallet/getnowblock \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{}'
POST /tron/wallet/gettransactioninfobyid 
curl -X POST <api_base_url>/tron/wallet/gettransactioninfobyid \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"value":"<txid>"}'
POST /tron/wallet/broadcasttransaction 
curl -X POST <api_base_url>/tron/wallet/broadcasttransaction \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '<signed_tron_transaction_json>'

Ethereum JSON-RPC

Ethereum uses standard JSON-RPC. Send all Ethereum requests to /eth.

Latest block number 
curl -X POST <api_base_url>/eth \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'
Transaction receipt 
curl -X POST <api_base_url>/eth \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_getTransactionReceipt","params":["0x<tx_hash>"]}'
Broadcast signed transaction 
curl -X POST <api_base_url>/eth \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_sendRawTransaction","params":["0x<signed_raw_tx>"]}'

Solana JSON-RPC

Solana uses standard JSON-RPC. Send all Solana requests to /solana.

Latest blockhash 
curl -X POST <api_base_url>/solana \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getLatestBlockhash","params":[]}'
Transaction query 
curl -X POST <api_base_url>/solana \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"getTransaction","params":["<signature>",{"encoding":"jsonParsed","maxSupportedTransactionVersion":0}]}'
Broadcast signed transaction 
curl -X POST <api_base_url>/solana \
  -H 'content-type: application/json' \
  -H 'X-API-Key: <your_api_key>' \
  -d '{"jsonrpc":"2.0","id":1,"method":"sendTransaction","params":["<base64_or_base58_signed_tx>"]}'

Usage and allowlist

Every TRON, Ethereum and Solana request is counted per customer. Exceeding the monthly plan quota returns 429.

curl <api_base_url>/api/me \
  -H 'X-API-Key: <your_api_key>'

Common errors

401API key is missing or invalid.
403API key is disabled, or caller IP is not in the allowlist.
429Monthly request quota is exhausted, or an upstream key is throttled.
502Upstream RPC is temporarily unavailable. The gateway will try alternate upstreams when configured.