開発者API
自然化、検出、引用の流れを自社プロダクトに組み込めます。
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 · ブログ
製品、支払い、提携について相談できます。
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.