Single-scan workflows break the moment a teacher has 200 essays a term, an agency has 40 freelance drafts a week, or a content platform has thousands of user submissions a day. TextSight bulk scanning runs on two surfaces backed by the same classifier. The Bulk Scan UI accepts paste, drag-and-drop file upload across 11 formats, and ZIP archives of multiple documents into one queue. The REST batch endpoint at api.textsight.ai/scan/v1/batch accepts an array of documents and returns an array of scored results in one call, with webhook callbacks for asynchronous pipelines. Both live on the Business tier with five workspace seats, shared scan history, and a workspace-wide audit log.
Free, Starter, and Pro cover individual reviewers. Business adds the Bulk Scan UI, the REST batch endpoint, webhook callbacks, 5 workspace seats, the audit log, and white-label PDF reports. Yearly billing saves 25%.
Billed $89.88/year, Save $30
Billed $179.88/year, Save $60
Billed $359.88/year, Save $120
Yearly billing saves 25%. View full pricing →
Both paths read from the same workspace and run the same model. The UI is the right answer when a human is sorting and triaging; the REST endpoint is the right answer when another system is the trigger.
Open the dashboard, click Bulk Scan, and paste, drag-and-drop, or upload a ZIP. The unified extractor handles .docx, .pdf, .txt, .md, .rtf, .odt, .epub, .html, .pptx, .xlsx, and .csv. Each item lands in a queue row with Authenticity Score, band label, word count, and sentence highlights. Sort by score ascending to triage the highest-risk submissions first. Click any row to open the full reading view with green, yellow, and red highlight spans for Human, Mixed, and AI sentences. The queue persists across refreshes and shares with every seat on the workspace.
POST an array of documents to api.textsight.ai/scan/v1/batch with an Authorization Bearer header and get an array of scored results in one call. Each result carries the score, the band, per-sentence labels with start and end offsets, and per-model confidence. Webhook callbacks let a CMS, LMS, or moderation pipeline submit a batch and forget the connection. The endpoint is the same one used by the Chrome extension and WordPress plugin in production, so the contract is well-exercised rather than a marketing diagram.
Under 50 documents on a one-off basis with a human reviewer, the Bulk Scan UI is faster to set up and gives visual triage. Over 50 documents, recurring jobs, or anything you want logged to a database, the REST endpoint is the right answer. Both paths draw from the same Business allowance, so an account never gets penalised for switching between them mid-week.
The four workflows we see most often. The UI handles the first two, the REST endpoint handles the second two, and the workspace audit log holds the trail for all four.
An agency editor receives ten to forty drafts a week from freelancers and needs a defensible QA step before invoicing. Open Bulk Scan, drag the week's drafts in, sort by Authenticity Score, and paste per-piece result links into the project tracker. Workspace seats let two editors share one billing and one history, and a multi-client setup keeps each client's history in its own workspace so the audit trail stays clean.
An English department processes 200 essays a term across four sections. The class submission folder gets dragged into Bulk Scan; ZIP upload handles a whole section at once. The queue sorts by score so the teacher reviews the highest-risk band first. White-label PDF export captures each result as an academic-integrity record, and the workspace audit log carries who scanned what and when as the artifact the dean asks for.
A user-generated content platform screens every submission before publish via the REST batch endpoint. The publish hook sends an array of pending posts, the response comes back with score, band, and highlights per post, and posts above the AI-likelihood threshold soft-block for human review. Webhook delivery handles the asynchronous case when the moderation queue spikes during product launches or seasonal traffic.
An SEO team or an editorial group audits a content archive for AI-written copy that pre-dates the team's quality bar. The audit script reads the sitemap, fetches each post, and batches them through the REST endpoint overnight. Results land in a warehouse table with score, band, and per-piece highlights; dashboards aggregate by writer, client, and project. Flat allowance pricing fits the steady nightly volume; credit pricing would burn the budget on this shape.
The Bulk Scan UI accepts paste, drag-and-drop, and ZIP archives. The unified extractor handles 11 file formats through officeparser, the same library the Unified Bulk Scan and File Extract endpoint runs in production.
.docx for Microsoft Word, .pdf for native PDFs (image-only PDFs need OCR first), .rtf, .odt for OpenDocument, and .epub for ebooks. The extractor pulls clean text from each one, drops document metadata, and queues the result as if it had been pasted in by hand.
.txt for plain text, .md for Markdown, and .html for web pages. Markdown formatting is stripped before scoring so the classifier sees prose rather than syntax. HTML tags are stripped the same way.
.pptx for PowerPoint decks (slide text is concatenated in slide order), .xlsx for spreadsheets (cell text is concatenated across sheets), and .csv for tabular exports. Useful when student submissions or client deliverables arrive as decks rather than essays.
Drop a ZIP of any combination of those formats and the queue unpacks them document by document. A class folder of 30 essays in mixed .docx and .pdf becomes 30 queue rows in one upload.
Bulk results are useless without a triage rule. The Authenticity Score collapses to one of five bands, and the queue sorts by band so you can act on the extremes first.
Clearly human writing. Pass through without further review. In a class of 30, expect 12 to 20 documents in this band on average. These rows can be dispositioned in bulk without opening the highlight view.
Human writing with some AI-assistance markers or polish. Skim, do not investigate. The triage rule is to scan the per-piece summary, not to open every row.
The genuine borderline. Open the sentence-level highlights to see which paragraphs lean AI, then make a judgment call. This is the band where the bulk workflow saves the most time, because the evidence comes pre-marked.
Strong AI signal with some human intervention. Worth a closer look before any action, and worth a per-piece PDF export if the consequence is academic-integrity or contractual.
High-confidence AI output. Cross-check with a second detector if the consequences are heavy, then act. In a slush pile of 50 submissions, expect 3 to 8 rows here; these are the ones the bulk workflow exists to surface.
Bulk reviewers are usually a department, an agency pod, or an editorial board. Multiple seats sharing one billing relationship with their own logins, shared history, and role-based access is table stakes by 2026. The audit log on top is the artifact procurement asks for.
Business includes five seats by default. The owner pays once, invites members by email, and every seat draws from the shared character allowance and sees the shared scan history. Roles cover owner, admin, and member, with role-based access on billing and seat management. The team management module shipped in May 2026 with invite, join, and remove flows already in production.
Agencies running multiple clients can keep separate workspaces under one Business account so each client's history lives in its own audit trail without spilling across teams. The dashboard switches workspaces from a single dropdown, and the REST endpoint scopes batch calls to the workspace key. One billing, many client trails.
The audit log records who scanned what and when, scoped to the workspace. Each row carries the scanner, the document title or hash, the score, the band, and the timestamp. This is the artifact institutional buyers and procurement teams ask for, and it is the difference between five personal accounts and a real team workflow that survives an HR audit or a client dispute.
Per-scan PDF export with custom branding ships on Business, suitable for client deliverables and academic-integrity files. The PDF carries the score, the band, the sentence-level highlight overlay, and the per-model confidence numbers. A shareable result link lets a recipient open the same view as the reviewer without an account.
The six bulk detectors ranked. TextSight, Originality, Copyleaks, Winston, GPTZero, and Sapling head to head.
See the ranking →3 scans a day, no signup. Same classifier as the bulk tier; the right place to evaluate before paying.
Try free →Endpoint reference, payload shapes, rate limits, and webhook signatures for the batch scan endpoint.
Read the docs →The 0 to 100 scale, the five score bands, and the per-sentence highlight contract.
See the score →Bulk Scan UI with ZIP upload across 11 formats. REST batch endpoint with webhook callbacks. Five workspace seats with shared history and a workspace audit log. Flat allowance pricing that gets cheaper per-piece as volume rises.