jevgram
jevgram is a small command-line tool that checks if a document is AI-generated. Similar to pangram but a lot cheaper. You need API key from TYPESAFE_API_KEY (super easy, couple of clicks)
Supported inputs
- Plain text and source-like text files, such as
.txt,.md,.tex, and similar files - PDF files
- DOCX files
Minimal example:
$ export TYPESAFE_API_KEY=apikey_...
$ pipx install jevgram
$ jevgram README.md # this document
File: README.md
Type: text
Characters extracted: 1957
Characters sent to JEV: 1957
Model: jev-1.13.0
Prediction: AI
Probability AI: 87.00%
Probability human: 13.00%
Confidence: 74.00%
PDF extraction uses pypdf. DOCX extraction is handled directly from the Word XML contained in the .docx file.
Detailed instructions
Install
With pipx (MacOS, Linux):
pipx install jevgram
With uvx:
uvx jevgram --help
API key
jevgram uses TypeSafe JEV API. Set one of these environment variables before running it:
export TYPESAFE_API_KEY="your-key"
# or
export JEV_API_KEY="your-key"
You can also pass a key directly with --api-key, but environment variables are safer for shell history and scripts.
Usage
jevgram document.txt
jevgram paper.pdf
jevgram manuscript.docx --json
By default, long files are sampled down to 32,000 characters using the beginning, middle, and end of the extracted text. To send the whole extracted document, use:
jevgram document.txt --max-chars 0
To inspect extraction without calling JEV:
jevgram document.pdf --extract-only
To inspect the request body without calling JEV:
jevgram document.txt --dump-request
Output
Human-readable output includes the predicted class, AI probability, human probability, confidence when provided by JEV, and whether the input was truncated. --json produces machine-readable output for scripts.
Cost
This app is open-source/free on my end, but it uses JEV API, which is not free. Works like this: once you create a TYPESAFE account and API key, you get a credit for $5 free usage. jevgram is intended for personal use, and you can check a lot of documents for $5. Once you use up the free credit, jevgram will fail and politely tell you to add credit card number to TYPESAFE (to be fair, this is untested because I have not reached that point yet)
Notes
Authorship detection is probabilistic.
This document is mostly AI :-)
Metadata
Release files for jevgram 0.1.3
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 | |
|---|---|---|---|---|
| jevgram-0.1.3.tar.gz | 9.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jevgram-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.3 kB
Release files / jevgram-0.1.3.tar.gz
| Download URL | jevgram-0.1.3.tar.gz |
|---|---|
| Size | 9.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0557f438f17a86c1c06f059faffdcfb657ecce93485ba580b8bb6845563aabed
|
|
BLAKE2b-256 checksum How to use checksums |
9a3b1be32d7e22d6aa801e83313e2c48bc168190ba5e28388885256ed8900f53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.4
|
Release files / jevgram-0.1.3-py3-none-any.whl
| Download URL | jevgram-0.1.3-py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
955ef932e668458ff8acb2a66fad45e4f6b4ad9675557bc0392970a4f517b83c
|
|
BLAKE2b-256 checksum How to use checksums |
f1b417d91c7784c0c061ca1eb27ee386da6797668e0f131f8ec4896004590fc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.4
|
Security for jevgram 0.1.3
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.