API Docs: Scan and Rewrite

Auth

Send Authorization: Bearer <key>. Create one key per user in the account area when accounts are enabled.

curl -sS https://aitextwatermarkchecker.com/api/v1/scan \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"hello"}'

Scan

POST /api/v1/scan with body { "text": "..." }, max 100,000 characters. Returns findings and cleaned text using the same rules as the homepage tool.

1. Paste or send the text you want checked.
2. Call Scan (or press Scan in the browser).
3. Read the findings list, then use the cleaned text if you want those characters gone.

curl -sS https://aitextwatermarkchecker.com/api/v1/scan \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Hello\u200Bworld"}'

Rewrite

POST /api/v1/rewrite is reserved for paid wording changes. While Rewrite is off, the route returns that Rewrite is not available yet and does not call a model.

curl -sS https://aitextwatermarkchecker.com/api/v1/rewrite \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Hello world","keep_language":true}'

Errors

• 400 — text too long (over 100,000 characters).
• 401 — missing or invalid key (when auth is required).
• 402 — not enough rewrite balance.
• 429 — rate limited.
• 502 / 503 — model failure or rewrite off; failed rewrite does not charge words.