, so every page shipped two description tags and crawlers read this generic one instead of the page's own. Each route sets its own. --> %sveltekit.head%
+ historical-weather-data

> Historical weather data

// Returns historical weather observations for a specific date and location

weathergeohistoricaltime_series

Returns historical weather observations for a specific date and location. Agents can request it by capability ID weather.historical, or by plain intent — EntRoute resolves phrases like “historical weather”, “past weather” and “weather on date” to this capability.

EntRoute currently lists 1 endpoint from 1 provider for weather.historical, priced at $0.004 per call, settled in USDC on Base. The quickest responds in about 250ms at the 95th percentile. Every endpoint below is re-probed every 10 minutes for a valid 402 payment challenge; the ordering blends measured success rate, latency and price rather than provider claims.

// aliases.json

These phrases resolve to this capability with intent-based discovery.

"historical weather" "past weather" "weather on date" "weather history"
// discover.sh
curl -X POST https://api.entroute.com/discover \
  -H "Content-Type: application/json" \
  -d '{"capability_id": "weather.historical"}'
// endpoints.json
1 results
#1 WeatherAPI Pro listed
$0.0040
https://api.weatherapi.example.com/v1/historical
success: N/A
latency: 250ms
// integrate.md

Use this capability in your agent or application:

TypeScript SDK → MCP Server → REST API →
// faq

Frequently asked questions about Historical weather data

How much does a historical weather data API call cost?

Endpoints listed for weather.historical on EntRoute are priced at $0.004 per call. Payment is per request — there is no subscription, account or API key. Prices shown are read from each endpoint's live 402 response, not from a provider-supplied catalogue.

How do AI agents pay for historical weather data endpoints?

Via the x402 protocol. The agent calls the endpoint, receives an HTTP 402 Payment Required response describing the price and recipient, signs a stablecoin payment (USDC on Base), and retries the request with proof of payment. The whole exchange takes seconds and needs no human approval.

How many providers offer historical weather data?

1 endpoint is currently listed for weather.historical across 1 provider. That number moves as endpoints are added and as failing ones are demoted.

Are these historical weather data endpoints verified?

Each one is probed every 10 minutes to confirm it still returns a well-formed 402 challenge on a payable network. Endpoints whose 7-day success rate drops below 50% are moved out of the ranked list into fallbacks with an explicit exclusion reason, so an agent can decide whether to retry them.

← Back to capabilities