API guide
Best Free APIs for Developers in 2026: 50+ APIs, Limits & Auth
Best free APIs for developers in 2026, organized by use case with current free-tier limits, auth requirements, commercial-use caveats, and official docs checks.
TL;DR
The best free API for most developers in 2026 is still Open-Meteo if you need weather data because it needs no API key and publishes a clear free non-commercial limit. For key-gated weather, compare OpenWeatherMap and WeatherAPI.com because their free plans now optimize for different quotas. For no-auth reference data, start with REST Countries, Wikipedia, Open Library, Frankfurter, JSONPlaceholder, and Hacker News. For production email, Resend is the most practical free starting point. For maps and routing, OpenRouteService and OpenStreetMap-backed tools are the safest no-Google starting points.
Use this page as a short list, not a contract. Free tiers change. Before you ship, click through to the official docs or pricing page, confirm the current quota, and check whether commercial use is allowed. APIScout keeps the canonical directory list at the free APIs category, while this guide explains which options fit common developer projects.
Quick picks by developer use case
| If you need... | Start with | Why it is usually the best free starting point | Watch out for |
|---|---|---|---|
| Weather forecast with no signup | Open-Meteo | No key, documented non-commercial free quota, broad forecast variables | Commercial use needs the paid/customer endpoint |
| Weather forecast with an upgrade path | OpenWeatherMap | Keyed weather APIs, free access for current/forecast products, paid One Call path | One Call 3.0 is a separate pay-per-call product after the free daily allowance |
| Higher free weather quota | WeatherAPI.com | Published free plan with 100K calls/month | Attribution and monthly quota reset rules matter |
| Country/reference data | REST Countries | No auth, simple REST responses, stable schema | Cache results; do not call it on every render |
| Currency conversion | Frankfurter | ECB-backed, no key, daily rates | Not a real-time trading feed |
| Transactional email | Resend | 3K emails/month and 100/day on the free plan | Domain verification and daily limit before production scale |
| News prototypes | News API | 100 requests/day for development and testing | Developer plan is not for production/commercial use |
| API integration testing | httpbin, JSONPlaceholder, Webhook.site | No-key endpoints that are ideal for demos and HTTP client tests | Do not treat test APIs as production data stores |
| Maps and routing | OpenRouteService, Nominatim, Overpass | OpenStreetMap-backed routes, geocoding, and map data | Respect per-second/fair-use policies and attribution |
| AI prototypes | Hugging Face, Gemini, Groq, OpenRouter | Useful free or free-credit access for model evaluation | Model-specific rate limits change frequently |
Source checks for high-intent queries
Last checked: 2026-05-15.
GSC demand for this page is concentrated around "best free APIs for developers 2026" plus weather-limit queries such as "OpenWeatherMap API free tier limits 2026" and "Open-Meteo API rate limits free tier 2026." The volatile claims below were rechecked against official pages before this refresh:
- Open-Meteo pricing: free API is for non-commercial use, rate-limited to 10,000 calls/day, 5,000 calls/hour, and 600 calls/minute; paid/customer plans remove daily limits for commercial use.
- OpenWeatherMap pricing: the free Weather API plan lists 60 calls/minute and 1,000,000 calls/month for current weather, 5-day forecast, air pollution, and geocoding APIs. One Call 3.0 separately lists the first 1,000 API calls/day as free on the pay-per-call product.
- WeatherAPI.com pricing: the free plan lists 100K calls/month and resets monthly; going over the request limit stops data until the next monthly reset.
- News API pricing: Developer is free for development and testing, includes 100 requests/day, and is not for staging or production.
- Resend pricing: Free includes 3,000 emails/month and a 100 emails/day daily limit.
- Alpha Vantage premium page: most endpoints can be accessed for free, but the standard free limit is 25 API requests/day.
How to choose a free API without getting trapped
A useful free API has three properties: the quota is high enough for the product you are building, the authentication model is safe for your architecture, and the terms permit your use case. A free weather API for a weekend project is different from a free weather API for a commercial logistics dashboard. A no-key public-data API is great for a demo, but it may be a poor fit if you need per-customer usage controls, support, or uptime commitments.
Use this checklist before integrating any free API:
- Confirm the current quota on the provider's official docs or pricing page.
- Check whether the free tier permits production or commercial usage.
- Note whether the limit is per IP address, per API key, per account, per user, per month, or per day.
- Prefer server-side calls for key-gated APIs so keys never ship to the browser.
- Cache stable data aggressively and set TTLs that match data freshness.
- Build graceful handling for
429 Too Many Requestsresponses. - Keep a migration path to a paid tier or alternate provider before the API becomes core product infrastructure.
For deeper implementation patterns, use APIScout's API caching strategies guide, API rate limiting best practices, and OAuth2 vs API keys vs JWT comparison.
Best free weather and location APIs
Weather is the highest-intent category for this page because developers search for exact free-tier limits before choosing a provider. Here is the current practical split.
| API | Free tier to verify | Auth | Best fit |
|---|---|---|---|
| Open-Meteo | 10,000 calls/day, 5,000/hour, 600/min on the non-commercial free API | None | No-signup forecasts, prototypes, hobby projects, education |
| OpenWeatherMap Current/Forecast APIs | 60 calls/minute and 1,000,000 calls/month on the free Weather API plan | API key | Apps that want a familiar provider and a commercial upgrade path |
| OpenWeatherMap One Call 3.0 | First 1,000 calls/day free on the separate pay-per-call product | API key | Apps that need current, minutely, hourly, daily, alerts, and historical bundles |
| WeatherAPI.com | 100K calls/month on the free plan | API key | Higher-volume prototypes that need forecast, realtime, and simple JSON responses |
| Nominatim | 1 request/second on the public OpenStreetMap service | None | Forward/reverse geocoding without Google Maps |
| IP-API | 45 requests/minute on the free non-commercial endpoint | None | Lightweight IP geolocation and timezone lookup |
| ipinfo.io | 50K requests/month on the free tier | Token for higher-detail data | IP enrichment, ASN, privacy, and localization signals |
Open-Meteo
Open-Meteo is the best first stop when the query is "free weather API no key." The free endpoint does not require signup and exposes forecast, historical weather, air quality, marine, geocoding, flood, and related weather APIs. The key caveat is commercial use: Open-Meteo's free API is non-commercial and rate-limited, while customer API plans are the path for commercial workloads.
curl "https://api.open-meteo.com/v1/forecast?latitude=51.5&longitude=-0.12¤t=temperature_2m,wind_speed_10m"
Use Open-Meteo when: you need a keyless weather API, you can cache by coordinate and forecast window, and your usage is non-commercial or evaluation-stage.
OpenWeatherMap
OpenWeatherMap is still the familiar default for keyed weather data. The important 2026 nuance is that the general free Weather API plan and One Call 3.0 are different products. If you only need current weather, 5-day/3-hour forecast, air pollution, and geocoding, the free Weather API plan is the relevant quota. If you need the bundled One Call response, inspect the separate One Call pay-per-call limit before building.
Use OpenWeatherMap when: you want a mainstream provider, you can protect an API key server-side, and you need a straightforward paid upgrade path.
WeatherAPI.com
WeatherAPI.com is worth comparing when the main blocker is quota. Its public pricing page lists a 100K calls/month free plan, which can be more comfortable than a low daily limit for cache-friendly apps. The provider also publishes clear reset behavior: if you exceed the monthly call limit, data stops until the quota resets.
Use WeatherAPI.com when: you need a keyed free plan with a generous monthly quota and can accept monthly quota enforcement.
See the weather and climate API guide, Tomorrow.io vs OpenWeatherMap comparison, and OpenWeatherMap vs Weatherbit comparison if weather is core to your product.
Best free AI and machine-learning APIs
AI free tiers change faster than open-data APIs. Treat the list below as a discovery map, then verify model-specific limits before building.
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| Hugging Face Inference | Free/rate-limited access to hosted open models and a large model hub | Token | Prototyping model calls and evaluating open models |
| Google Gemini API | Free tier with model-specific request and token limits | API key | Long-context and multimodal prototypes |
| Groq | Free developer access with model-specific rate limits | API key | Low-latency inference experiments |
| OpenRouter | Free models with provider-specific limits | API key | Multi-provider routing and model fallback tests |
| Together AI | Free credits on signup | API key | Comparing open-source LLMs before self-hosting or paying |
| Replicate | Free credits on signup | API token | Image, video, audio, and async model experiments |
| Cohere | Free developer access for Command and Embed models | API key | Embeddings, RAG, and semantic search prototypes |
Do not put an AI provider's key in a browser app. Proxy requests through your server, add per-user budgets, and cache deterministic outputs when terms allow it. For narrower picks, read best AI APIs for developers, free AI APIs for developers, and best AI agent APIs.
Best free maps, routing, and geocoding APIs
Maps are often "free until suddenly expensive" because tiles, geocoding, and routing each have different cost drivers.
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| Nominatim | Public OpenStreetMap geocoder, 1 request/second policy | None | Low-volume geocoding and reverse geocoding |
| OpenRouteService | Free routing/geocoding quota with API key | API key | Directions, isochrones, distance matrices, and routing |
| Overpass API | Public OSM data extraction under fair-use expectations | None | POI search and custom spatial queries |
| MapTiler Cloud | Free tile/geocoding allowance | API key | Map display with OpenStreetMap-derived tiles |
| Geoapify | Free geocoding/maps allowance | API key | Geocoding plus place search experiments |
Use Nominatim for careful server-side geocoding, not client-side autocomplete spam. Use Overpass when you need raw OpenStreetMap entities rather than address lookup. Use OpenRouteService when routing, distance matrices, or isochrones are the actual product feature.
# OpenStreetMap POI extraction with Overpass
curl "https://overpass-api.de/api/interpreter?data=[out:json];node[amenity=cafe](51.5,-0.2,51.6,0.0);out;"
See the maps and location API comparison, geocoding API guide, and Google Maps vs Mapbox vs HERE comparison before committing to a map stack.
Best free data and knowledge APIs
Open reference data is usually the safest category for free APIs because it is often backed by public institutions, open licenses, or community datasets rather than a venture-backed free tier.
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| REST Countries | Free country metadata | None | Country pickers, localization, currency/language lookup |
| Wikipedia REST API | Free summaries and page data under Wikimedia policies | None | Entity lookup and content enrichment |
| Wikidata Query Service | Free structured knowledge graph queries under usage policy | None | Entity IDs, facts, and linked data |
| Open Library | Free book and edition metadata | None | Reading apps and ISBN lookup |
| Open Food Facts | Free food-product database | None for read | Nutrition, barcode, and allergen apps |
| PokéAPI | Free structured Pokémon data | None | Learning projects and predictable demo data |
| World Time API | Free timezone/current-time endpoint | None | Timezone-aware scheduling demos |
| Data.gov | Free federal dataset catalog | API key for many endpoints | Civic-tech and public-data projects |
| World Bank API | Free economic and development indicators | None | Data journalism and global comparison tools |
curl "https://restcountries.com/v3.1/name/canada"
The main production rule is caching. Country lists, book metadata, and public indicators rarely need to be fetched on every request. Cache them at build time or behind a durable server-side cache.
Best free communication APIs
Communication APIs are rarely unlimited because abuse prevention and deliverability costs are real. Free tiers are best for development, early product validation, and low-volume transactional flows.
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| Resend | 3,000 emails/month, 100/day | API key | Transactional email in early-stage apps |
| Mailjet | Free daily/monthly email allowance | API key + secret | Higher-volume email testing |
| Postmark | Small free test allowance | Server token | Deliverability testing and transactional email trials |
| Twilio | Trial credits, verified numbers, trial message restrictions | Account SID + token | SMS/voice proof-of-concepts |
| SendGrid | Free email allowance varies by plan/region | API key | Transactional email experiments |
| Webhook.site | One active request-capture URL per session | None | Debugging webhook payloads during development |
If an app depends on email or SMS for login, payments, or user notifications, treat the free tier as a staging environment. Move critical production flows to a paid plan with monitoring and support once real users depend on it.
For SMS-specific choices, read best SMS APIs for developers and Twilio vs Vonage vs Sinch.
Best free finance and currency APIs
Finance APIs need extra caution because "free" may mean delayed data, personal use only, or strict daily caps.
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| Frankfurter | Free ECB-backed exchange rates | None | Currency conversion with daily rates |
| Alpha Vantage | Free access to most endpoints, standard 25 requests/day limit | API key | Stock and macro-data prototypes |
| CoinGecko | Free crypto-market API access with rate limits | Optional key | Crypto prices and market metadata |
| Financial Modeling Prep | Free daily quota | API key | Fundamental data prototypes |
| ExchangeRate-API | Free monthly quota | API key | Simple fiat currency conversion |
| Open Exchange Rates | Free/latest endpoint limits vary by plan | App ID | Exchange-rate experiments |
curl "https://api.frankfurter.app/latest?from=USD&to=EUR,GBP,JPY"
Frankfurter is the safest free default when daily ECB exchange rates are enough. If you need real-time quotes, intraday financial data, or commercial redistribution rights, verify the exact license and consider a paid plan before launch. APIScout's free currency exchange API comparison covers this category in more depth.
Best free developer and testing APIs
These APIs are useful because they help you build and test other APIs.
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| GitHub REST API | 60 requests/hour unauthenticated, 5,000/hour with token | None, PAT, OAuth | Repo analytics, open-source dashboards, CI tools |
| Hacker News Firebase API | Free public endpoints | None | News readers and teaching real-time APIs |
| httpbin | Free HTTP request/response inspection | None | Debugging HTTP clients and headers |
| JSONPlaceholder | Free fake REST resources | None | Frontend demos and integration tests |
| Webhook.site | One active URL per session | None | Inspecting outbound webhooks |
| QR Server / goqr.me | Free QR image generation | None | QR-code demos and simple utilities |
| Random User Generator | Free fake user profiles | None | Seed data and mock UI states |
| DiceBear | Free generated avatars | None | Placeholder avatars and user defaults |
| Abstract API | Free product-specific quotas | API key | Email validation, phone validation, IP lookup |
# Public GitHub data without a token
curl "https://api.github.com/repos/vercel/next.js"
Use testing APIs in tests and demos, not as dependencies for customer-facing core flows. If a demo API goes down, your app should degrade gracefully.
Best free media, science, and public-health APIs
| API | Free access shape | Auth | Best fit |
|---|---|---|---|
| TMDB | Free for non-commercial use with key | API key or bearer token | Movie and TV metadata apps |
| Last.fm API | Free read access with key | API key, OAuth for user writes | Music metadata and listening-history apps |
| Open Trivia DB | Free trivia questions | None | Quiz apps and teaching examples |
| JokeAPI | Free joke endpoint with safety filters | None | Lightweight demo content |
| NASA Open APIs | Free key with higher hourly limit, demo key lower limit | API key | Space, Mars rover, asteroid, and earth imagery apps |
| OpenFDA | Free FDA datasets with higher key-based quota | None or API key | Health, drug, recall, and safety-data tools |
| disease.sh | Free public-health datasets | None | Public-health dashboards and teaching datasets |
TMDB, NASA, and OpenFDA are powerful but require careful terms review. Check attribution, permitted use, and whether your product is allowed to redistribute or cache the data.
Authentication patterns you will see in free APIs
No authentication
Keyless APIs such as Open-Meteo, REST Countries, Frankfurter, JSONPlaceholder, httpbin, and many public datasets are the easiest to try. The tradeoff is that the provider generally limits by IP address and has less ability to distinguish your production traffic from someone else's traffic behind the same network.
Use keyless APIs for prototypes, open data, and low-risk lookups. Do not rely on them for high-volume client-side traffic unless the provider explicitly supports that use case.
API key
API keys are the most common free-tier pattern. They let the provider enforce quota by account, but they also create secret-management work for you. Keep keys in environment variables, never commit them, and avoid putting them in browser JavaScript. If a browser app needs the data, proxy through your own server or edge function and apply your own rate limits.
OAuth 2.0
OAuth appears when an API acts on behalf of a user. GitHub, Last.fm write operations, and many communication APIs use OAuth for user-specific actions. OAuth is overkill for read-only public data, but it is the right path when the user grants scoped permissions.
Bearer tokens and PATs
Bearer tokens and personal access tokens are common for developer APIs. Treat them like passwords: scope them narrowly, rotate them when exposed, and store them only server-side.
How to stay on a free tier longer
Most apps exceed free quotas because they make duplicate calls, not because they have millions of users.
Cache by data freshness. Currency rates can usually be cached for a day. Country lists can be cached at build time. Weather forecasts may tolerate 5-15 minute TTLs depending on the product. Match cache TTLs to user expectations and provider terms.
Batch when the API supports it. Fetching 50 currencies, countries, or crypto assets one by one is almost always wasteful. Look for /all, bulk, multi-symbol, or batch endpoints.
Track usage before quota is exhausted. Add a simple daily counter per provider and alert around 70% of the free quota. That gives you time to cache, throttle, or upgrade before users see failures.
Back off on 429s. Implement exponential backoff with jitter and respect Retry-After headers. Retrying immediately after a rate-limit response burns more quota and can get keys suspended.
Separate dev and production keys. Development traffic can consume production quotas if every environment uses the same key. Use separate accounts or keys when the provider allows it, and mock external API calls in tests.
Quick comparison table
| API | Category | Free access shape | Auth |
|---|---|---|---|
| Open-Meteo | Weather | 10K/day non-commercial free API | None |
| OpenWeatherMap Weather APIs | Weather | 60/min and 1M/month on free Weather API plan | API key |
| OpenWeatherMap One Call 3.0 | Weather | First 1K/day free on separate pay-per-call product | API key |
| WeatherAPI.com | Weather | 100K/month | API key |
| Nominatim | Geocoding | 1 request/second public service policy | None |
| IP-API | Geolocation | 45/min on free endpoint | None |
| ipinfo.io | Geolocation | 50K/month | None/token |
| Hugging Face | AI/ML | Rate-limited/free access varies by model | Token |
| Gemini API | AI/ML | Free tier with model-specific limits | API key |
| Groq | AI/ML | Free developer limits vary by model | API key |
| OpenRouter | AI/ML | Free models with provider-specific limits | API key |
| Together AI | AI/ML | Free credits on signup | API key |
| Replicate | AI/ML | Free credits on signup | API token |
| Cohere | AI/ML | Free developer access | API key |
| OpenRouteService | Maps | Free routing/geocoding quota | API key |
| Overpass API | Maps | Fair-use OSM data queries | None |
| MapTiler Cloud | Maps | Free tile/geocoding allowance | API key |
| REST Countries | Reference data | Free public API | None |
| Wikipedia REST API | Knowledge | Free public API under Wikimedia policy | None |
| Wikidata Query Service | Knowledge | Free public query service under usage policy | None |
| Open Library | Books | Free public API | None |
| Open Food Facts | Food | Free read API | None |
| PokéAPI | Demo/reference | Free public API | None |
| World Time API | Time | Free public API | None |
| Data.gov | Government data | Free dataset APIs | API key for many datasets |
| World Bank API | Government/econ | Free public API | None |
| Resend | 3K/month, 100/day | API key | |
| Mailjet | Free email allowance | API key + secret | |
| Postmark | Small free test allowance | Server token | |
| Twilio | SMS/voice | Trial credits | Account SID/token |
| News API | News | 100/day for development/testing | API key |
| Frankfurter | Currency | Free ECB-backed rates | None |
| Alpha Vantage | Finance | Standard 25/day free limit | API key |
| CoinGecko | Crypto | Free crypto API access with rate limits | Optional key |
| Financial Modeling Prep | Finance | Free daily quota | API key |
| ExchangeRate-API | Currency | Free monthly quota | API key |
| TMDB | Media | Free non-commercial use | API key/bearer token |
| Last.fm | Music | Free read access | API key/OAuth |
| Open Trivia DB | Media | Free public API | None |
| JokeAPI | Media | Free public API | None |
| NASA APIs | Science | Free key/demo key limits | API key |
| OpenFDA | Health/government | Free public API, higher key limit | None/API key |
| disease.sh | Public health | Free public API | None |
| GitHub REST API | Developer tools | 60/hour unauth, 5K/hour token | None/PAT/OAuth |
| Hacker News Firebase API | Developer tools | Free public API | None |
| httpbin | Testing | Free public service | None |
| JSONPlaceholder | Testing | Free fake REST API | None |
| Webhook.site | Testing | One free active URL per session | None |
| QR Server / goqr.me | Utility | Free QR image endpoint | None |
| Random User Generator | Utility | Free random user profiles | None |
| DiceBear | Utility | Free generated avatars | None |
| Abstract API | Utility | Product-specific free quotas | API key |
When to upgrade from free
Upgrade when the free tier starts shaping product behavior in a way users notice.
- You are caching data longer than the product can justify.
- The provider's free terms do not allow production or commercial use.
- You need uptime commitments, support, or incident escalation.
- Attribution requirements conflict with your product or customer requirements.
- You need higher data freshness, historical depth, or redistribution rights.
- Your usage regularly approaches 70-80% of the free quota even after caching and batching.
The best upgrade path is one you understood before launch. If a provider hides pricing behind sales calls, requires annual contracts too early, or has unclear data rights, keep a second provider in your architecture notes.
Related APIScout guides
- Browse the free APIs category
- Best weather and climate APIs
- Best AI APIs for developers
- Free AI APIs for developers
- Best maps and location APIs
- Best free currency exchange rate APIs
- API authentication: OAuth2 vs API keys vs JWT
- How to handle API rate limits gracefully
Conclusion
The best free APIs in 2026 are not just the ones with the biggest quota. They are the APIs with clear docs, stable authentication, explicit usage terms, transparent upgrade paths, and limits you can design around. Start with no-key public-data APIs when you are prototyping, move key-gated APIs behind your server when you need production control, and verify every pricing or rate-limit claim on the provider's official page before users depend on it.
Ready to compare options beyond this shortlist? Browse the APIScout API directory or filter directly to free APIs.
The API Integration Checklist (Free PDF)
Step-by-step checklist: auth setup, rate limit handling, error codes, SDK evaluation, and pricing comparison for 50+ APIs. Used by 200+ developers.
Join 200+ developers. Unsubscribe in one click.