開發者 API
將自然化改寫、AI 檢測及文獻引用能力無縫接入您的應用與學術工作流。
把 TurnitPass 接入寫作工具、內容平台、瀏覽器外掛和內部編輯系統。
7
v1 endpoints
1k
transform words
5k
detector words
5
active keys
API command center
v1 routes, metering, and key status
Authenticate
Bearer key
Transform
Humanize draft
Review
AI signals
Return
JSON + usage
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"}'response shape
typed JSONThe API is not a single text rewrite endpoint. It exposes the practical workflow: transform a draft, scan AI-like signals, keep source metadata, and route users toward the next revision.
Preflight matrix
Ready response
JSON
Score, warnings, sentence-level signals, usage, and route metadata.
OUTPUT
Result + usage metadata
RATE MODEL
Per key, workspace-owned
BILLING
Plan limits + Stripe-ready
將自然化改寫、AI 檢測及文獻引用能力無縫接入您的應用與學術工作流。
智能潤色 · 學術改寫 · 論文 AI 率檢測
支援英文、簡體與繁體中文，一站式提供自然化改寫、AI 檢測、智能潤色與文獻引用服務。
將自然化改寫、AI 檢測及文獻引用能力無縫接入您的應用與學術工作流。
價格 · API · 部落格
支援英文、簡體與繁體中文，一站式提供自然化改寫、AI 檢測、智能潤色與文獻引用服務。
The public API mirrors the product: lower AI-like phrasing, run AI Detector scans, rewrite passages, and keep citation work in the same account.
/api/v1/humanizeLower AI-like phrasing while preserving meaning, names, citations, and structure.
/api/v1/paraphraseRewrite in standard, fluency, formal, academic, simple, creative, expand, or shorten modes.
/api/v1/rewriteUse the focused academic polish workflow for cleaner structure and sentence flow.
/api/v1/detectReturn review estimates, writing signals, source notes, and revision guidance.
/api/v1/citationFormat DOI, URL, web, book, journal, and manual source metadata.
/api/v1/bibliographySort and format citation lists with HTML, text, BibTeX, and RIS output.
/api/v1/statusCheck key name, word balance, request limits, created time, and last use.
Generate a workspace API key and copy it once.
Call /api/v1 endpoints with a Bearer token and JSON payload.
Requests are logged with words, endpoint, status, and owner.
Plan limits, checkout, portal routing, and webhooks are ready for live Stripe keys.
The Stripe and Google secrets stay configurable, but the product surface is already shaped around account-owned keys, metered calls, and workspace review.
Every API call stays tied to a workspace, key, endpoint, status code, and word count. That gives teams a clear path from first test request to production usage review.
Shared word balance
Transform and detector endpoints deduct words from the same workspace balance after a successful result.
Failed request behavior
Auth errors, validation errors, insufficient balance, and processing failures return JSON errors before credits are consumed.
Volume path
Use the workspace for API keys and plan status, then contact support for higher limits, partner traffic, or volume review.
The API follows the same product boundary as the app: account-owned keys, explicit language handling, clear limits, and response metadata that clients can show back to users.