A treasury assistant should show which wallet and networks it queried, what came back, and when. API3's dRPC integration on AirnodeHub offers a way to keep that evidence beside a holdings snapshot, so another reader can check the original responses.

The dRPC listing is labelled “by API3.” API3 says it builds the Hub's current integrations. This is an API3-built Airnode integration over dRPC; the signature belongs to the serving Airnode. Integration documentation

Scope the report before reading balances

Consider a treasury operator who wants a snapshot for one public EVM wallet, with recent transfers on a selected network. The useful output is a dated table of returned holdings, a bounded transaction list and the receipts behind both. This is a proposed workflow; the examples below have been checked against the API description and have not been executed.

Start by checking indexed coverage. The listing describes dRPC's broader RPC network as spanning 100+ chains, but that does not establish wallet-indexing coverage. dRPC documents a separate supported-chains query for its Data API. Read its current result and any remaining pages before selecting a network. Coverage documentation

Then inspect the Airnode's current API document. It defines the available operations, parameters and verification address. Keep a copy with the report. The chain-specific balance operation requires a network that dRPC both routes and indexes for EVM portfolios; a successful RPC connection alone is insufficient.

Make a small set of documented requests

These are request examples derived from the deployed API document. Replace the uppercase placeholders with a public treasury address and the textual Wallet API id returned by discovery, rather than its numeric id_numeric. Check the current listing and API description for availability and access requirements before making data calls.

# Read the API contract and verification metadata.
curl --silent --show-error https://airnode-drpc.fly.dev/

# Discover indexed chains; continue pagination if needed.
curl --request POST https://airnode-drpc.fly.dev/ \
  --header 'Content-Type: application/json' \
  --data '{"operation":"supportedChains","parameters":{"limit":100}}'

# Request one wallet's balances on a selected indexed EVM network.
curl --request POST https://airnode-drpc.fly.dev/ \
  --header 'Content-Type: application/json' \
  --data '{"operation":"chainWalletBalances","parameters":{"chain":"CHAIN_ID","address":"PUBLIC_TREASURY_ADDRESS"}}'

# Request a bounded history page on the same network.
curl --request POST https://airnode-drpc.fly.dev/ \
  --header 'Content-Type: application/json' \
  --data '{"operation":"transactionHistory","parameters":{"address":"PUBLIC_TREASURY_ADDRESS","chain_ids":"CHAIN_ID","limit":25}}'

Keep the history page's continuation token if one is returned. A page capped at 25 records does not establish the wallet's total transaction count. The current Airnode envelope exposes no start or end filter for this operation, even though dRPC's upstream interface documents time filters. Label the output as a recent-history page; a complete period report requires pagination, timestamp filtering in the application and an explicit completeness check. Transaction documentation

Verify each receipt before summarizing it

For the JSON envelope, preserve the exact operation, parameters and complete response. Check the expected verification address from the API document, reconstruct the request hash, and verify the EIP-191 signature over the hash, signed timestamp and returned data. Include any response projection in the request identity if one was used. Apply an application freshness policy to the signed timestamp; it does not establish when every underlying balance was last indexed. The attestation specification documents the algorithm and client example.

A signature establishes which configured Airnode attested to that request and response. The Hub distinguishes original-source operators from integrations run over another provider: the latter provide relay provenance. A valid signature does not independently establish the truth or completeness of upstream balances, prices or transaction records. Consumer documentation

Store the untouched receipts separately from the assistant's calculations. A practical report can record the wallet, requested network, collection time, verification status, returned holdings and USD valuations, plus the transfer page and pagination status. Mark missing data or failed reads explicitly instead of treating them as zero.

Keep the accounting limits visible

An indexed portfolio is one input to treasury review. Reconcile it with the treasury's address inventory and position records before describing total assets. dRPC's portfolio documentation describes indexed native tokens, ERC-20 balances and DeFi positions; valuation still depends on returned coverage and pricing. Portfolio documentation

For a later historical view, the listing also exposes token net-worth history. dRPC says that history excludes DeFi changes, so it cannot by itself explain total treasury profit or loss. Historical net-worth documentation

The application supplies the comparison, saved history and review rules. The integration supplies documented reads with receipts that can travel alongside them.

Inspect the dRPC operations on AirnodeHub and begin with one scoped wallet report.