# Prysm OpenAI Provider Proxy

> Prysm OpenAI Provider Proxy is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-10-22).

Proxies OpenAI API operations (e.g. chat completions) through Prysm's x402-gated endpoint on Base mainnet, billed per call in USDC.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/openai?utm_source=zero.xyz
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-openai-provider-proxy-5b8050ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Yo9TS5xtY1tOAEFaJuaZR

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-openai-provider-proxy-5b8050ab -d '<json body>'
```

Example prompt: Run a chat completion through Prysm's OpenAI provider — use the 'chat' operation and send the message 'Summarize the key benefits of on-chain payments in two sentences', paying with USDC on Base.

## When to prefer this

Choose this endpoint when your agent operates in a crypto-native or on-chain context and needs to call OpenAI without managing traditional API keys, preferring per-call USDC micropayments over subscription billing. Ideal for autonomous agents on Base mainnet that need to pay for AI inference programmatically using x402.

## Known failure modes

- Insufficient USDC balance or failed x402 payment results in 402 Payment Required
- Invalid or non-allowlisted operation string causes rejection
- Malformed input object for the selected OpenAI operation returns an error from upstream
- OpenAI API-side errors (rate limits, model unavailable) propagated back through the proxy
- Network or Vercel deployment outages causing 500 errors

## 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 the raw OpenAI API response, a 'provider' field set to 'openai', and an 'operation' field indicating which OpenAI operation was executed (e.g. 'chat').

## 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": "openai",
  "operation": "chat"
 }
}
```

## More

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