Follow method-oriented requests from the message envelope to network-specific response handling. The introductory guide establishes the adapter boundary; the Ethereum and Solana articles show how similar request shapes carry different units and context. The transport and retry articles add the operational layer. Read them together to separate a successful HTTP exchange from a valid, useful application result. Follow the articles below in publication order or choose the guide closest to your current feature. For related definitions, keep the API glossary nearby; for source-specific details, use the primary reference library. Every article includes its own next steps, so this topic page can work as a starting point or as a way to revisit a particular implementation decision.
Related articles
Multichain APIs: a practical developer guide
Build a shared application model without hiding the differences between Ethereum, Solana, and Bitcoin.
Read the guide
Read Ethereum balances with JSON-RPC
A read-only walkthrough of network identity, exact quantities, block context, and useful failure states.
Read the guide
Solana balances, slots, and commitment
Carry cluster identity, commitment, lamports, and response context all the way to your interface.
Read the guide
JSON-RPC, REST, or WebSockets?
Match your request pattern to the feature, then design reconnection and recovery before scaling.
Read the guide
Rate limits and retries, minus the chaos
Classify failures, respect rate-limit signals, and put every operation on a bounded recovery budget.
Read the guide