Docs menuUsage
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.
/api/v1/humanizecurl -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
Validate input
Requests fail early for missing text, unsupported payloads, word limits, or invalid keys.
Run the workflow
Humanizer, paraphrase, rewrite, detector, citation, and bibliography routes return structured JSON.
Record activity
Successful authenticated calls can be associated with endpoint, word count, status, and account owner.
Return remaining balance
Clients can show post-request state or poll /api/v1/status before the next batch.
Usage model