Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →verifypdf/verifypdf
Verify whether a PDF document (bank statement, payslip, invoice, tax return, ID, contract) is authentic or has been forged, AI-generated or edited.
Passed 16 of 20 test cases with the skill, and 7 of 20 without it.
and 7 more in the full report
10 fixed8 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When the document API returns `fraud_risk` as `medium`, what corresponding status label appears in the VerifyPDF web dashboard for human reviewers?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies that the dashboard displays the label "Needs Attention" for medium fraud risk. | Missed | Passed |
The instructions your model reads when the skill loads.
Verify a PDF with VerifyPDF's forensic API. One submit, poll for the verdict,
read back a trust_score, a fraud_risk label and the fraud warnings.
VerifyPDF detects forged and manipulated PDFs: AI-generated bank statements and payslips, documents edited after creation, template forgeries and metadata anomalies. It works on any HTTP client, no SDK required.
Every call needs your VerifyPDF API key in the API-KEY request header.
key_live_ and consume your plan allowance.key_test_, are free, and return a deterministic
verdict from the filename (see "Testing" below). Use a test key to confirm
the integration works before spending live quota.Get a key from the Developers section of https://secure.verifypdf.com. API access is on the Professional and Corporate plans.
This skill resolves the key in this order:
VERIFYPDF_API_KEY environment variable (recommended for production and
CI — keep the secret out of files on disk)..verifypdf-key file in this skill's own directory, containing nothing
but the key on a single line. Copy .verifypdf-key.example to
.verifypdf-key and paste your key in. The file is git-ignored.If neither is set, the helper scripts stop and tell the user how to add one. Never paste the key into a chat prompt or echo it into logs.
The two helper scripts in this directory do all of this for you. The flow they
implement, against base URL https://api.verifypdf.com:
POST /v2/document as multipart/form-data with the field
file (the PDF) and an optional custom_id. Returns 202 Accepted with a
document_id. The bytes go to the API directly; never base64-encode the PDFtest cases passed, vs 7 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.