Start with the Bitcoin data guide to define an output-oriented feature and its coverage. Then use the provider evaluation to test whether your chosen source can supply the exact records and history you need. Keep transaction identifiers and output positions distinct. A narrow successful lookup should not become an unsupported claim of comprehensive wallet discovery, and a pricing estimate should not replace a practical compatibility test. 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
Bitcoin API data: think in outputs
Understand outpoints, observation status, and the difference between one output and a wallet overview.
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