# Phone Number Validation (Batch)

> Phone Number Validation (Batch) is a paid API for AI agents from x402.professorsausages.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Validates and normalizes up to 25 phone numbers in a single call, returning per-item E.164 format, line type, region, and verdict using pure CPU processing with no upstream dependencies.

## Facts

- Endpoint: POST https://x402.professorsausages.com/phone-check/batch
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/phone-number-validation-batch-38d73b68
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-N69A7VFFvbSVkj4fbhvW

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 phone-number-validation-batch-38d73b68 -d '<json body>'
```

Example prompt: Can you validate these 5 phone numbers for me and tell me which ones are real, what type of line they are (mobile, landline, etc.), and their normalized E.164 format: +14155552671, +442071838750, +61291234567, 5551234567, and +33-1-40-79-75-00?

## When to prefer this

Use this endpoint when you need to validate or normalize multiple phone numbers at once (up to 25) without making separate API calls. Because it runs on pure CPU with no upstream dependencies, it is extremely fast and reliable. Prefer this over single-number validation endpoints when dealing with lists of contacts, form submissions, or CRM data cleanup. It is ideal for pre-send validation before SMS campaigns or lead qualification pipelines.

## Known failure modes

- Batch exceeds 25 numbers — request rejected or truncated
- Malformed input schema — missing required 'input' field returns validation error
- Unparseable phone number strings return per-item error rather than failing the whole batch
- Payment not received or insufficient USDC — x402 payment required error
- Rate limiting if too many calls made in rapid succession

## Output

A per-item result set for each submitted phone number, including: whether the number is valid, its normalized E.164 representation, line type (mobile, landline, VoIP, etc.), geographic region/country, and a pass/fail verdict. Results are error-isolated so a bad number in the batch does not fail the entire request.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/phone-number-validation-batch-38d73b68/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.professorsausages.com](https://www.zero.xyz/host/x402.professorsausages.com/llms.txt)