Browse documentation
TurnitPass product updates
Recent platform changes across the humanizer, AI detector, writing tools, billing, and API.
Latest platform notes
Developer API expanded
Added authenticated v1 endpoints for humanize, paraphrase, rewrite, detect, citation, bibliography, and API key status.
/humanize/detect/citation/statusTimeline
Citation exports expanded
Citation and bibliography responses now include formatted HTML, plain text, BibTeX, and RIS output for common academic and technical styles.
Document import warnings surfaced
TXT, Markdown, DOCX, and PDF imports now keep source kind, filename, and parser warnings visible in writing and detector workflows.
Detector response normalized
Detector-style scans now return review estimates, source context, status, and writing-signal metadata through the same public API shape.
Writing tools added
Launched usable AI rewriter, paraphrase, detector, citation generator, and bibliography generator pages backed by the shared writing workflow.
Homepage workbench
Shipped the TurnitPass humanizer homepage with document input, processing language selection, rewrite action, and side-by-side result review.
Workspace usage overview added
Added workspace summary surfaces for word balance, subscription state, API keys, and recent usage so billing and developer access stay together.
Integrated plan limits
Checkout, billing portal, and plan-limit code paths are in place while production settings remain externally configurable.
Private API key storage
API keys are shown once, stored as secure hashes, and can be revoked without changing Google account access.
Update streams
Humanizer and AI detector
Changes to AI-writing signal estimates, side-by-side review, and revision notes.
Citation and bibliography
New source types, citation formats, BibTeX/RIS export behavior, and bibliography sorting logic.
Developer platform
API key lifecycle, limits, status fields, usage logging, and workspace controls.
Public pages
Notion-style page updates, comparison pages, feature pages, pricing, contact, and localized shells.
Release policy
The changelog follows the same product boundary as the API platform: public notes cover endpoint behavior, billing surfaces, document parsing, and visible workflow changes. Internal implementation details stay unpublished unless they affect public behavior.
API compatibility notes
FAQ
What do changelog entries cover?
Behavior changes, endpoint impact, and compatibility expectations, with examples where they help.
How should API clients handle new response fields?
Treat unknown fields as additive metadata. Clients should parse the fields they need and ignore additional keys unless the API reference says otherwise.
Where do billing configuration changes appear?
Billing behavior is noted here when checkout, portal, or plan-limit logic changes. Production credentials are configured securely outside the codebase.