# Prysm WeatherAPI Provider

> Prysm WeatherAPI 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-10-20).

Fetches real-time or forecast weather data via WeatherAPI, accessible as an x402-paid agent-ready endpoint on Base mainnet

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/weatherapi?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-weatherapi-provider-15eada59
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r4Ra0cYXcmOmqllEyj8qS

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-weatherapi-provider-15eada59 -d '<json body>'
```

Example prompt: What is the current weather in Paris right now — temperature, conditions, humidity, and wind speed?

## When to prefer this

Choose this endpoint when you need real-time or forecast weather data in an agent workflow that already uses x402 micropayments on Base mainnet with USDC, and want a single aggregated gateway rather than managing a WeatherAPI key directly. It is especially useful for AI agents that need weather enrichment as part of a broader on-chain or automated pipeline.

## Known failure modes

- Invalid or unsupported operation name returns an error
- Missing or malformed location/input parameters may result in empty or error data
- Payment failure over x402 (insufficient USDC balance or network issue) prevents the call from executing
- WeatherAPI upstream downtime may cause the provider to return an error or empty data object
- Querying a location with no coverage returns empty or null weather fields

## How this service works

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

## Output

A JSON object with a 'data' field containing WeatherAPI response fields (e.g. current temperature, conditions, humidity, wind), a 'provider' field set to 'weatherapi', and an 'operation' field indicating which operation was called (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": "weatherapi",
  "operation": "current"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-weatherapi-provider-15eada59/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)