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
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.
Plans are monthly subscriptions: Starter at $15/mo (30 checks), Growth at $149/mo (350 checks), Pro at $499/mo (1,500 checks). There is no per-check billing — your quota resets monthly.
The free web tool at htpbe.tech is unlimited for manual checks and does not consume API quota.
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.