Browse documentation

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.

REST API v1

Your 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

1curl -X POST https://turnitpass.com/api/v1/humanize \
2  -H "Authorization: Bearer tp_live_your_api_key" \
3  -H "Content-Type: application/json" \
4  -d '{"text":"Paste your draft here","language":"en"}'

Review board

Metering unit

Transform requests spend word balance after a successful response.

Status route

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

Workspace

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

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

Limits clients should design around

Transform input

500 / 2,000 quality unitsHumanize/rewrite: 500 units; paraphrase: 2,000. One CJK character or three other characters per quality unit. All plans use the same limits.

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, make it part of your workflow.Continue reading