This release is a pre-release and may not be stable for production use.
openai-billing-playwright
Fetch openai billing info from command line
Install it
Download the latest release and unzip.
Use it
Run openai-billing.exe from command line.
openai-billing.exe --help
openai-billing.exe u@gmai.com pw1 u2@gmai.com pw2
# check two pairs
openai-billing.exe u@gmai.com pw1 u2@gmai.com pw2
# or when special characters (&, * etc) are in passwords
openai-billing.exe "u@gmai.com pw*1 u2@gmai.com pw2&"
# check pairs in clipboard
openai-billing.exe openai_billing
# check pairs in a file
openai-billing.exe --filename email-pw-pairs.txt
# use a proxy
openai-billing.exe --proxy soscks5://127.0.0.1:1080 u@gmai.com pw1 u2@gmai.com pw2
# turn on browser: to see the whole thing in action
openai-billing.exe u@gmai.com pw1 --headful
# turn on debug
set LOGURU_LEVEL=TRACE
openai-billing.exe u@gmai.com pw1 --headful
Use it with python
pip install openai-billing
# pip install git+https://github.com/ffreemt/openai-billing-playwright
# poetry add git+https://github.com/ffreemt/openai-billing-playwright
# git clone https://github.com/ffreemt/openai-billing-playwright && cd openai-billing-playwright
python -m openai_billing
# or
openai-billing
# help
python -m openai_billing --help
# check two pairs
python -m openai_billing u@gmai.com pw1 u2@gmai.com pw2
# or special characters (&, * etc) in passwords
python -m openai_billing "u@gmai.com pw*1 u2@gmai.com pw2&"
# check pairs in clipboard
python -m openai_billing
# check pairs in a file
python -m openai_billing --filename email-pw-pairs.txt
# use a proxy
python -m openai_billing --proxy soscks5://127.0.0.1:1080 u@gmai.com pw1 u2@gmai.com pw2
# turn on browser: to see the whole thing in action
python -m openai_billing u@gmai.com pw1 --headful
# turn on debug
set LOGURU_LEVEL=TRACE
python -m openai_billing u@gmai.com pw1 --headful
Metadata
Release files for openai-billing 0.1.0a2
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 | Actions |
|---|---|---|---|---|
| openai_billing-0.1.0a2.tar.gz | 6.8 kB | Without provenance | Details for openai_billing-0.1.0a2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| openai_billing-0.1.0a2-py3-none-any.whl | Python 3 | none | any | Details for openai_billing-0.1.0a2-py3-none-any.whl |
Total release size: 14.5 kB
Release files / openai_billing-0.1.0a2.tar.gz
| Download URL | openai_billing-0.1.0a2.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d1b4e93367d130ac916412232847ca5c2d7a3567c3203d0c07e5b70d561010d
|
|
BLAKE2b-256 checksum How to use checksums |
cacbf3d793a42a70e4f13e8fe8c28fe8c3af51d0ac8dbac14c75db48c8d0cbe2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.8.10 Windows/10
|
Release files / openai_billing-0.1.0a2-py3-none-any.whl
| Download URL | openai_billing-0.1.0a2-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
439f64a410590bd56a8aeadef764bdcc159d7fe15bd560d15ff45cd51e9f2c61
|
|
BLAKE2b-256 checksum How to use checksums |
f7c4eba290ca937c6c6e8d56a00023796d1469bb4f9f493c75c93197ff8837fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.5.1 CPython/3.8.10 Windows/10
|
Security for openai-billing 0.1.0a2
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.