Summary

SMSBazaar is a single-page application that compares pricing and inventory for SMS verification services, specifically for OpenAI (ChatGPT) usage. It targets users needing cost-effective, readily available virtual phone numbers for account verification, offering a unified, real-time dashboard to streamline provider selection and optimize spending.

How It Works

The backend Express API periodically polls up to seven SMS platform APIs, normalizing data by ISO2 country codes and converting prices to CNY/USD. A frontend React SPA consumes this aggregated data, allowing users to sort and filter by country, platform, availability, and price. Data refreshes every minute, with specific optimizations for SMSPool to manage API rate limits and ensure accurate stock reporting.

Quick Start & Requirements

• Installation: Local Dev: npm install, cp .env.example .env, npm run dev. Production: npm install, npm run build, npm start.
• Prerequisites: Node.js 20+ or newer, npm, and API keys for desired SMS platforms.
• Resource Footprint: Requires API keys and a local SQLite database. Production service listens on PORT=8787.
• Links: Online access: https://sms.fur.li/

Highlighted Details

• Compares SMS verification prices and stock for OpenAI/ChatGPT.
• Integrates 7 SMS providers: Hero SMS, SMSBower, 5sim, NexSMS, GrizzlySMS, SMS Verification Number, SMSPool.
• Normalizes country data (ISO2) and displays prices in CNY/USD.
• Supports sorting/filtering by country, platform, status, price, and stock.
• Offers multiple business modes: pre-registration OAuth, post-registration OAuth, and recommended countries.
• Backend data refresh defaults to 1 minute.

Maintenance & Community

No specific details regarding maintainers, community channels (like Discord or Slack), or sponsorships are present in the provided README.

Licensing & Compatibility

• License: MIT License.
• Compatibility: Permissive MIT license allows commercial use and integration into closed-source projects.

Limitations & Caveats

Configuration requires managing API keys for each SMS provider. Manual refresh is protected by an administrator token; missing token results in a 503 error. Production deployments should disable EXPOSE_PROVIDER_ERRORS for security. Specific configurations are needed for SMSPool to manage API rate limits and ensure accurate inventory.