TurnitPass
PricingAPIBlog
Sign inDashboardStart free

TurnitPass

Docs

Platform

GeneralAPI KeysUsageBillingNotifications

Docs

OverviewQuickstartAuthenticationAPI ReferenceChangelog

Endpoints

POST/humanizePOST/paraphrasePOST/detectGET/status
Workspace

Manage billing, word balance, API keys, and subscription from one place.

Create a key
Docs menuUsage
GeneralAPI KeysUsageBillingNotificationsOverviewQuickstartAuthenticationAPI ReferenceChangelog
DeveloperKeys, usage, and billing

Usage

Track requests, words, endpoints, and remaining balance

TurnitPass usage is metered around the same writing workflow users see in the browser: transform text, detect signals, format citations, and keep account balance visible.

Developer workspace

Platform overview

Open usage

Review workspace activity

See recent requests, word usage, subscription state, and API key activity from the workspace.

API reference

Design against response fields

Use the documented usage fields instead of guessing balance behavior from the UI.

workspace
POST/api/v1/humanize
account scoped
usage-aware call
POST /api/v1/humanize
curl -X POST https://turnitpass.com/api/v1/humanize \
  -H "Authorization: Bearer tp_live_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{"text":"Paste your draft here","language":"en"}'

Words

Metering unit

GET /status

Status route

Recent activity

Workspace

review board

01

Metering unit

Transform requests spend word balance after a successful response.

02

Status route

Clients can check remaining balance and request limits before sending work.

03

Workspace

The workspace summarizes endpoint activity, subscription state, and key usage.

Private by default

Workspace actions require a signed-in account.

Metering flow

How a request becomes usage

1

Validate input

Requests fail early for missing text, unsupported payloads, word limits, or invalid keys.

2

Run the workflow

Humanizer, paraphrase, rewrite, detector, citation, and bibliography routes return structured JSON.

3

Record activity

Successful authenticated calls can be associated with endpoint, word count, status, and account owner.

4

Return remaining balance

Clients can show post-request state or poll /api/v1/status before the next batch.

Usage model

Limits clients should design around

Transform input
1,000 words/requestHumanize, paraphrase, and rewrite share the transform limit.
Detector input
5,000 words/requestDetector scans can review longer text and document extracts.
Citation routes
Rate limitedCitation and bibliography calls return exports but do not spend word credits.
Rate limit
Per keyDefault limits are keyed so production and staging traffic can be separated.
Implementation note. The workspace is the source of truth for account-level usage. API clients should use status responses for in-product balance checks.

Next step

Related docs and product surfaces

API Reference

Response fields, request limits, and endpoint contracts.

Workspace

View word balance, recent usage, API keys, and billing.

Live API routes

v1 endpoints are implemented for product calls.

Safe iteration

Keys, billing, and notifications point to account-owned surfaces.

Tool-first product

Developer pages stay connected to writer-facing workflows.

Get started

Humanize English, Simplified Chinese, and Traditional Chinese AI drafts, check AI-like signals, and keep writing workflows fast from one workspace.

Start freeAPI
TurnitPass

Humanize English, Simplified Chinese, and Traditional Chinese AI drafts, check AI-like signals, and keep writing workflows fast from one workspace.

Products
  • Humanizer
  • AI Detector
  • AI Essay Checker
  • AI Detector for Teachers
  • API
  • Developers
  • Dashboard
Resources
  • Pricing
  • Blog
  • Compare
  • Changelog
  • About
  • Contact
Legal
  • Privacy Policy
  • Terms of Service

© 2026 TurnitPass. All rights reserved.

All systems normal