Sms Validator X402

What is Sms Validator X402?

Sms Validator X402 validates SMS-capable phone numbers, detecting mobile vs landline, carrier type, E.164 format, and SMS readiness. It uses pay-per-call via x402 (USDC on Base L2) with no API key or signup, and is part of the klymax402 marketplace.

How to use Sms Validator X402?

Add the server URL to your MCP client config (Claude Desktop, Cursor, ElizaOS). Use the sms_validate_number tool with a required phone parameter (E.164 format) and optional countryCode (ISO 3166-1 alpha-2). For HTTP, use an x402-aware client that handles the 402 payment challenge automatically.

Key features of Sms Validator X402

• Validate SMS capability of phone numbers
• Mobile vs landline detection
• Carrier type and E.164 format
• Pay-per-call via x402 micropayments
• No API key, no signup, no rate limits
• Part of klymax402 marketplace

Use cases of Sms Validator X402

• Filtering landlines from SMS campaign lists
• Verifying 2FA phone numbers
• OTP delivery validation
• Checking if a number can receive SMS before sending

FAQ from Sms Validator X402

What does Sms Validator X402 check?

It checks if a phone number can receive SMS, returns carrier type (mobile/landline), E.164 format, and country code.

How is payment handled?

Payment uses the x402 protocol (HTTP-native pay-per-call) with USDC on Base L2. No signup or API key required.

What are the parameters for sms_validate_number?

The required parameter is phone (string, with country code). Optional parameter is countryCode (ISO 3166-1 alpha-2 hint).

What is Sms Validator X402 not for?

It is not for full phone validation with carrier lookup, email validation, or address validation.

Is there any rate limit?

No rate limit wall; it is pay-per-call with no signup or API key.