APIXU Weather API

Name: APIXU Weather API API
Brand: APIXU Weather API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey6 EndpointsREST

For Agents

Look up current weather, forecasts, location search, and historical weather for any location through the legacy APIXU/Weatherstack endpoints.

Quickstart

Get started with APIXU Weather API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"get current weather for a city"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with APIXU Weather API API.

Fetch real-time current weather for a location via GET /current.json

Retrieve multi-day weather forecasts via GET /forecast.json

Autocomplete or fuzzy-search locations by name with GET /search.json

Pull historical weather observations for a date range via GET /history.json

GET STARTED

Start building with APIXU Weather API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for APIXU Weather API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for APIXU Weather API, keeping it validated and agent-ready. APIXU provides current weather, multi-day forecasts, location autocomplete search, and historical weather data for any location worldwide. The service has been rebranded as Weatherstack but the original APIXU endpoints remain documented here, returning JSON or XML for integrators that depend on the legacy contract. Authentication is by API key passed as a query parameter on every request.

Use Cases

Patterns agents use APIXU Weather API API for, with concrete tasks.

★ Field Service Routing

Field service dispatchers fetch the current weather and tomorrow's forecast for each job site so that outdoor work can be reordered ahead of incoming storms. GET /current.json gives the live conditions and GET /forecast.json projects the next several days, both keyed by city name or coordinates so the dispatcher does not need a separate geocoding pass.

Call GET /current.json with q set to the job site postcode, return temperature and precipitation, and reorder jobs if the forecast shows storms within 24 hours.

Travel Itinerary Enrichment

Travel platforms enrich each itinerary with the forecast for the destination so travellers can pack appropriately and adjust plans. GET /forecast.json returns the multi-day outlook for the destination city while GET /search.json lets users disambiguate cities that share a name.

Call GET /search.json with the user's destination text, pick the matching location, then call GET /forecast.json for that location to return a 5-day outlook.

Historical Weather Analytics

Insurance and agriculture analysts query historical weather to model claim patterns and crop risk. GET /history.json returns observations for a chosen date and location, and the JSON shape can feed directly into a notebook or BI tool without scraping a web page.

Call GET /history.json with q set to the farm location and dt set to the storm date, returning rainfall and wind data for the claim record.

AI Agent Weather Lookup

An AI assistant answering 'what's the weather in Berlin?' or 'will it rain at my outdoor meeting tomorrow?' can use Jentic to call APIXU without managing the query-parameter API key directly. Jentic returns the matching operation by intent and injects the credential at call time, so the agent only has to choose between current, forecast, or history.

Search Jentic for 'get current weather', load the GET /current.json schema, and execute it with q set to the user's city to return temperature and conditions.

Key Endpoints

6 endpoints — jentic publishes the only available openapi specification for apixu weather api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/current.json

Get current weather for a location.

GET

/forecast.json

Get a multi-day weather forecast.

GET

/search.json

Search or autocomplete a location name.

GET

/history.json

Get historical weather observations for a date.

GET

/current.xml

Current weather in XML format for legacy consumers.

GET

/forecast.xml

Forecast in XML format for legacy consumers.

GET

/current.json

Get current weather for a location.

GET

/forecast.json

Get a multi-day weather forecast.

GET

/search.json

Search or autocomplete a location name.

GET

/history.json

Get historical weather observations for a date.

GET

/current.xml

Current weather in XML format for legacy consumers.

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

APIXU keys are passed as a query parameter, which is fragile in browser histories and logs. Jentic stores the key in the encrypted vault (MAXsystem) and appends it to outbound requests at call time, so the raw key never enters agent context or shared logs.

Intent-based discovery

Agents search Jentic by intent (e.g., 'get current weather' or 'historical weather lookup') and receive the matching APIXU operation with its query-parameter schema, so the agent can call the right endpoint without reading the APIXU docs.

Time to first call

Direct APIXU integration: 1-2 hours for auth and JSON parsing. Through Jentic: under 15 minutes — search, load schema, execute, and you keep the same path through the rebrand to Weatherstack.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

OpenWeatherMap API

Widely used weather data provider with a deeper free tier and broader endpoint surface.

Choose OpenWeatherMap when the workflow needs alerts, radar tiles, or air quality data not covered by APIXU.

Alternative

WeatherAPI.com

Modern weather API from the same lineage as APIXU/Weatherstack with marine and astronomy data.

Choose WeatherAPI.com when newer endpoints (marine, astronomy, sports) are needed alongside the classic forecast surface.

Complementary

Factorial HR API

Pair weather lookups with employee location data when calculating travel or attendance impact.

Use when an HR workflow needs to factor weather into attendance or travel decisions.

FAQs

Specific to using APIXU Weather API API through Jentic.

Why is there no official OpenAPI spec for APIXU Weather API?

APIXU does not publish an OpenAPI specification — its reference is rendered as HTML at apixu.com/doc/request.aspx and the service has since rebranded as Weatherstack. Jentic generates and maintains this spec so that AI agents and developers can call APIXU Weather API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the APIXU Weather API use?

APIXU uses an API key passed as the query parameter named key on every request. There is no header-based auth and no OAuth flow. Through Jentic the key is stored encrypted in the vault and appended at call time, so it never enters the agent's prompt or appears in logs.

Can I get weather alerts or radar imagery from this API?

No. The APIXU surface here exposes current conditions, forecast, search, and history only. Severe-weather alerts and radar tiles are not part of this API; for those use cases the Weatherstack successor or another vendor is required.

What are the rate limits for the APIXU API?

Rate limits are not declared in the OpenAPI spec — they depend on the APIXU/Weatherstack plan tier. The free and starter tiers historically capped monthly call volume rather than per-second throughput, so cache responses for repeated queries against the same city.

How do I get current weather through Jentic?

Run pip install jentic, then search Jentic for 'get current weather', load the schema for GET /current.json, and execute it with q set to the city name or 'lat,lon' coordinates. Jentic appends the API key from your stored credentials. Sign up at https://app.jentic.com/sign-up.

Can I get JSON and XML from the same API call?

No, but parallel endpoints exist. GET /current.json and GET /current.xml return the same data in their respective formats; GET /forecast.json and GET /forecast.xml do the same for forecasts. Pick the format-specific endpoint that matches your downstream consumer rather than negotiating content type.