# Prysm Abstract Phone Lookup

> Prysm Abstract Phone Lookup is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-10-21).

Performs phone number lookup and intelligence operations via the Abstract Phone provider, paid per-call with USDC over x402 on Base mainnet.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/abstract_phone?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-abstract-phone-lookup-0be462d4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sKXTIlNZrmpcy8GK2E8Vi

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-phone-lookup-0be462d4 -d '<json body>'
```

Example prompt: Can you look up the carrier and line type for the phone number +14155552671 using the Abstract Phone provider on Prysm?

## When to prefer this

Choose this endpoint when you need real-time phone number intelligence — carrier, line type, validity, or geographic metadata — and are already operating in a Web3/x402 payment environment using USDC on Base. It is ideal for agents that need pay-per-call phone enrichment without managing a traditional API key subscription, or when integrating phone validation into an on-chain-native workflow.

## Known failure modes

- Invalid or malformed phone number input returns an error or empty data payload
- Unsupported operation string returns a provider error
- Insufficient USDC balance or failed x402 payment causes a 402 response before execution
- Rate limiting or provider downtime may cause timeouts or 5xx errors
- Non-allowlisted operation values are rejected by the API

## How this service works

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

## Output

Returns a JSON object with the provider name ('abstract_phone'), the operation performed (e.g. 'lookup'), and a data payload containing phone intelligence such as carrier, line type (mobile/landline/VoIP), country, validity status, and other provider-specific fields.

## 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_phone",
  "operation": "lookup"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-abstract-phone-lookup-0be462d4/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)