About this tool
Get a browser notification when your chosen crypto asset crosses a target price.
Crypto Price Alarm pulls the current spot price for any coin by its CoinGecko asset ID and reports the price, the 24-hour change as a percentage, and the exact timestamp the source last updated that figure. It is for anyone watching a target level on an asset and wanting a clean, on-demand reading rather than a chart-heavy exchange page. Enter an ID such as `bitcoin` or `ethereum`, request a reading, and you get a four-row result plus the named source it came from.
Open Crypto Price Alarm on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
The result shows the source's own last-updated time in ISO format, so you can tell a live quote from one that has been sitting still for minutes.
The 24-hour change is returned to three decimal places alongside the price, which is enough to see direction and size in one line.
Readings come from the CoinGecko simple price API and the result says so, so you always know which provider's number you are quoting.
A CoinGecko asset ID, not a ticker symbol — `bitcoin` rather than BTC, `ethereum` rather than ETH. Spaces are converted to hyphens and the text is lowercased, so 'Binance Coin' resolves to `binance-coin`; if the ID does not exist the tool reports that the asset was not found.
No — readings are fetched on demand when you request them, so nothing runs in the background and no notification fires on its own. Use it to check a level, not as an unattended watcher.
US dollars by default. The request also accepts a currency parameter, and whichever currency is used is printed next to the figure so the unit is never ambiguous.
Requests are cut off after 9 seconds, and the upstream price API applies its own rate limits, so a rapid burst of lookups or a slow provider will surface an error instead of a stale figure. Waiting a moment and requesting again usually clears it.