开放 API
将改写、检测与引用能力接入自有系统。
API 平台
写作改写与 AIGC 检测 API
把 TurnitPass 接入写作工具、内容平台、浏览器插件或内部编辑系统，通过 Bearer API 密钥调用。
7
v1 endpoints
1k
transform words
5k
detector words
5
active keys
API command center
v1 routes, metering, and key status
01
Authenticate
Bearer key
02
Transform
Humanize draft
03
Review
AI signals
04
Return
JSON + usage
first call
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"}'
Detector-aware API
Ship the same review loop users see in the app.
The 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
Turnitin-styleAcademic submission reviewGPTZeroRhythm and probability signalsOriginality.aiPublishing review patternsQuillBotParaphrase-heavy passagesCNKIChinese academic workflowWanfangLocal review contextCQVIPWeipu-style checking
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 + billing
工具
改写润色 · 学术改写 · 论文检测
语言
降低 AI 痕迹，写出自然好内容。中英文改写、检测、润色与引用，一站完成。
账户中心
将改写、检测与引用能力接入自有系统。
免费开始
会员价格 · 开放 API · 博客
资源
降低 AI 痕迹，写出自然好内容。中英文改写、检测、润色与引用，一站完成。
Core endpoints
One API surface for the writing workflow.
The public API mirrors the product: lower AI-like phrasing, run AI Detector scans, rewrite passages, and keep citation work in the same account.
POST
/api/v1/humanizeHumanize text
Lower AI-like phrasing while preserving meaning, names, citations, and structure.
POST
/api/v1/paraphraseParaphrase & polish
Rewrite in standard, fluency, formal, academic, simple, creative, expand, or shorten modes.
POST
/api/v1/rewriteAcademic rewrite
Use the focused academic polish workflow for cleaner structure and sentence flow.
POST
/api/v1/detectAI detector
Return review estimates, writing signals, source notes, and revision guidance.
POST
/api/v1/citationCitation format
Format DOI, URL, web, book, journal, and manual source metadata.
POST
/api/v1/bibliographyBibliography
Sort and format citation lists with HTML, text, BibTeX, and RIS output.
GET
/api/v1/statusKey status
Check key name, word balance, request limits, created time, and last use.
Create key
Generate a workspace API key and copy it once.
Send request
Call /api/v1 endpoints with a Bearer token and JSON payload.
Track usage
Requests are logged with words, endpoint, status, and owner.
Control billing
Plan limits, checkout, portal routing, and webhooks keep usage and subscriptions in sync.
Request lifecycle
Built for keys, limits, and usage review.
The platform is built around account-owned keys, metered calls, and workspace review, so usage stays visible from the first request.
API billing
Meter usage like a product surface, not a black box.
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.
Workspace balanceStatus endpointUsage ledgerPlan-aware billing
01
Shared word balance
Account-owned
Writing endpoints share the account word balance. Detection uses a separate daily scan allowance shared with the website.
02
Failed request behavior
No output, no charge
Auth errors, validation errors, insufficient balance, and processing failures return JSON errors before credits are consumed.
03
Volume path
Pro and Business
Use the workspace for API keys and plan status, then contact support for higher limits, partner traffic, or volume review.
Frequently asked
Developer questions before the first deploy.
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.
01How does API billing work?
API calls use the word balance attached to the workspace owner. Successful humanize, paraphrase and rewrite requests deduct input word credits. AI detection uses daily scans, with no word-credit charge; citation and bibliography generation are free.
02When are words deducted?
Words are deducted after the endpoint returns a successful processed result. Invalid API keys, malformed bodies, rate-limit errors, insufficient balance, and processing errors do not consume the requested words.
03How many keys can a workspace create?
The v1 workspace supports up to five active API keys, so production, staging, partner, and internal automations can be separated and revoked independently.
04Which languages does the API process?
The writing logic is designed around English, Simplified Chinese, and Traditional Chinese processing. The API accepts a language field so clients can keep processing behavior explicit.
05What should developers build first?
Start with /api/v1/status to verify the key and balance, then send a small /humanize or /detect request before wiring larger editor, LMS, extension, or CMS workflows.
Developer docs
Open workspace