# Prysm Deepgram Audio Transcription via x402

> Prysm Deepgram Audio Transcription via x402 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-09-14).

Transcribes audio to text by proxying Deepgram's speech recognition API, payable per-call in USDC over x402 on Base mainnet.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/deepgram
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-deepgram-audio-transcription-via-x402-b5f92af2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Fg5YVUj2mfOsUdg7tblnl

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-deepgram-audio-transcription-via-x402-b5f92af2 -d '<json body>'
```

Example prompt: Can you transcribe this audio file for me? Use the Deepgram transcription operation and send it the URL of my recording at https://example.com/my-interview.mp3.

## When to prefer this

Choose this endpoint when you need Deepgram-powered speech-to-text transcription and want to pay per-call in USDC without managing a Deepgram API key directly. Ideal for crypto-native agents or workflows operating on Base mainnet that need audio transcription as a composable, metered service via the x402 payment protocol.

## Known failure modes

- Payment failure if USDC balance is insufficient or x402 handshake fails
- Invalid or inaccessible audio URL results in transcription error
- Unsupported audio format or codec causes Deepgram to return an error
- Operation name not in allowlist returns a rejection
- Network timeout on large audio files
- Malformed input schema results in 400-level 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 ('deepgram'), the operation performed ('transcribe'), and a data object with the transcription result from Deepgram, including the recognized text and any metadata returned by Deepgram's 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": "deepgram",
  "operation": "transcribe"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-deepgram-audio-transcription-via-x402-b5f92af2/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)