Skip to content
Docs navigation

FAQ

Answers about keys, limits, pricing, and billing.

Smarter Weather covers the 50 US states and DC only. Coverage details

Ask us

One question at a time, answered from our developer docs. We will say so if we do not know.

Getting started

Can I try before paying?

Yes. The Free plan needs no card, and your first key is a live sw_live_ key: 60 requests/minute and 1,000 requests/day, never billed. For CI, create a sw_test_ key: same endpoints and the same per-key limits as your plan, never billed.

Can I call the API from a browser?

Call Smarter Weather from your own backend, serving only your own app, behind your app's own sign-in. Browsers on other origins are blocked by design, and a key in page code can be copied. Keep the key server-side, as Acceptable Use §4 asks. Sharing your key with third parties, or operating a proxy, gateway or bring-your-own-key service that lets third parties use your credentials, is prohibited by Acceptable Use §1. Build a weather app has a Node and a Python backend that check an app token first.

What attribution do I show?

Display the attribution.notice string from each response, as returned, wherever you show its data, and link Acknowledgements next to it. Read it from the response rather than copying it, so a wording change reaches your users without a release.

Keys and requests

What counts as a request?

Rate limits and daily caps count requests: every call is one request. Billing counts credits. REST calls are 1 credit; /v1/series/batch is 1 credit per location, /v1/weather/batch is 1 per call, and /v1/catalog is free. MCP tools cost 0 to 4 credits per call by tool weight (see credits per call). REST and MCP draw on one credit allowance.

How do rate limits work?

Each key has a per-minute limit and a daily cap set by its plan; the rate limits table lists them. Both count requests, not credits, and daily caps reset at 00:00 UTC. Every keyed response carries RateLimit-* headers (per the IETF rate-limit-headers draft, no X- prefix) so your client can slow down before it hits a limit. On a 429, wait for Retry-After.

How long can I cache a response?

For the max-age in its Cache-Control header, on your backend. Read the header on every response: an answer that says no-store must not be cached at all. Errors carry no Cache-Control: keep an outside-coverage 404, wait out a 429's Retry-After, and cache no other error. A cached answer never reaches the API, so it costs no request and no credits.

Pricing and billing

How does overage billing work?

Each paid plan includes a monthly allowance of credits. Anything beyond it bills as metered overage at the plan's posted per-1,000-credit rate, so the allowance never stops your calls; the daily cap does (429 until 00:00 UTC). Only successful calls are billed: a 2xx REST response, or an MCP tool result that is not an error. Errors (4xx, 5xx, MCP tool errors) are never billed, and x402 never settles them. Every successful call counts, including your agent's retries and loops. Every request your key makes counts toward its rate limits and daily cap, whatever its status, except one rejected with a 429. Overage is added to the next monthly invoice; there's no surprise mid-cycle charge.

Can I change plans anytime?

Manage your subscription from the Billing page of your developer dashboard, which opens Stripe's billing portal. The billing portal shows when a change takes effect and any prorated charge or credit before you confirm it. Canceling takes effect at the end of the billing period.

Do you offer enterprise pricing?

Yes. Scale starts from $1,000/month on an annual commitment, billed by invoice. Enterprise is negotiated above Scale: a contractual SLA, SSO and custom limits. Reach us through the contact page or at developers@smarterweather.com.

Agents and the Weather MCP

Is there a trial key for agents?

Yes. A trial key allows 300 requests over 72 hours, 10 a minute (burst 5); /v1/catalog requests don't count toward the 300. It works on routes under /v1/weather, /v1/geocode, and /v1/alerts. A human can claim it within 7 days from the printed claim link to keep the same key on the Free plan (60 requests a minute, 1,000 a day, no card). The Quickstart shows how an agent gets one.

Does the Weather MCP use the same API key?

Yes. New keys carry both the api and the mcp scope. Each tool call is one request toward your rate limits and costs 0 to 4 credits from the allowance REST uses. See Set up the Weather MCP.

Can an agent pay per call without a key?

On the Weather MCP, yes: an agent with a wallet can pay per tool call with x402, with no account. The REST API always needs a key. See how x402 works.