Explore application design across more than one blockchain. Begin with the architecture guide, compare the output-based Bitcoin model, and review the boundaries between network reads and wallet context. The provider evaluation adds a practical decision process for choosing your own infrastructure. Keep identities, source references, and failure states attached to each result instead of relying on a universal-looking balance field. 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
Bitcoin API data: think in outputs
Understand outpoints, observation status, and the difference between one output and a wallet overview.
Read the guide
A safer wallet connection checklist
Keep discovery, connection, account context, and signing permissions separate in your application.
Read the guide
How to evaluate a blockchain API provider
Turn method coverage, costs, credentials, and recovery tests into an evidence-based decision record.
Read the guide