SMS Validator · Phone Number Validation
Validate phone number format and detect country from E.164 input.
What it does
Validate phone number format and detect country from E.164 input.
- Validate user phone numbers at signup
- Detect country code from international numbers
- Sanitize phone input for SMS delivery
Ideal buyer
Applications requiring phone validation before SMS sending or user verification workflows.
Run this through your governed agent wallet.
- 01Bootstrap AXON once with
npx @axon402/init. - 02Use the AXON runtime MCP tools to
search_x402_servicesorinspect_x402_offerfor this service. - 03Quote, test-buy, then run the governed paid fetch through AXON.
Send this
Prompt for your agent
A natural-language instruction for your LLM agent — with this endpoint exposed as a tool — to call this resource. Not sent to the endpoint; the endpoint consumes the JSON body below.
Pasting this prompt into a raw ChatGPT or unconfigured agent will notexecute the paid endpoint flow. Run it through an agent with the AXON runtime / MCP tools exposed (see “Use with AXON” above) so the 402 challenge, quote, and governed fetch are handled for you.
“Validate this phone number: +14155551234 with country hint US.”
Endpoint request body
The JSON payload your agent sends to the endpoint.
{
"phone": "+14155551234",
"countryCode": "US"
}Advanced HTTP details
For integrators who need the raw protocol surface. Most agents should use AXON above instead of calling these directly.
curl fallback
curl https://sms-validator-production-d5a0.up.railway.app/api/validate \ -H "Content-Type: application/json" \ -H "X-PAYMENT: [signed_payment_envelope]" \ -d '{"phone":"+14155551234","countryCode":"US"}'
Payment & settlement details
Raw on-chain settlement parameters. AXON above handles these automatically through quote / test-buy / governed fetch.
Price & network
Trust & risk
More in Tools
Browse all →Other resources in this category
Category proxy — we don't track live co-purchase signals yet.