# DataVault Phone Number Validation

> DataVault Phone Number Validation is a paid API for AI agents from zetavault.vercel.app, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-15).

Validates a phone number and returns structured validation data including format, carrier, and line type information

## Facts

- Endpoint: POST https://zetavault.vercel.app/api/phone-validate
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/datavault-phone-number-validation-6ec02e73
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Wqjbp8qd39hbRwse27uY2

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 datavault-phone-number-validation-6ec02e73 -d '<json body>'
```

Example prompt: Can you validate this phone number for me — +14155552671 — and tell me if it's a real, active number, what carrier it's on, and whether it's a mobile or landline?

## When to prefer this

Use this endpoint when you need to validate a single phone number before storing it, sending an SMS, or onboarding a user. It is pay-per-call at $0.03 USDC, so well suited for on-demand validation rather than bulk operations. Prefer this over regex-only validation when you need carrier and line-type enrichment alongside format verification.

## Known failure modes

- Invalid or malformed phone number returns success:false or validation error
- Missing required 'phone' field returns 400 error
- Unsupported country or phone format may return limited data
- Payment failure via x402 returns 402 Payment Required
- Rate limiting or service downtime returns 5xx error

## How this service works

54 endpoints spanning local tools, live data feeds, and AI-powered text processing. Pay-per-call with USDC on Base.

## Output

Returns a JSON object with a success boolean and a data object containing phone validation results such as whether the number is valid, its formatted form, line type (mobile/landline/VOIP), carrier name, and country information.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "phone"
 ],
 "properties": {
  "phone": {
   "type": "string"
  },
  "country": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object"
  },
  "success": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/datavault-phone-number-validation-6ec02e73/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from zetavault.vercel.app](https://www.zero.xyz/host/zetavault.vercel.app/llms.txt)