# MyRadar MyRadar is the weather data behind the MyRadar app. The forecast endpoint returns current conditions, minute by minute rain for the next hour, hourly forecasts for 48 or 168 hours, and daily forecasts for 7 days at any point, with severe weather alerts in the US, in the same shape as the former Dark Sky API. Road weather time series give road and surface temperature, road condition, precipitation, cloud cover, wind, and delay risk at a list of points, along a driving route for a future departure time, or over a historical window. Severe weather endpoints return warning, watch, and advisory polygons for a point or a bounding box and a multi year history of hail and high wind events. Layer endpoints expose the radar and model products as rendered images, map tiles, NetCDF, or point extracts. Every call is one request. ## API reference, endpoint lookup and prices **[MyRadar API catalog: endpoints, request parameters, prices and payment methods](https://agents.myradar.dev/zcj/hnp9jvh1efbw/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: Forecast, Radar and weather layers, Road weather time series, Severe weather. **Suggested next request:** GET [task guide](https://agents.myradar.dev/zcj/hnp9jvh1efbw/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.myradar.dev/zcj/hnp9jvh1efbw/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.myradar.dev/zcj/hnp9jvh1efbw/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.myradar.dev/zcj/hnp9jvh1efbw/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.myradar.dev/zcj/hnp9jvh1efbw/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.myradar.dev/zcj/hnp9jvh1efbw/SKILL.md) or [full direct workflow reference](https://agents.myradar.dev/zcj/hnp9jvh1efbw/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. ## References - [Buyer SKILL](https://agents.myradar.dev/zcj/hnp9jvh1efbw/SKILL.md): read as a skill when needed. - [Complete reference](https://agents.myradar.dev/zcj/hnp9jvh1efbw/llms-full.txt): advisor workflow and direct fallback. - [Catalog](https://agents.myradar.dev/zcj/hnp9jvh1efbw/manifest.json): services, plans and prices. - [OpenAPI](https://agents.myradar.dev/zcj/hnp9jvh1efbw/openapi.json): exact operation schemas. ## Guides - [Get a weather forecast by latitude and longitude with MyRadar's API](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/quickstart.md): One GET to MyRadar's forecast API returns current, hourly and daily weather for one point. Each call is one request drawn from a plan bought once. - [Check severe weather alerts for a point or area with MyRadar's API](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/severe-weather-alerts.md): MyRadar's severe weather API returns watch, warning and advisory polygons for a point or a box, plus hail and wind history. Each call is one request. - [Replace the Dark Sky API with MyRadar's forecast endpoint](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/replace-dark-sky-api.md): MyRadar's forecast endpoint takes Dark Sky-style requests and returns the same sections. Change the base URL, send a bearer header, buy a plan once. - [Add weather radar map tiles and layers with MyRadar's API](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/radar-map-tiles.md): MyRadar's layers API serves x/y/z radar tiles for Leaflet, Mapbox and Google Maps, box images and point values. Each tile is one request drawn from a plan. - [Forecast road weather along a driving route with MyRadar's API](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/road-weather-along-a-route.md): MyRadar's route endpoint returns road temperature, road condition and delay risk where the vehicle will be at each step. Each call is one request on a plan. - [MyRadar weather API pricing per request: Credits and monthly plans](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/pricing.md): MyRadar's weather API bills every service per request at your plan's rate. Compare prepaid Credits with Starter, Pro and Platinum by monthly volume. - [MyRadar API errors and recovery: bearer_required, plan_required](https://agents.myradar.dev/zcj/hnp9jvh1efbw/guides/errors.md): MyRadar's agent storefront answers credential, plan and purchase errors; MyRadar's API answers bad requests. Each code below has its recovery.