scripter-x

Local Flipkart session extractor. It rents virtual numbers, logs into Flipkart, and extracts the login session JSON — running on your own machine (your residential IP), which is the only way the Flipkart login-verify completes (datacenter IPs get blocked). Results sync automatically to your ScripterX dashboard for storage + export.

Install

npm install -g scripter-x

That installs the scripterx command. Needs Node 18+.

Use

Just run it for the interactive shell:

scripterx

You get a prompt. Type a command, or press / to open the command palette.

Selecting from a menu — three ways

• Press 1–9 to instantly pick that row ⭐ (most reliable)
• ↑/↓ then Enter to navigate
• Click a row (best-effort; works when the screen hasn't scrolled)

Yes/no questions: ←/→ to toggle (or y/n), Enter to accept.

One-shot commands

You can also run any command directly without the shell:

scripterx login
scripterx run --provider otpcart --count 10 --concurrency 2 --check-minutes
scripterx campaigns
scripterx export <name>          # → ~/Downloads/scripterx/<name>.json
scripterx balance
scripterx config set server <url>

How it works

1. You run it locally → all Flipkart calls go from your residential IP (with a built-in 2-second gap between calls so you're never rate-limited).
2. It rents a number (OTPCart or TempOTP), sends the OTP, reads the SMS, verifies, and extracts the full session.
3. Each result is pushed to your ScripterX server (encrypted at rest) — view and export from the web dashboard, or auto-saved locally to ~/Downloads/scripterx/.
4. Only successful extractions cost money — failed/cancelled numbers are refunded.

Config + token live in ~/.scripterx/config.json. Point at a different backend with scripterx config set server <url> or the SCRIPTERX_SERVER env var.