The last traded price is useful for orientation, but it may be stale if the market has low volume.
Application · Angular · FastAPI · CCXT
Cryptocurrency price comparison app
Separate application to query exchanges, pairs, ticker, bid/ask and price comparison from the published API.
What can you do in this app?
This tool lets you inspect crypto market data from a custom API connected to several exchanges.
It is designed as a learning and analysis tool, not as a trading interface.
How to use it
- Refresh exchanges
Load the available exchanges from the API. - Select markets
Choose one or more exchanges for comparison. - Search a pair
Type a symbol like BTC/USDT. - Inspect the data
Review ticker, bid/ask and cross-exchange comparison.
Price differences do not automatically imply real arbitrage opportunities because fees, liquidity and execution time matter.
This page is also a frontend integration example: a FastAPI backend normalizes exchange data, Angular handles loading and error states, and the table helps compare whether different markets report similar prices for the same pair. For implementation details, continue with the technical API article.
How to read the market data
The spread between bid and ask is often more informative than the last price when comparing execution quality.
Always check whether the returned data is recent. Two exchanges can look different simply because one response is older.
A price gap only becomes relevant after considering fees, liquidity, transfer costs and withdrawal limits.
Interactive query
Available exchanges
Load the exchanges supported by the API and choose the ones you want to compare.
Pairs by exchange
Cross-exchange comparison
Enter a symbol and compare its price across the selected exchanges.
Production checklist
Frontend responsibilities
Keep loading states, empty states and exchange-specific errors visible. A financial table should never fail silently or mix old and new responses without telling the user.
Backend responsibilities
Cache stable catalog data, protect credentials, normalize provider responses and expose timestamps so Angular can decide whether a result is still useful.
This app is intentionally separated from the technical article. The app satisfies the practical intent, while the architecture article explains how the API is organized.