# Prysm Stability AI Image Generation

> Prysm Stability AI Image Generation is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.2/call, status unknown (last checked 2026-09-14).

Generates images from text prompts by proxying Stability AI operations over x402 micropayments on Base mainnet

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/stability
- Price: $0.2/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-stability-ai-image-generation-aa8e2ba5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oJY5isJlJieBWyxe1NDWQ

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-stability-ai-image-generation-aa8e2ba5 -d '<json body>'
```

Example prompt: Use Prysm's Stability AI provider to generate an image of a futuristic cityscape at sunset with neon lights reflecting on wet streets — run a text_to_image operation with that description as the input prompt.

## When to prefer this

Choose this endpoint when you need to generate images via Stability AI using crypto micropayments (USDC on Base mainnet via x402 protocol), particularly in agent workflows that already operate in the Web3/on-chain ecosystem. Prefer this over direct Stability AI API calls when you want pay-per-use billing without API key management, or when building agents that use x402-compatible payment flows.

## Known failure modes

- Invalid or unsupported operation name returns an error — only allowlisted operations are accepted
- Insufficient USDC balance or failed x402 payment results in a 402 Payment Required response
- Malformed input parameters for the chosen operation cause a validation error
- Stability AI upstream service outage or rate limiting propagates as a provider error
- Missing required prompt or input fields for text_to_image operation returns a bad request 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 generated image data under a 'data' key, the provider name ('stability'), and the operation performed ('text_to_image'). The data payload contains the Stability AI response which typically includes base64-encoded image content or image URLs.

## 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": "stability",
  "operation": "text_to_image"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-stability-ai-image-generation-aa8e2ba5/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)