canonical: https://jentic.com/apis/interzoid.com/interzoid-get-weather-by-zip-code-api

# Interzoid Get Weather By Zip Code API

The Interzoid Get Weather By Zip Code API returns current weather conditions for any US zip code, including temperature in Fahrenheit and Celsius, wind speed and direction, relative humidity, and visibility in miles. It is intended for workflows that already hold a US zip code and need to enrich it with conditions at request time, such as field-service routing, delivery dispatch, or a customer-facing status view. The single GET endpoint also returns the resolved City and State so the response is self-describing.

## For AI agents

Look up current temperature, wind, humidity, and visibility for a US zip code so an agent can enrich a delivery, dispatch, or routing decision with live weather conditions.

## Scope

Does not provide forecasts, historical data, or non-US coverage - use for current US weather conditions by zip code only.

## Capabilities

- Retrieve current temperature in Fahrenheit and Celsius for a US zip code on a delivery row
- Check wind speed and direction at a destination zip code before dispatching a field crew
- Read current visibility in miles for a zip code to gate outdoor work
- Resolve a zip code to its City and State alongside the live weather payload
- Capture humidity and Weather summary text for a zip code into a routing record

## Use cases

### Pre-Dispatch Weather Check

Check current conditions at a delivery zip code before dispatching a driver, so routes can be deferred or rerouted when wind, humidity, or visibility breach configured thresholds. The Get Weather By Zip Code API returns TempF, WindMPH, WindDir, RelativeHumidity, and VisibilityMiles in a single GET call. Field-service platforms commonly call this in the dispatch hook.

Example prompt: Call /getweatherzipcode with zip=90210 and abort the dispatch step if VisibilityMiles is below 1 or WindMPH exceeds 30.

### Delivery ETA Adjustment

Adjust a delivery ETA by reading current conditions for the destination zip and applying a margin when temperatures are extreme or visibility is poor. The API's TempF, Weather, and VisibilityMiles fields give an agent enough signal to add buffer minutes without integrating a full meteorological feed. The single endpoint keeps latency predictable.

Example prompt: Call /getweatherzipcode with the destination zip, read TempF and VisibilityMiles, and add 20 minutes of buffer to the displayed ETA when either threshold is breached.

### Customer Status Page Conditions

Display current conditions on a customer-facing tracking page by zip code, so a recipient sees the weather at the delivery address while the package is in transit. The API returns Weather, TempF, and RelativeHumidity strings ready for direct display, and resolves City and State so the panel can confirm the address. No tz handling is required.

Example prompt: Call /getweatherzipcode with the customer's zip and render the returned Weather, TempF, and RelativeHumidity values on the tracking page.

### Agent-Driven Field Routing via Jentic

An AI dispatch agent uses Jentic to call the Interzoid Get Weather By Zip Code API as part of its routing decision. The agent reads TempF, WindMPH, and VisibilityMiles, applies thresholds, and either confirms the route or queues the job for the next day. Through Jentic the Interzoid license key is held in the credential vault and never enters the agent context.

Example prompt: Use Jentic to search for 'get current weather for a US zip code', load /getweatherzipcode, and execute it for each open route to gate dispatch on wind and visibility thresholds.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/getweatherzipcode` | Return current weather conditions for a US zip code |

## Key resources

- **Weather by Zip Code** — GET endpoint that accepts a US zip code and returns City, State, Weather, TempF, TempC, WindMPH, WindDir, RelativeHumidity, and VisibilityMiles.

## Why Jentic

- **Setup:** Wiring the Interzoid Get Weather By Zip Code API by hand means obtaining a license key, appending it as a license query parameter on each call to /getweatherzipcode, and handling the request plumbing yourself. Through Jentic you install once, import this API from the API Directory, store the license key once, and your agent calls it.
- **Permission scoping:** This API exposes a single read-only GET /getweatherzipcode operation that takes a US zip code in the query, with no resource id in the URL path, so scoping is at the operation level: you limit the agent to the current-conditions lookup it needs. It only reads weather and writes nothing, so there is no destructive operation to include.
- **Credential handling:** Your Interzoid license key is stored once, encrypted, by your own Jentic One instance and injected as the license parameter at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get current weather for a US zip code', and Jentic returns the Get Weather By Zip Code operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Interzoid Get Weather City API** — Same conditions payload, accessed by US city and state instead of zip code.
- **OpenWeatherMap** — Global current weather, forecasts, and historical data with zip-code, city, and lat/lon lookup.
- **Interzoid Zip Code Detailed Info API** — Returns city, state, latitude, longitude, and demographic data for a zip code, often used alongside the weather lookup.

## FAQ

### What authentication does the Interzoid Get Weather By Zip Code API use?

The API uses an Interzoid license key passed as the required `license` query parameter on /getweatherzipcode. Through Jentic the license key is held in the credential vault and injected at execution time, so the raw key never enters the agent context.

### Can I get a forecast or only current conditions with this API?

Only current conditions. /getweatherzipcode returns TempF, TempC, Weather, WindMPH, WindDir, RelativeHumidity, and VisibilityMiles at the moment of the call. There is no forecast endpoint on this spec.

### What are the rate limits for the Interzoid Get Weather By Zip Code API?

The OpenAPI spec does not declare a numeric rate limit. Each successful call decrements a credit balance returned in the Credits response field, and a 402 status is returned when credits are exhausted. Refer to interzoid.com for current per-license-tier throughput.

### How do I look up weather for a zip code through Jentic?

Install the SDK with `pip install jentic`, search for 'get current weather for a US zip code', load /getweatherzipcode, and execute it with zip set to a five-digit US zip code. The TempF, WindMPH, and VisibilityMiles fields are ready for direct use.

### Does this API cover non-US locations?

No. The endpoint accepts US zip codes only and resolves them against US weather stations. For city-level US conditions, use the Interzoid Get Weather City API instead.

### What happens for an invalid zip code?

The API returns a 404 status with no weather payload when the zip cannot be matched. Agents should treat this as a soft failure and skip the weather-enrichment step rather than retrying the same zip.

### Can I limit what my agent is allowed to do with the Interzoid Get Weather By Zip Code API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and this API exposes a single read-only GET /getweatherzipcode operation, so you scope the agent to just the current-conditions lookup it needs. There is no resource id in the URL path and nothing is written, so there is no destructive operation to grant. You control whether the agent can call this weather lookup at all and can withhold the Interzoid license key from any agent that should not reach it.