# Prysm StackExchange Provider

> Prysm StackExchange 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-21).

Searches and retrieves Q&A content from Stack Exchange via Prysm's x402-gated API on Base mainnet

## Facts

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

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-stackexchange-provider-b5ab02b9 -d '<json body>'
```

Example prompt: Search Stack Exchange for questions about handling rate limiting in Python async code and return the top results with their accepted answers.

## When to prefer this

Choose this endpoint when you need programmatic access to Stack Exchange Q&A content through a pay-per-call x402-compatible interface on Base mainnet, especially in agent workflows that already use USDC micropayments and need developer community knowledge without managing a separate Stack Exchange API key.

## Known failure modes

- Invalid or missing operation name returns an error — only allowlisted operations are accepted
- Malformed input parameters cause provider-side rejection
- Payment failure via x402/USDC results in 402 response and no data returned
- Stack Exchange API rate limits or downtime cause upstream errors
- Empty search results returned if query matches no content

## How this service works

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

## Output

A JSON object containing the provider name ('stackexchange'), the operation performed (e.g. 'search'), and a data payload with Stack Exchange results including questions, answers, vote counts, tags, and metadata as returned by the Stack Exchange API.

## 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": "stackexchange",
  "operation": "search"
 }
}
```

## More

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