# Prysm Weatherstack Provider — Current Weather Data

> Prysm Weatherstack Provider — Current Weather Data 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 weather data via the Weatherstack API, proxied through Prysm's x402 micropayment gateway on Base mainnet

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/weatherstack
- 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-weatherstack-provider-current-weather-data-81962090
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2FTjE-EAUXjaF0BqbWLnD

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-weatherstack-provider-current-weather-data-81962090 -d '<json body>'
```

Example prompt: What's the current weather in Paris right now — temperature, wind speed, and conditions? Use the Weatherstack provider on Prysm and pay with USDC.

## When to prefer this

Choose this endpoint when you need real-time weather data in a pay-per-call model without committing to a Weatherstack subscription, or when your agent operates in a blockchain-native environment using x402 micropayments on Base mainnet with USDC. Ideal for low-frequency lookups, agent pipelines that need weather enrichment on demand, or any scenario where you want to avoid managing separate API keys for Weatherstack directly.

## Known failure modes

- Invalid or unrecognized location string returns an error or empty data
- Unsupported operation name causes rejection by the allowlist check
- Insufficient USDC balance or failed x402 payment results in 402 Payment Required
- Weatherstack API downtime causes upstream failure passed through as error
- Malformed input object missing required fields returns a validation error

## How this service works

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

## Output

Returns a JSON object containing the provider name ('weatherstack'), the operation performed ('current'), and a data object with real-time weather fields such as temperature, weather description, wind speed, humidity, and observation time for the queried location.

## 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": "weatherstack",
  "operation": "current"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-weatherstack-provider-current-weather-data-81962090/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)