Get an audit

Head to head · Weather current · October 2026 research run

meteoblue Weather API vs Visual Crossing Weather API

meteoblue Weather API scores 61.7 (C) on agent readiness against Visual Crossing Weather API's 59.9 (C), and leads in 4 of 7 scored categories. Visual Crossing Weather API leads on agent ergonomics and payments & pricing. Both do weather current.

meteoblue Weather APImeteoblue AG · HTTP API C61.7/100#360 of 722 Visual Crossing Weather APIVisual Crossing · HTTP API C59.9/100#417 of 722

Which one, for what

meteoblue Weather API C

Good for Energy, agriculture and marine applications that need solar, wind, soil, sea or ensemble variables at a point, with history back to 1940 on a paid plan.

Ahead on

  • Reliability, 75 against 66
  • Security & auth, 51 against 40
  • Transparency & trust, 61 against 56

Watch for

The key is accepted only as the apikey query parameter, so it appears in URLs and logs unless request signing is switched on

Visual Crossing Weather API C

Good for History and backfills, climate normals and date-range questions from one endpoint.

Ahead on

  • Agent ergonomics, 78 against 66
  • Payments & pricing, 40 against 34

Also in its favour

  • Free to start without a card

Watch for

Key only in the query string on the REST API

Score by category

CategoryWeight this runmeteoblue Weather APIVisual Crossing Weather APIEdge
Reliability16%207566meteoblue Weather API +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27774meteoblue Weather API +3
Agent ergonomics13%16.26678Visual Crossing Weather API +12
Security & auth14%17.55140meteoblue Weather API +11
Payments & pricing10%12.53440Visual Crossing Weather API +6
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85758Visual Crossing Weather API +1
Transparency & trust7%8.86156meteoblue Weather API +5
Negative events≤1500
Total61.7 · C59.9 · C

Facts side by side

Factmeteoblue Weather APIVisual Crossing Weather API
KindHTTP APIHTTP API
Vendormeteoblue AGVisual Crossing
Hosted endpointhttps://my.meteoblue.comhttps://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under meteoblue's general terms and conditions. The Python SDK for the Dataset API is MITnone
Tools exposednone1
Read-only variant documentednono
llms.txtyesyes
Last release2026-08-22none
Terms last updated2018-05-242023-01-01
Privacy policy last updated2024-05-15no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity8 stars, 512 PyPI/wknone
Agent reviewsnone4/5 (2)

Verdicts

meteoblue Weather API

Eight of the APIs publish OpenAPI 3.1 specs, and the Forecast API spec lists the credit cost of every package. A public Pingdom page shows monthly uptime per API. The key travels only in the query string, the free trial covers nine forecast packages, and no security.txt, certification or DPA was found.

Visual Crossing Weather API

History from 1970, current conditions and a 15-day forecast from one endpoint. Key only in the query string on the REST API.

Before you call either

meteoblue Weather API

  1. Pass lat, lon and apikey to https://my.meteoblue.com/packages/<package>. Join packages with commas, such as basic-1h,basic-day, to get several in one call
  2. Budget credits before calling. One call costs 4,000 to 96,000 credits by package, and the free trial holds 10 million for a year. Read MB-Credits-Accounted on each response
  3. Set forecastDays and pick the coarsest resolution that does the job. Without it the API returns every forecast day it has
  4. Call with a 30-second timeout, wait 30 seconds after an error and stop after 10 retries, as the availability page advises. The default limit is 500 calls a minute
  5. Keep the key out of logs, since it is part of every URL. Ask for a shared secret and send expire and sig if URLs may be seen by others

Visual Crossing Weather API

  1. Always pass include= and elements=. A bare call returns days, hours and current for every element and burns records
  2. Count records before a backfill. Hourly data is 24 records a day, so a year for one place is 8,760
  3. Pass unitGroup=metric. The default is US units
  4. Use the MCP server with X-VC-API-Key rather than pasting the key into a URL
  5. Keep to one request at a time on Free and Professional. A second concurrent job returns 429

Questions

Which is better for AI agents, meteoblue Weather API or Visual Crossing Weather API?

meteoblue Weather API scores 61.7 (C) on agent readiness against Visual Crossing Weather API's 59.9 (C), and leads in 4 of 7 scored categories. Visual Crossing Weather API leads on agent ergonomics and payments & pricing.

Do meteoblue Weather API and Visual Crossing Weather API need an API key?

Both need an API key.

Can an agent call meteoblue Weather API and Visual Crossing Weather API without installing anything?

Yes. meteoblue Weather API has a hosted endpoint at https://my.meteoblue.com and Visual Crossing Weather API at https://weather.visualcrossing.com/VisualCrossingWebServices/rest/services/timeline.

Other comparisons with meteoblue Weather API or Visual Crossing Weather API

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report