# Prysm OpenWeatherMap Provider

> Prysm OpenWeatherMap Provider is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Fetches real-time and forecast weather data via OpenWeatherMap through Prysm's x402-enabled API gateway on Base mainnet

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/openweathermap
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-openweathermap-provider-d5b8ce87
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uNOGhKuc9-Yk0yMMGzqN0

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability prysm-openweathermap-provider-d5b8ce87 -d '<json body>'
```

Example prompt: What's the current weather in Tokyo — temperature, humidity, and wind conditions?

## When to prefer this

Choose this endpoint when you need weather data within an x402 micropayment workflow on Base mainnet using USDC, and you want a single unified gateway to OpenWeatherMap without managing your own API keys. Ideal for AI agents that already handle x402 payments and need real-time or forecast weather as part of a broader agentic pipeline.

## Known failure modes

- Invalid or unsupported operation name returns an error — must use an allowlisted operation string
- Missing or malformed 'input' object results in a bad request error
- Payment failure via x402/USDC on Base mainnet blocks the request
- Unsupported city name or invalid coordinates may return empty or error data from OpenWeatherMap
- Rate limiting or provider-side errors from OpenWeatherMap may propagate as API errors

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object with a 'data' field containing OpenWeatherMap response data (temperature, humidity, wind speed, weather description, etc.), a 'provider' field set to 'openweathermap', and an 'operation' field indicating which operation was performed (e.g. 'current').

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "openweathermap",
  "operation": "current"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-openweathermap-provider-d5b8ce87/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)