AI Detector API and MCP documentation

Access

Authentication

REST requests and local MCP clients use customer API keys in different headers. Hosted MCP connectors discover OAuth and open a browser authorization flow.

Usage safety

Retry one request without paying twice

New integrations should send a unique Idempotency-Key for every logical REST request and keep that value until the request succeeds or you abandon it. If a connection drops, retry the exact same endpoint, text, version or model, and key. An exact replay returns the stored response without running the provider or deducting the words again.

While the first caller still owns the provider lease, an exact concurrent retry returns HTTP 409 with Retry-After. After completion, the exact response remains replayable for 24 hours. Once that private body expires, the same key returns HTTP 410. Its permanent tombstone still prevents a second charge.

REST endpoint

AI Detector API

Analyze supplied text for patterns associated with AI writing. Results are probabilistic review signals, not proof of authorship.

Request body

curl --request POST \
  --url https://api.detecting-ai.com/api/detect/ \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: detector-review-001" \
  --header "X-API-Key: YOUR_API_KEY" \
  --data '{
    "text": "Paste the text you want to analyze.",
    "version": "v3"
  }'

Response

{
  "success": true,
  "data": {
    "details": {
      "chunks": [
        {
          "text": "A sentence from the input.",
          "startChar": 0,
          "endChar": 26,
          "type": "AI",
          "score": 0.87
        }
      ],
      "ai_percentage": 42.5
    },
    "version": "v3",
    "words_processed": 120
  }
}

Read the AI Detector API overview

REST endpoint

AI Humanizer API

Rewrite supplied text with a selected humanizer model. The output is editable and should be reviewed for meaning, facts, names, links, tone, and required terminology.

Request body

curl --request POST \
  --url https://api.detecting-ai.com/api/humanize/ \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: humanizer-review-001" \
  --header "X-API-Key: YOUR_API_KEY" \
  --data '{
    "text": "Paste the text you want to rewrite.",
    "model": "cognia"
  }'

Response

{
  "humanized_text": "The rewritten text is returned here.",
  "words_processed": 120,
  "model_used": "cognia"
}

Read the AI Humanizer API overview

REST endpoint

Plagiarism Checker API

Search for sentence-level overlap and return source context when a match is found. A match needs human review because quotation, citation, permission, and standard phrasing affect what it means.

Request body

curl --request POST \
  --url https://api.detecting-ai.com/api/plagiarism/ \
  --header "Content-Type: application/json" \
  --header "Idempotency-Key: plagiarism-review-001" \
  --header "X-API-Key: YOUR_API_KEY" \
  --data '{
    "text": "Paste the text you want to check."
  }'

Response

{
  "result": {
    "results": [
      {
        "sentence": "A sentence from the input.",
        "is_plagiarised": true,
        "web_sentence": "A similar source sentence.",
        "similarity": 91.0,
        "link": "https://example.com/source"
      }
    ],
    "plagiarism_score": 34.2
  },
  "words_processed": 120
}

Read the Plagiarism Checker API overview

Streamable HTTP

Remote MCP server

One remote server exposes exactly two tools: detect_ai_text and humanize_text. Plagiarism checking is available through REST, not MCP.

Hosted connectors

Add only the MCP URL in a hosted connector. The client discovers OAuth, opens sign-in and consent in the browser, and stores its own tokens. Do not append an API key or other credential to the URL.

Codex

export DETECTING_AI_API_KEY="YOUR_API_KEY"

[mcp_servers.detecting_ai]
url = "https://api.detecting-ai.com/api/mcp"
bearer_token_env_var = "DETECTING_AI_API_KEY"
tool_timeout_sec = 300

Claude Code

claude mcp add --transport http --scope user \
  --header "Authorization: Bearer YOUR_API_KEY" \
  detecting-ai https://api.detecting-ai.com/api/mcp

Failure handling

Errors

Check both the HTTP status and response body. Error payloads are not yet normalized into one universal schema.

Quotas and boundaries

Usage and limits

Usage is charged from the whitespace-separated input word count. Detector, humanizer, and plagiarism balances are feature-specific, including when the same key accesses more than one product.

• Check remaining words and active plans in the API dashboard.
• MCP uses the same detector or humanizer balance as the matching REST API.
• REST and MCP have a default 160,000-character text limit. MCP also has a 1 MiB transport body limit. Split unusually large documents into meaningful sections.