What does the API response look like?
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.
← Previous
How is HTPBE? different from KYC platforms like Onfido or Persona?
Next →
How much does each document check cost?
Related questions
Keep reading
3 answers
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.
Yes — this is the primary use case for lending teams. HTPBE? detects edited bank statements at the file structure level: multiple xref tables indicating post-export editing, producer field showing Excel or a consumer PDF tool instead of a banking system, and modification timestamps that differ from creation timestamps.
See the fake bank statement detection guide for integration details.