mlx-sms-verify
SMS / OTP verification queue for Multilogin Cloud Phone antidetect Android
Community SDK — not affiliated with Multilogin GmbH. Requires your own Multilogin subscription.
Why this package
Mobile verify — Cloud Phone minutes promo MIN50.
| Problem | This tool |
|---|---|
| Scattered scripts for Multilogin workflows | Typed helpers + CLI you can import in CI |
| Unclear browser vs Cloud Phone choice | mlx-sms recommend --use-case sms_verify |
| Partner offers hard to verify | Structured disclosure via mlx-sms affiliate |
Install
pip install mlx-sms-verify
export MLX_API_TOKEN="your_token" # from Multilogin dashboard
mlx-sms doctor
Quick start
mlx-sms estimate --jobs 50
mlx-sms queue --profile-id ID --app tiktok --country VN
# Library usage
from mlx_sms_verify import __version__
import mlx_sms_verify.core as core
CLI reference
| Command | Purpose |
|---|---|
mlx-sms doctor |
Token, env, package health |
mlx-sms recommend |
Browser vs Cloud Phone guide |
mlx-sms affiliate |
Partner disclosure + SAAS50 / MIN50 |
mlx-sms seo --json |
PyPI / docs metadata |
Run mlx-sms --help for domain-specific commands.
Account group (acc-1)
Publish these four packages on the same PyPI account:
| Package | Role |
|---|---|
| mlx-browser-sdk | Companion on same PyPI account |
| selenium-mlx-connector | Companion on same PyPI account |
| account-farm-csv | Companion on same PyPI account |
Related: Cloud Phone stack
| Package | Role |
|---|---|
| mlx-cloud-phone | Mobile SDK + mlx-phone |
| cloud-phone-geo | Country / proxy presets |
| cloud-phone-warmup | Mobile warmup |
| cloud-phone-fleet | Bulk fleet |
Partner disclosure
We publish independent tooling for Multilogin users and may earn a commission when you use partner offers. Always verify discount lines at checkout.
| Product | Code | Where |
|---|---|---|
| Multilogin X browser plans | SAAS50 | SaaSVerdict |
| Cloud Phone minutes | MIN50 | SaaSVerdict |
| Scripts & alerts | — | @Multilogin_Scripts_Bot |
mlx-sms affiliate --json
mlx-sms recommend --use-case sms_verify
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for mlx-sms-verify 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mlx_sms_verify-2.0.0.tar.gz | 10.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mlx_sms_verify-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.6 kB
Release files / mlx_sms_verify-2.0.0.tar.gz
| Download URL | mlx_sms_verify-2.0.0.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
31291d0cc329d1fa984e288681654ace0047b7a0fd61c281ebcd420dc23545c5
|
|
BLAKE2b-256 checksum How to use checksums |
f4cb41f395bd436f01d34f4b78a31cc6cd0c4d0d91e86e61b0f9dc05f17b85da
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / mlx_sms_verify-2.0.0-py3-none-any.whl
| Download URL | mlx_sms_verify-2.0.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5a83343bcf8afb475008d537a3fba7d291b3ffeadeb1d7255e4fc9a32c752ff8
|
|
BLAKE2b-256 checksum How to use checksums |
078bf7aa4ae106530aac788f6771a71f06030c0a365837e55506b2b055af79fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for mlx-sms-verify 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
