Data & APIs
Live currency, crypto, weather, and world data. 8 tools
Live reference data, fetched the moment you ask for it: exchange rates and market prices, country facts, weather, public holidays and dictionary definitions — plus a quote generator and a link shortener. The converters that move data between JSON, CSV, XML and YAML are not here; they are in Converters.
Every tool on this page needs a server, because the answer lives on someone else's. Most only relay the query and forget it — the exception is the URL shortener, which hands your full link to a third party that keeps it permanently on a public address.
All 8 data & apis
Currency Converter
Convert between 160+ world currencies at live exchange rates.
Crypto Price Tracker
Live prices, market cap, and 24h change for top cryptocurrencies.
Country Info Lookup
Population, capital, currency, languages, and flag for any country.
Weather Lookup
Current conditions and a 7-day forecast for any city.
Public Holidays
See official public holidays for any country and year.
Dictionary & Definitions
Definitions, phonetics, synonyms, and examples for English words.
Random Quote Generator
Fetch inspiring quotes to copy, share, or seed designs.
URL Shortener
Shorten long links into tidy, shareable URLs.
What to know before you pick one
CSV is not a standard, which is why it keeps breaking
There is no single specification everyone follows. Separators vary by locale, quoting rules differ, line endings differ between operating systems, and a leading character can make a spreadsheet interpret a field as a formula. Most “corrupted” exports are not corrupted at all — they are one program’s conventions being read by another program with different ones.
Flattening structure loses information permanently
JSON and YAML can nest; a spreadsheet grid cannot. Converting nested data into rows and columns has to flatten or discard the shape, and converting back cannot reconstruct what was thrown away. If a round trip through a flat format is unavoidable, keep the original rather than treating the flattened version as the source of truth.
Numbers stop being numbers surprisingly easily
Leading zeros disappear, long identifiers get rewritten in scientific notation, and values that merely look like dates get converted into them. This is the single most common way real data is damaged in transit, and it usually happens silently in a spreadsheet rather than in any tool. Identifiers should be treated as text from the beginning, not repaired afterwards.
Encoding decides whether names survive
A file saved in one character encoding and opened as another produces the familiar run of mangled symbols where accented letters and non-Latin scripts used to be. UTF-8 is the answer nearly everywhere, and it is worth setting deliberately rather than accepting whatever a program defaults to — because the damage appears in exactly the fields that matter most, like people’s names.