Odel
SMS Validator API

SMS Validator API

@br0ski777TypeScriptMITUpdated 4 days ago

Validate SMS-capable phone numbers — mobile vs landline, E.164 format. x402 micropayment.

View on GitHubSign in to connect
Server endpointStreamable HTTPNo authProbed

Registry lists this as SSE; the live endpoint answered over Streamable HTTP.

https://sms-validator.api.klymax402.com/mcp

This is the third-party server itself — Odel doesn't run it. Hitting this URL directly talks straight to the upstream server with no auth or proxying. Connect through Odel to front it with managed auth.

SMS Validator API

MCP Server x402 License: MIT

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.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "sms-validator": {
      "url": "https://sms-validator.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://sms-validator.api.klymax402.com/api/validate" \
  -H "Content-Type: application/json" \
  -d '{"phone":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
sms_validate_numberPOST/api/validate$0.005Validate if a phone number can receive SMS

sms_validate_number

Use this when you need to check if a phone number can receive SMS messages. Returns SMS capability data in JSON.

Parameters

NameTypeRequiredDescription
phonestringyesPhone number with country code (e.g. +14155551234)
countryCodestringnoISO 3166-1 alpha-2 country code hint (e.g. US, FR, GB)

Example response:

{"phone":"+14155551234","canReceiveSMS":true,"carrierType":"mobile","e164":"+14155551234","countryCode":"US","numberType":"mobile","carrier":"T-Mobile"}

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).

Example agent prompts

  • "Check if a phone number can receive SMS messages"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT