--- title: "How to use MyRadar with your AI agent | ZeroClick" url: https://zeroclick.ai/resources/how-to-use-myradar-with-your-ai-agent fetched_at: 2026-10-10T22:19:10.139Z --- # 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/4exgrb1aq5cq/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/4exgrb1aq5cq/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/4exgrb1aq5cq/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/4exgrb1aq5cq/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. Fill documented inputs and execute the returned requests with your own tools under existing user authorization. Check usage cost AND minimum cash required against the budget. No second advisor request is needed solely to switch from quoting to execution. For needs_input, supply only missing facts. Check configured credential storage and payment tools when needed; reuse existing identity and access, 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, with authorized email disclosure. 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/4exgrb1aq5cq/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/4exgrb1aq5cq/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/4exgrb1aq5cq/SKILL.md) or [full direct workflow reference](https://agents.zeroclick.ai/zcj/4exgrb1aq5cq/llms-full.txt). Confirm missing request details from seller documentation, stay within the existing catalog and user authorization, 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`. # How to use MyRadar with your AI agent *Published October 6, 2026 · 11 min read · [Resources](https://zeroclick.ai/resources)* MyRadar gives your AI agent weather data: forecasts at any point, road weather along a driving route, severe weather warnings, and radar layers and map tiles. Prices start at $0.02 per 100 requests. MyRadar sells through ZeroClick at the [MyRadar storefront](https://agents.myradar.dev). Your agent buys a plan before its first call: it registers a free agent credential, buys prepaid credit or a monthly plan over x402, MPP, or card, then calls the API with its bearer token. **Key facts before you start:** - A call without a credential returns `401`. A call without a covering plan returns `403 plan_required`. - Prepaid Credits cost $0.02 per 100 requests on all four services. $1 covers 5,000 calls. - Pay the plan's one priced 402 with x402 on Base USDC, MPP on Tempo USDC, or a card checkout from $0.50. - Send calls to `https://agents.myradar.dev` with MyRadar's own paths and queries. Forecasts come back in the shape of the former Dark Sky API. --- - [What MyRadar is](#what-myradar-is) - [What agents use MyRadar for](#what-agents-use-myradar-for) - [Prices](#prices) - [How to buy and call MyRadar from your agent](#how-to-buy-and-call-myradar-from-your-agent) - [Example requests](#example-requests) - [If your agent has no wallet](#if-your-agent-has-no-wallet) - [What to know](#what-to-know) - [Frequently asked questions](#frequently-asked-questions) --- ## What MyRadar is MyRadar is a weather app with more than 50 million downloads. People know it for high-definition radar, NOAA weather alerts, hurricane tracking, and aviation features. The weather data behind the app now sells to AI agents. Weather sits inside many agent jobs: deciding whether a crew goes out, when a van should leave, or whether a warning covers a customer's address. MyRadar answers each of those with one request. Responses are JSON, with CSV, images, map tiles, or NetCDF on the services that offer them. Its forecast endpoint takes the place of the old Dark Sky forecast request, so code written for Dark Sky can point at it. An agent storefront is the machine-readable version of a business. It is a URL where an agent reads what is for sale, the live prices, and the payment steps, then buys without filling in forms. MyRadar's storefront is a transparent proxy in front of its API. Your agent sends the method, path, query, and body it would send MyRadar, and the storefront handles identity, payment, and forwarding with no upstream API key. For how storefronts work, see [What is an agent storefront?](https://zeroclick.ai/resources/what-is-an-agent-storefront) --- ## What agents use MyRadar for | Job your agent is given | Service | Path | What comes back | |---|---|---|---| | Get the weather forecast for a location, hourly or 7-day | Forecast | `GET /v1/forecast/{point}` | `currently`, `minutely`, `hourly`, `daily`, `alerts`, `flags` | | Check whether rain starts in the next hour (US) | Forecast | `GET /v1/forecast/{point}` | `minutely` precipitation for 60 minutes | | Forecast road conditions along a driving route for a departure time | Road weather time series | `GET /v1/timeseries/route` | Road and weather fields aligned to where the vehicle will be | | Watch road temperature and delay risk at a list of sites | Road weather time series | `GET` or `POST /v1/timeseries/point` | 18 hours of `roadTemperature`, `roadCondition`, `delayRisk`, and more | | Pull past road weather for points | Road weather time series | `GET /v1/timeseries/hist/{begin_time}/{end_time}` | A continuous time series per point | | Check active watches, warnings, and advisories at an address | Severe weather | `GET /v1/severe/wwa/{lat}/{lon}` | `count`, `total`, `limit`, `offset`, `results` | | List warnings across a region | Severe weather | `GET /v1/severe/warnings/{ul_lat}/{ul_lon}/{lr_lat}/{lr_lon}` | Warning polygons, paged | | Look up hail and high wind history at a property | Severe weather | `GET /v1/severe/history?latlon=` | Several years of recorded events | | Add radar map tiles to Leaflet, Mapbox, or Google Maps | Radar and weather layers | `GET /v1/layers/tile/{cycle_time}/{image_time}/{zoom}/{tile_x}/{tile_y}` | One colored PNG tile | | Render radar over a box as a PNG, GIF, NetCDF, CSV, or JSON | Radar and weather layers | `GET /v1/layers/layer/{layer}/{valid_time}/...` | The rendered layer | Start a layers job with `GET /v1/layers/listlayers`, which returns every layer name. The route endpoint takes `origin`, `destination`, and `depart_time` (YYYYMMDD.HHMM). An origin or destination can be a `lat,lon` pair or an address. Each service has its own API reference, such as the [forecast API reference](https://agents.myradar.dev/services/forecast/openapi.json). --- ## Prices Every call is one request. Each plan charges the same rate for all four services. | Plan | How it bills | Price | Included | Overage rate | |---|---|---|---|---| | Credits | Prepaid credit | From $0.02 on a wallet, $0.50 by card | None | $0.02 per 100 requests | | Starter | Monthly | $199 / month | $199 credit, 1,000,000 requests | $0.199 per 1,000 requests beyond | | Pro | Monthly | $399 / month | $399 credit, 3,000,000 requests | $0.133 per 1,000 requests beyond | | Platinum | Monthly | $549 / month | $550 credit, 5,000,000 requests | $0.110 per 1,000 requests beyond | On Credits, one request costs $0.0002. Checking one location's forecast every 15 minutes for 30 days is 2,880 requests, about $0.58. Checking warnings at 50 delivery stops, one request each, costs one cent. The $0.50 card minimum buys 2,500 requests. At volume a monthly plan costs less: 3,000,000 requests a month cost $600 on Credits, while Pro's $399 a month includes 3,000,000 requests. Prices come from the live [catalog](https://agents.myradar.dev/manifest.json). Read it at call time rather than caching it. The purchase 402 states the exact amount before your agent pays. --- ## How to buy and call MyRadar from your agent 1. Open the storefront's [agent guide](https://agents.myradar.dev/llms.txt), which links the catalog, the payment guide, the identity guide, and the API reference. 2. Match the task to a service and path from the table above, or ask the read-only task guide at `https://agents.myradar.dev/zeroclick/agent/guide?goal=URL_ENCODED_TASK`. The task guide never buys anything. 3. Look for an existing ZeroClick agent credential in your keychain first, because one credential works at every ZeroClick storefront. 4. If there is none, register one with a single free call to `/agent/identity` and store the result. 5. Exchange the stored assertion for a short-lived access token at `/oauth2/token`. 6. Pick a plan and read its `id` and `purchase.url` from the catalog. The Credits plan is the entry with the slug `credits`. 7. Send the purchase with your bearer token, plus an amount for Credits. The storefront answers with one priced 402. 8. Check `payment.amountUsd` against your budget, then settle the challenge on x402 or MPP and resend the identical purchase with the proof. 9. If you are unsure the purchase went through, list your active plans with `GET /agent/entitlements` before paying again. 10. To keep the plan beyond an anonymous credential's few days, have your human claim the credential to their email. 11. Call the weather endpoint with `Authorization: Bearer ` and read the `zc-billing` header for your remaining credit. 12. Top up with `POST /extend` when the balance runs low or a call returns `usage_exhausted`. --- ## Example requests Register an anonymous credential once. It needs no email and no human step. The response carries `identity.assertion`, which you store, and a `claim.token` for claiming it later: ```http POST https://agents.myradar.dev/agent/identity Content-Type: application/json {"type": "anonymous"} ``` Exchange the stored assertion for an access token. Tokens last minutes, so repeat this step whenever one expires: ```http POST https://agents.myradar.dev/oauth2/token Content-Type: application/x-www-form-urlencoded grant_type=urn:ietf:params:oauth:grant-type:jwt-bearer&assertion= ``` Buy Credits with the bearer token. Take the plan id from the catalog. This $25 purchase covers 125,000 requests: ```http POST https://agents.myradar.dev/plans/{planId}/purchase Authorization: Bearer Content-Type: application/json {"amountUsd": "25.000000"} ``` The reply is a 402. Its body carries `payment.amountUsd`, the `plan`, and a `protocols` block with a challenge for each rail. The signable challenges also arrive as headers, so a standard x402 or MPP client can settle them without reading the body: ```http HTTP/1.1 402 Payment Required payment-required: www-authenticate: ``` Sign the challenge and resend the same purchase with the proof. This is the x402 retry. On MPP, send `Authorization: Payment ` instead and move your token to `ZC-Agent-Authorization: Bearer `: ```http POST https://agents.myradar.dev/plans/{planId}/purchase Authorization: Bearer x-payment: Content-Type: application/json {"amountUsd": "25.000000"} ``` With the plan active, call the forecast. The point is latitude and longitude with no space: ```http GET https://agents.myradar.dev/v1/forecast/45.51,-122.68?units=us&exclude=minutely,alerts Authorization: Bearer ``` The response follows the forecast schema. Shown here trimmed, with the API reference's example values and placeholders for the long sections: ```json { "latitude": 45.51, "longitude": -122.68, "timezone": "America/Los_Angeles", "currently": {"time": 1590159600, "summary": "Showers.", "temperature": 49, "precipProbability": 0.49}, "hourly": {"summary": "", "data": [""]}, "daily": {"summary": "", "data": [""]}, "flags": {"units": ""} } ``` A `zc-billing` header comes with each plan-funded response. It reports `fundingSource`, `chargedUsd`, and `remainingCreditUsd`. --- ## If your agent has no wallet - **Create a wallet.** An autonomous agent can create one at no cost and without signing up, then follow the steps above. - **Buy by card.** Send the purchase with your bearer token and `checkout: true` to get an unpaid hosted checkout URL. Creating it needs no funds or card. A browser agent can pay an eligible checkout with Link Pay Tokens, and the page takes Link directly. The [card checkout instructions](https://agents.myradar.dev/payment/card.md) cover the details. Poll the returned `statusUrl` until payment completes. Credits by card start at $0.50. - **Use a shared payment token.** Card-eligible 402s carry a `method="stripe"` challenge, which your agent answers with the token in `Authorization` and its access token in `ZC-Agent-Authorization`. - **Hand off to a human.** Send the checkout URL to your human privately. To share any other MyRadar page, use `https://agents.myradar.dev/outclick?url={URL-encoded seller page}` so the referral is recorded. --- ## What to know **No per-call payment.** MyRadar sells only on plans. The 402 your agent settles is the plan purchase, and every call after it draws on the plan with no new payment. **Coverage limits.** Minute-by-minute rain and forecast alerts are US only. Hourly forecasts run 48 hours by default, or 168 hours with `extend=hourly`. Summaries come in English only. **Credentials.** An anonymous credential that nobody claims lapses after a few days, taking any plan bought with it. Claiming it to your human's verified email keeps purchases recoverable. Monthly plans request that verified email and share it with MyRadar so it can tie the purchase to their account. Credits does not. **What is charged, and when.** Paying a 402 completes the purchase under ZeroClick's [buyer terms of service](https://www.zeroclick.ai/legal/buyer-terms-of-service). A payment is not proof of delivery. If a purchase looks unfinished, check your active plans with `GET /agent/entitlements` before paying again. A delivered response with no `zc-billing` header billed nothing. Once a call reaches MyRadar, your agent gets MyRadar's own status code and body. **Errors worth handling.** The [error reference](https://agents.myradar.dev/errors.md) covers more. | Error | What to do | |---|---| | `bearer_required` (401) | Register a credential and retry with the bearer token. | | `plan_required` (403) | Buy one of the plans listed in the body, then retry. | | `invalid_token` (401) | On `token_expired`, exchange the stored assertion for a fresh token. | | `usage_exhausted` | Top up with `POST /extend` or buy again. | | `amount_below_card_minimum` | Raise the card amount to $0.50, or pay on a wallet rail. | | `payment_provider_unavailable` | This is the only payment error to retry unchanged, with backoff. | --- ## Frequently asked questions ### Does MyRadar need an API key for AI agents? No upstream API key is needed. Your agent needs a free ZeroClick agent credential and a plan, then calls with `Authorization: Bearer `. ### Is MyRadar a Dark Sky API alternative? Yes. MyRadar's forecast endpoint returns current, minutely, hourly, daily, and alert sections laid out like the former Dark Sky API's responses, so code written for Dark Sky's forecast can switch to it through the storefront once your agent has a plan. ### How much does the MyRadar API cost for an agent? Prepaid Credits cost $0.02 per 100 requests on every service. Monthly plans run $199, $399, and $549, with 1,000,000, 3,000,000, and 5,000,000 requests included. ### Can my agent pay MyRadar with x402? Yes. Your agent settles the plan purchase's 402 over x402 on Base USDC, using the challenge in the `payment-required` header and sending the signed payload in `x-payment`. ### How do I get road weather along a driving route? Call `GET /v1/timeseries/route` with `origin`, `destination`, and `depart_time`. The forecast for each step of the trip matches where the vehicle should be at that time. ### Do I have to use an AI agent to use MyRadar? No. People can download the MyRadar app, and developers can buy MyRadar's API directly from its [Developer API Portal](https://myradar.com/developer_portal), on monthly plans from $199 for up to 1,000,000 calls. An agent that registers and pays for itself uses the storefront instead. --- ## More in Get more done with your agent - [How to use Dappier with your AI agent](https://zeroclick.ai/resources/how-to-use-dappier-with-your-ai-agent) — Dappier sells live web search and licensed publisher news to AI agents through ZeroClick, on prepaid credit from one cent with no signup or API key. - [How to use ZeroGPU with your AI agent](https://zeroclick.ai/resources/how-to-use-zerogpu-with-your-ai-agent) — ZeroGPU sells small and open-weight models to AI agents through ZeroClick, on prepaid credit from $0.02 per million tokens, paid over x402, MPP, or card. - [How to use DeepAI with your AI agent](https://zeroclick.ai/resources/how-to-use-deepai-with-your-ai-agent) — DeepAI sells image and video tools to AI agents through ZeroClick, from $0.01 per image, paid per request over x402 or MPP with no signup or API key. [All resources](https://zeroclick.ai/resources#get-more-done)