Quick start
How it works
1
Upload
Send a PDF via
multipart/form-data. Max 50 MB, max 100 pages.2
Extract
Text is extracted from each page using the PDF text layer. Pages with fewer than 20 characters of extractable text are skipped. A SHA-256 hash of the raw file is computed for chain-of-custody verification.
3
Detect
Each page is analyzed against your chosen detection endpoints in parallel (bounded concurrency of 3 pages at a time). Long pages are chunked before analysis.
4
Aggregate
Per-page results are aggregated into an overall risk score, severity level, and list of flagged pages. Incidents are recorded and webhooks triggered for flagged content.
Available endpoints
You can run any combination of these 8 detection endpoints against each page:
Default endpoints (when
endpoints is omitted): unsafe, coercive-control, radicalisation.
Request parameters
Upload your PDF as amultipart/form-data request. The file field must be named file.
Response
Key response fields
Credit pricing
Document analysis uses dynamic pricing based on the actual work performed:
The minimum charge is 10 credits (covers extraction overhead). Each page-endpoint combination costs 1 credit.
Choose your endpoints carefully. Running 8 endpoints on a 100-page document costs 800 credits. For most use cases, the 3 default endpoints (
unsafe, coercive-control, radicalisation) provide comprehensive coverage.Chain-of-custody
Every response includes adocument_hash — a SHA-256 hash of the exact bytes uploaded. Use this to:
- Prove which file was analyzed in compliance audits
- Verify document integrity if the same file is analyzed again
- Include in incident reports for regulatory submissions
Zero retention
No document data is stored. The PDF is processed entirely in memory, analyzed, and discarded. The response is the only output. This is the same privacy-by-design approach used across all Tuteliq endpoints.