Reference & Lookup Data · Integration
Weather API
Add Weather API to your product for your customers, and give your AI agents governed access to it.
Weather API is a read surface and nothing more, so treat this integration as a feed rather than a system your product writes into: current conditions, forecasts by hour and by day, historical observations, and the location or coordinate lookup that resolves where a customer means. Nothing is created, updated or deleted, and no webhook exists to tell you a forecast moved, so your product polls on a schedule it picks and caches what comes back. The constraints are the ones any metered feed has: a call quota on the key, units and locale that must be chosen deliberately, and forecast horizons that vary by plan. fastn holds each customer's key and follows the provider's API changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Have each customer supply their own key, so the calls your feature makes are metered against them rather than you.
Read current conditions for a location your product already stores, and show them beside the record they belong to.
Pull an hourly or daily forecast to decide whether a scheduled job, delivery or site visit should go ahead.
Cache responses per location and refresh on your own timetable, because nothing here will notify you when a value moves.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks the forecast for a site before advising on a reschedule, with the location it queried logged.
An agent compares historical observations against a date a customer asks about, reading only what the key permits.
An agent states plainly that it can read weather and change nothing, because this connector exposes no writes.
Example prompt
What is the hourly forecast for this site tomorrow, and was it raining there on the day of the incident?
Set up Weather API in 4 steps
- 01Enable the Weather API connector from your fastn dashboard.
- 02Have each customer authorise their own Weather API account, so calls run under their credentials rather than a shared key.
- 03Decide which current conditions, forecasts, historical observations and locations your product needs, then decide your polling interval and cache policy, because this is a read-only feed with no webhooks.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Weather API integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Weather API integration without building it. Your customers connect their own Weather API account inside your product and work their lookups, results and reports there, with no per-customer code on your side.
- Handle the part that actually costs time: these are metered read sources, so an uncached lookup on every page view burns the customer's allowance. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Weather API update is not your on-call problem.
- One integration serves your product and your agents. The same governed Weather API connection powers in-product features and gives AI agents scoped, audited access, so you answer questions from an authoritative outside source without holding that data yourself without wiring it twice.
Used by these teams
Compare with
OneMap SingaporeOften used alongside
Tools the same teams tend to run next to Weather API, across other categories.
Salesforce
HubSpot
Notion
SnowflakeWeather API integration FAQ
How do I add a Weather API integration to my product?
Enable the Weather API connector in your fastn dashboard, then let each customer authenticate their own Weather API account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Weather API client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Weather API account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Weather API account and only ever sees their own lookups, results and reports. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Weather API integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent checks the forecast for a site before advising on a reschedule, with the location it queried logged.
Who maintains the Weather API integration?
fastn does. When Weather API changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose credentials does a Weather API lookup run under?
Each customer's own. Quota and cost land on the customer that caused them rather than on a shared key you have to meter and re-bill, and one heavy customer cannot exhaust another's allowance.
How should Weather API results be cached?
Per tenant, with a window that matches how fast the underlying data actually moves. Weather API is a read source rather than a system of record, so the same query returns the same answer until the source changes, and caching is the difference between a sustainable integration and one that exhausts a customer's allowance on a busy page.
What can I build with the Weather API integration?
A common starting point: have each customer supply their own key, so the calls your feature makes are metered against them rather than you. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Weather API integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Weather API does not change your per-connector cost. You can start free with 3 connected accounts.
Add Weather API to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.