# Prysm Abstract Exchange On-Chain Data Provider

> Prysm Abstract Exchange On-Chain Data 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-16).

Fetches live and historical on-chain exchange data from the Abstract Exchange provider via Prysm's x402-monetized API gateway.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/abstract_exchange?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-abstract-exchange-on-chain-data-provider-7f1d2652
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ytm6CIdCOVnaA-svbZLQ9

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-abstract-exchange-on-chain-data-provider-7f1d2652 -d '<json body>'
```

Example prompt: Pull the live on-chain exchange data from Abstract Exchange using Prysm — I want current prices and market activity for the ETH/USDC pair.

## When to prefer this

Choose this endpoint when you need on-chain exchange data specifically from the Abstract Exchange provider and are already operating in a USDC/Base x402 payment environment. It is appropriate when you want agent-native, pay-per-call access without managing an API key subscription, and when the 'live' or other Abstract Exchange-specific operations are what you require.

## Known failure modes

- Invalid or unsupported operation name returns an error indicating the operation is not allowlisted
- Missing or malformed input parameters cause a 400-level error
- Payment failure via x402/USDC on Base mainnet prevents the call from completing
- Abstract Exchange upstream service unavailable results in a 5xx or empty data response
- Insufficient USDC balance for the $0.05 per-call fee causes payment rejection

## How this service works

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

## Output

A JSON object containing the data payload returned by the Abstract Exchange provider, including fields relevant to the requested operation (e.g. live prices, trade data, liquidity metrics), along with the provider name ('abstract_exchange') and the operation type used.

## 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": "abstract_exchange",
  "operation": "live"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-abstract-exchange-on-chain-data-provider-7f1d2652/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)