The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the SMS Validator API listing page.
Validate SMS-capable phone numbers -- mobile vs landline detection, carrier type, E.164 format, SMS readiness. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.
Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):
Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.
| Tool | Method | Path | Price | Description |
|---|---|---|---|---|
sms_validate_number | POST | /api/validate | $0.005 | Validate if a phone number can receive SMS |
sms_validate_numberUse this when you need to check if a phone number can receive SMS messages. Returns SMS capability data in JSON.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
phone | string | yes | Phone number with country code (e.g. +14155551234) |
countryCode | string | no | ISO 3166-1 alpha-2 country code hint (e.g. US, FR, GB) |
Example response:
When to use: sending SMS campaigns, FOR filtering landlines from SMS lists, verifying 2FA phone numbers, and OTP delivery validation.
Not for: full phone validation with carrier lookup (use phone_validate_number), email validation (use email_verify_address), address validation (use address_validate).
eip155:8453)100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.
MIT