# whatdoiwear.run

> Weather-based running outfit recommender. Give a location, get a complete running outfit — top, bottom, layers, and accessories — matched to current conditions (temperature, wind, rain, UV, humidity).

whatdoiwear.run is a free web app for humans and a paid, machine-readable API for AI agents.

## Agent API (x402)

Agents can buy outfit recommendations directly — no account, no API key. Payment uses the [x402 protocol](https://docs.x402.org): USDC on Base, $0.01 per call, scheme `exact`.

Always call the API on the `https://www.whatdoiwear.run` host. The apex domain (`whatdoiwear.run`) redirects to `www`, and x402 clients may not follow redirects — a redirected request can drop the payment and fail.

- Agent skill (free): `GET https://www.whatdoiwear.run/skill.md` — drop-in skill file covering the full flow: geocoding, payment, month mode, and how to present results to humans
- Discovery document (free): `GET https://www.whatdoiwear.run/api/v1` — full parameter and pricing schema as JSON. Includes the operator identity — the payTo wallet is operated by whatdoiwear.run
- Paid endpoint: `GET https://www.whatdoiwear.run/api/v1/outfit?lat=<lat>&lon=<lon>`
  - Required: `lat`, `lon` (decimal degrees — geocode on your side)
  - Optional: `gender` (`men` | `women`), `thermo` (`cold` | `neutral` | `hot`), `label` (human-readable location name, echoed back), `month` (integer 1-12)
  - Returns JSON: current weather snapshot, recommended outfit as items by slot (base_layer, top, midlayer, bottom, accessories), run advice, and any active weather alerts
  - With `month` set, the endpoint returns typical historical conditions for that month (basis `historical-typical`) plus two representative run-window outfits — a morning window near the typical low and a midday window near the typical high — instead of a live forecast; same price
  - Both response shapes carry a `basis` discriminator (`live` vs `historical-typical`) and a `summary` field: a compact 3-4 line human-readable string safe to display verbatim

Flow: call the endpoint, receive `402 Payment Required` with x402 payment requirements in the `payment-required` header, sign and retry with payment attached. Settlement only happens on successful responses — failed requests are never charged.

## Notes

- Weather comes from Apple WeatherKit with an Open-Meteo fallback; recommendations come from a deterministic rules engine (temperature bands, wind, precipitation, UV, humidity), not an LLM.
- Same weather on the same day returns the same outfit — responses are stable within a day and cached ~5 minutes server-side.