---
title: "MyRadar × ZeroClick: weather data any AI agent can buy | ZeroClick Blog"
url: https://zeroclick.ai/blog/myradar-weather-data-any-ai-agent-can-buy
fetched_at: 2026-10-26T13:40:45.022Z
---

# ZeroClick API catalog and pricing

## API reference, endpoint lookup and prices

**[ZeroClick API catalog: endpoints, request parameters, prices and payment methods](https://agents.zeroclick.ai/zcj/31tngzbshknn/zeroclick/agent/guide).** Tell the seller advisor what you want to accomplish. It returns the matching operation contract, known prices, authentication prerequisites and concrete next steps. It is read-only: no login, wallet, card or purchase approval is needed to look up an API. It never executes a sale.

Available API services: Agent readiness report, Demo booking.

**Suggested next request:** GET [task guide](https://agents.zeroclick.ai/zcj/31tngzbshknn/zeroclick/agent/guide?goal=URL_ENCODED_TASK). Use this URL directly with your web fetch tool; no preliminary document fetch is required. Include known inputs and desired output in the goal. Optional: quantity=API_CALL_COUNT, budgetUsd=TOTAL_USD, requirements=REQUIREMENTS, payment=x402|mpp|card, auth, identity, assertion and access state. Omit unknowns. Do not equate output items with API calls or guess a call count.

For private task details or known request arguments, POST https://agents.zeroclick.ai/zcj/31tngzbshknn/zeroclick/agent/guide with Content-Type: application/json. Example: {"intent":"quote","goal":"YOUR_TASK","purchase":{"budgetUsd":"5.00"}}. Replace the task and budget with known facts; budgetUsd is a string. Include known buyerState, paymentCapabilities and arguments. For execution planning use intent=execute and the authorized constraints. Exact fields: [request schema](https://agents.zeroclick.ai/zcj/31tngzbshknn/zeroclick/agent/schema). GET and POST are alternatives, not mandatory stages.

The advisor describes a recommended happy path, not the only allowed path. You may use the API reference, buyer SKILL and your own tools directly, including for catalog operations with failed probes. Missing guidance or an unverified probe is not a policy refusal. The returned requests are documented API calls; fill in the documented inputs. Check usage cost AND minimum cash required against the budget. For needs_input, supply only missing facts. Keep secrets local, and never put credentials or private payloads in URLs. Unknown does not mean absent.

For a human's credit or plan purchase, reuse an existing ZeroClick credential first. Otherwise use their signed-in Link account for identity as well as payment, sharing their email only if they agree. An empty or expired Link credential list means request a credential, not fall back to anonymous. Follow [Link identity setup](https://agents.zeroclick.ai/zcj/31tngzbshknn/auth.md#link-identity-preview) through issuance, presentation, registration and token exchange. Anonymous auth remains available for agents acting on their own behalf with no human in the loop.

Open the checkout URL in a browser: eligible Stripe pages support Link Pay Tokens (LPT) through WebMCP or the documented DOM flow. Follow this storefront's /payment/card.md to verify the same-frame token input and merchant binding before requesting an LPT. Token submission requires payment authorization. If unavailable, privately send the checkout URL to your human to pay.

When the selected route uses hosted checkout, follow [card checkout instructions](https://agents.zeroclick.ai/zcj/31tngzbshknn/payment/card.md) before requesting a token. LPT goes only to Stripe, never to the advisor or ZeroClick API. Poll the returned statusUrl before using credit or retrying delivery.

Verify delivery; a payment or HTTP 202 is not completion. For an unexpected result, POST the original input and continuation (version, stepId, outcome and sanitized error/accessId/paymentId). Reconcile uncertain payments or writes before retrying. Use raw HTTP for exact schemas and authenticated execution; do not reconstruct fields omitted by a summarizing web tool.

The human subscription prices on the requested page describe a separate channel. Use the API quote for per-unit pricing, funding minimums and commercial terms; tier names do not prove quality or licensing.

For an alternative documented path, use the [buyer SKILL](https://agents.zeroclick.ai/zcj/31tngzbshknn/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/31tngzbshknn/llms-full.txt). Confirm missing request details from seller documentation, stay within the existing catalog and what your user asked for, and respect actual access and payment requirements.
Terms: by completing a purchase through this endpoint, whether directly or through an AI agent acting on your behalf, you agree to be bound by the platform's buyer terms of service (https://www.zeroclick.ai/legal/buyer-terms-of-service). If the purchase is made by an agent, you represent and warrant that the agent is acting with your authorization, and you agree that the agent's actions, including its acceptance of these terms, are attributed to you and bind you as if you had taken them yourself. Paying a 402 challenge completes the purchase and constitutes your affirmative acceptance of the terms linked above. The link travels in every payment challenge and receipt as `terms`.

# MyRadar × ZeroClick: Weather Data Any AI Agent Can Buy

[Blog](https://zeroclick.ai/blog) · October 13, 2026 · Partnership · 7 min read
By [Daniel Baum](https://x.com/realdanbaum), VP GTM

Weather is the data an AI agent needs most often and owns least. Should the delivery go out this morning? Will the crew get the roof closed before the storm? Which of fifty job sites sits under a warning right now? Has that address taken hail in the last few years? Every one of those questions comes down to a forecast, a radar frame, or a warning polygon. Until now an agent could only get them the way its developer did: sign up for a weather API, pick a monthly tier, and keep a key alive. [MyRadar](https://myradar.com) has been answering those questions for people since 2008, through the weather app behind more than 50 million downloads and the developer API that runs underneath it.

Today we are announcing a partnership that opens that data to any AI agent on the internet. MyRadar's weather API is live as an agent storefront at [agents.myradar.dev](https://agents.myradar.dev/llms.txt), on MyRadar's own domain. An agent can buy a hundred forecast calls for two cents over open payment rails, or a monthly plan at the same prices MyRadar charges developers, and start calling.

## The Weather Layer

MyRadar is the weather app from Acme AtronOmatic, an Orlando, Florida company founded by Andy Green. It started in 2008 as a way to answer one question, whether it was about to rain, with an animated radar map. It has grown into one of the most-used weather apps on any platform, with more than 50 million downloads. Behind the app is a weather company: a forecast engine, a road-weather product called RouteCast that gives dispatchers the conditions along a route for the time a truck will actually be there, a severe-weather feed, and, since 2019, small satellites of its own. That work has drawn contracts from the US Navy and Air Force. The same data is sold to developers through the MyRadar API, from a forecast endpoint built as a drop-in replacement for the former Dark Sky forecast request to radar tiles for any map.

An agent could already read all of that. MyRadar documents its API publicly, and its forecast endpoint speaks a shape that most developers, and the models trained on their code, already know. What an agent could not do on its own was pay. The API is sold on monthly tiers, from Starter at $199 for a million calls, and every one of them needed an account, a card, and a key that a person set up.

## What the Partnership Does

MyRadar's weather API is live today as an agent storefront at [agents.myradar.dev](https://agents.myradar.dev/llms.txt), on MyRadar's own domain. It takes the same requests a developer sends the MyRadar API directly, with every parameter from its docs. Four services cover fifteen endpoints.

- **Forecast** returns current conditions, minute-by-minute rain for the next hour, hourly forecasts for the next 48 or 168 hours, daily forecasts for seven days, and active severe weather alerts for any point, in the same shape as the former Dark Sky API.
- **Road weather time series** (the data behind RouteCast) gives road and surface temperature, road condition, precipitation, wind, and delay risk for a list of points, along a driving route for a future departure time with the forecast aligned to where the vehicle will be, or over a historical window.
- **Severe weather** returns warning, watch, and advisory polygons for a point or a bounding box, plus a multi-year history of hail and high-wind events at a location.
- **Radar and weather layers** expose the radar and model products as rendered images, map tiles for Google Maps, Mapbox, or Leaflet, NetCDF or CSV downloads, and point extracts.

Every call is one request.

An agent discovers the storefront, reads the machine-readable catalog and the live pricing manifest, registers a free credential, buys credits or a monthly plan over x402, MPP, or card, and calls against its balance. It does not have to work out the catalog by itself: the storefront's seller agent takes a goal in plain language, road conditions from Reno to Salt Lake City for a 5am departure, say, and returns the endpoint to call, the request to send, what it will cost, and the next step, before anything is bought. An agent that shows up without a wallet is not stuck: the storefront's guide walks it through creating one at no cost.

ZeroClick handles the commerce around every request: agent identity, payment on open rails, metering, and transaction-level analytics on every sale, with revenue settling directly to MyRadar's Stripe account. Discovery comes built in: the storefront is already listed on [zero.xyz](https://zero.xyz/), x402scan, and mppscan, and MyRadar already points agent traffic at it straight from [myradar.com](https://myradar.com), from its llms.txt to its homepage and developer portal. The first purchases went through end to end the day the storefront went live.

## Two Cents for a Hundred Forecasts

MyRadar prices its API by the request, and the storefront keeps that model exactly as it is.

**Pay-as-you-go credits:** every call to every service costs $0.02 per 100 requests, a fiftieth of a cent a call, with no verified email, no tier to choose, and a minimum purchase of two cents. That is the smallest first purchase of any storefront in this series.

**Monthly plans** (same prices as the developer portal):

| Plan | Price | Requests per month |
|---|---|---|
| Starter | $199 | 1,000,000 |
| Pro | $399 | 3,000,000 |
| Platinum | $549 | 5,000,000 |

Run the numbers on a real errand. An agent that checks the forecast at twenty delivery stops every morning makes 20 calls a day, 600 a month, for twelve cents. One that watches severe-weather warnings over fifty job sites every fifteen minutes makes 4,800 calls a day, about $29 a month on credits. The Starter plan only starts to pay for itself around a million calls a month, exactly where its quota sits. A route forecast for a cross-country drive, with conditions aligned to where the truck will be at every step, is one request.

That fits the way an agent works. It does not know in advance how many calls a job will take, and it does not have to: it can buy two cents of credit, run the task, and buy more only if the task keeps going. There is nothing to cancel. A job that turns out to need a million calls a month can move to a plan at the price a developer would pay. Claim your agent's credential with your email to keep what it buys.

## Shared Philosophy

MyRadar built its business on the question people ask before they do almost anything outdoors: what is the weather about to do? Agents are starting to act on the answer, dispatching, scheduling, routing, and quoting, and the data they act on has to be something they can find, read, and pay for without waiting on a person. That is the conviction ZeroClick is built on: helping businesses come online for a new kind of customer, AI agents, and turning them into buyers with identity, payment, pricing, and receipts all handled by ZeroClick. MyRadar kept its product, its prices, and its tiers exactly as they were. What changed is who can pay: any AI agent, on MyRadar's own domain, with or without a human in the loop.

## Get Started

- **Agent needing weather data:** point it at [agents.myradar.dev](https://agents.myradar.dev/llms.txt)
- **Developer wanting a key and subscription:** start at the [MyRadar developer portal](https://myradar.com/developer_portal)
- **Seller wanting to reach AI agents:** get a demo at [zeroclick.ai](https://zeroclick.ai/getlisted?utm_source=blog) or read the docs at [docs.zeroclick.ai](https://docs.zeroclick.ai)