How is HTPBE? different from KYC platforms like Onfido or Persona?
KYC platforms check that a document looks authentic — correct template, matching identity, valid format. HTPBE? checks whether the specific PDF file was modified after it was generated. These are different layers of fraud detection.
A bank statement can pass every KYC template check and still have edited balances. HTPBE? detects the modification at the file structure level — xref tables, incremental updates, producer field inconsistencies.
← Previous
What does HTPBE? stand for, and how do you pronounce it?
Next →
What does the API response look like?
Related questions
Keep reading
3 answers
Pricing & API
The API returns a structured JSON verdict: INTACT, MODIFIED, or INCONCLUSIVE. For modified documents, the response includes specific modification_markers — the named forensic signals that triggered the verdict, such as “Multiple xref tables detected” or “Incremental update chain length: 3”.
No black-box scores — every verdict is explained. See the full response schema at github.com/htpbe/docs.
Every check costs one credit, whether it runs from the web app or the API — both draw from the same balance.
You can fund that balance three ways: a monthly subscription (Starter $15/mo for 30 credits, Growth $149/mo for 350, Pro $499/mo for 1,500, Enterprise custom), a one-time pack ($5 for 8 credits, $15 for 25 credits, no subscription required), or the 5 free credits every new account gets on signup. They spend in that order — subscription balance first, then packs, then welcome credits.
Credits don’t expire while your account stays active, and test API keys are free and unlimited — they never draw from your balance.
Yes. Test keys (htpbe_test_...) are available on all plans including before you subscribe. They return deterministic synthetic results for integration testing and do not consume monthly quota.
Test keys only accept test URLs — they cannot be used to analyze real documents.