1
2 Comments

I built SMS-Act: fast, privacy-first SMS verification for 600+ apps

Hey Indie Hackers! I’ve been shipping a tool I wanted for ages: SMS-Act — a simple way to receive verification codes (OTPs) fast, with global virtual numbers, automatic refunds on fails, and a clean API.

The problem
When testing products, opening accounts, or running quick experiments, the OTP step often breaks flow. Many services are slow, opaque, or unreliable; refunds take tickets; APIs feel bolted on. That time sink kills momentum for solo founders.

What SMS-Act does

  • Instant SMS codes for 600+ services across 160+ countries

  • Auto refunds if a verification fails

  • Developer-friendly API to automate at scale

  • Privacy-first: use temporary numbers instead of exposing your main line

  • Simple pricing; no fluff

Who it’s for
Indie makers, growth folks, marketers, and teams that frequently spin up accounts, run ads, or validate ideas.

Why I’m building it
I got tired of OTP friction slowing experiments. SMS-Act exists to make verification boringly reliable so we can spend more time shipping.

Ask

  • If you regularly deal with OTPs, what’s your current workflow?

  • Which services/numbers should I prioritize next?

  • Would a Zapier/Make integration help your setup?

👉 Try it: https://sms-act.net
Happy
to answer anything in the comments!

posted to Icon for SMS-Act
SMS-Act
  1. 1

    Another idea for you: provide an API for app/website developers to verify phone number of their users. like users can sms verification code (provided by app/website) to local number, alloted by you, which you forward to app/website.

    PS. your try it link is not clickable. fix that.

  2. 1

    are you earning yet ?