tinyantigate
============
Tinest (as I can imagine) antigate/anti-captcha api wrapper. It's just a **subset** of antigate api. It can only:
* send captcha
* check captcha status
* check balance
* abuse
## Reasons
* [Antigate](https://github.com/gotlium/antigate) wrapper uses [grablib](http://grablib.org/), so it comes with a bit more dependences (like pycurl, lxml, etc.).
* [requests](docs.python-requests.org) is just awesome!
* [Antigate](https://github.com/gotlium/antigate) wants filename of captcha, but in most cases you need to pass 'this' bytes (from requests response, for example), and you defenitly don't want to create files.
* uniform calls
## Requirements
* Python 3
* requests
## Usage
All methods, can return errors:
* 'ERROR_*', None (from [antigate list](https://anti-captcha.com/apidoc))
* 'ERROR_HTTP', status_code (requests errors)
### Automatic (most common usage)
#####antigate function
```python
from tinyantigate import antigate
status, text = antigate(
your_key_from_antigate,
bytes_of_your_captcha,
timeout=5, # \
count=6, # ) default values (can be omitted)
host="anti-captcha.com", # /
)
```
This function is just wrapper around creation Antigate object and calling 'run' function.
### Manual usage
##### Creating:
```python
import tinyantigate
a = tinyantigate.Antigate(your_key_from_antigate, host="anti-captcha.com")
```
##### Sending captcha:
```python
status, captcha_id = a.send(bytes_of_your_captcha)
```
Return values:
* 'OK', captcha_id
##### Getting status:
```python
status, text = a.status(captcha_id)
```
Return values:
* 'OK', captcha_text
* 'CAPCHA_NOT_READY', None (yeah, CA**PC**HA_NOT_READY, it's antigate funny mistake)
##### Abuse:
```python
status, data = a.abuse(captcha_id)
```
Return values:
* "", None
##### Balance:
```python
balance, data = a.balance()
```
Return values:
* balance, None
`balance` as string
##### Run:
```python
status, text = a.run(bytes_of_your_captcha, timeout=5, count=6)
```
Mix of 'send' and 'status' functions. Timeout is the delay between checks of captcha status. Count is number of checks.
Return values:
Same as for 'send' and 'status' functions.
============
Tinest (as I can imagine) antigate/anti-captcha api wrapper. It's just a **subset** of antigate api. It can only:
* send captcha
* check captcha status
* check balance
* abuse
## Reasons
* [Antigate](https://github.com/gotlium/antigate) wrapper uses [grablib](http://grablib.org/), so it comes with a bit more dependences (like pycurl, lxml, etc.).
* [requests](docs.python-requests.org) is just awesome!
* [Antigate](https://github.com/gotlium/antigate) wants filename of captcha, but in most cases you need to pass 'this' bytes (from requests response, for example), and you defenitly don't want to create files.
* uniform calls
## Requirements
* Python 3
* requests
## Usage
All methods, can return errors:
* 'ERROR_*', None (from [antigate list](https://anti-captcha.com/apidoc))
* 'ERROR_HTTP', status_code (requests errors)
### Automatic (most common usage)
#####antigate function
```python
from tinyantigate import antigate
status, text = antigate(
your_key_from_antigate,
bytes_of_your_captcha,
timeout=5, # \
count=6, # ) default values (can be omitted)
host="anti-captcha.com", # /
)
```
This function is just wrapper around creation Antigate object and calling 'run' function.
### Manual usage
##### Creating:
```python
import tinyantigate
a = tinyantigate.Antigate(your_key_from_antigate, host="anti-captcha.com")
```
##### Sending captcha:
```python
status, captcha_id = a.send(bytes_of_your_captcha)
```
Return values:
* 'OK', captcha_id
##### Getting status:
```python
status, text = a.status(captcha_id)
```
Return values:
* 'OK', captcha_text
* 'CAPCHA_NOT_READY', None (yeah, CA**PC**HA_NOT_READY, it's antigate funny mistake)
##### Abuse:
```python
status, data = a.abuse(captcha_id)
```
Return values:
* "", None
##### Balance:
```python
balance, data = a.balance()
```
Return values:
* balance, None
`balance` as string
##### Run:
```python
status, text = a.run(bytes_of_your_captcha, timeout=5, count=6)
```
Mix of 'send' and 'status' functions. Timeout is the delay between checks of captcha status. Count is number of checks.
Return values:
Same as for 'send' and 'status' functions.
Metadata
Release files for tinyantigate 0.1.1
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 | |
|---|---|---|---|---|
| tinyantigate-0.1.1.tar.gz | 2.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tinyantigate-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.4 kB
Release files / tinyantigate-0.1.1.tar.gz
| Download URL | tinyantigate-0.1.1.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4b91a7278d779b111498be3413dfa46956783ee473785f50eb7f3a400960ecdd
|
|
BLAKE2b-256 checksum How to use checksums |
833b52c16403a0d3f24f3ef553135686f7ce1de9db1bf3cb89faf6c8b511fed3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / tinyantigate-0.1.1-py3-none-any.whl
| Download URL | tinyantigate-0.1.1-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
570a4f5fb07fc8fb9b27203d2d41fdcde23b2dd5ee665f65467ab93383fca185
|
|
BLAKE2b-256 checksum How to use checksums |
6dc0ed2312d9d12fe401f2a271dae0e16c5b0424b6afaf83c87b9c97bec9bf97
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tinyantigate 0.1.1
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.