Document AI score
ai_percentage reports how much of the input is covered by AI-labeled sentences, so you can sort a queue, set a threshold or trigger a second review on one field.
AI Detector API
Add AI content detection to your own product. Send text to one REST endpoint and get back a document score with sentence-level evidence as JSON, built on the detection models behind detecting-ai.com.
Plans from $15 a month for 100,000 words. No SDK to install: any language that can send HTTPS works.
Illustration of the AI Detector API: a document goes in, and a JSON response with a 61 percent AI score and labeled sentences comes back
What you get back
The response is designed for products, not screenshots. One number for sorting and thresholds, plus the sentence-level detail that lets your interface show users why.
ai_percentage reports how much of the input is covered by AI-labeled sentences, so you can sort a queue, set a threshold or trigger a second review on one field.
Every analyzed sentence comes back with character offsets, an AI or Human label and a confidence score from 0 to 1. Highlight the exact passages inside your own editor or report.
Designed to review text from ChatGPT and GPT-5, Claude, Gemini and mixed human-edited drafts, and retested as new models ship.
A feature-based classifier and a fine-tuned transformer are calibrated into one score, keeping wrong flags on human writing under 1% in Detecting AI's published benchmarks.
Use cases
Any product that accepts writing it did not watch being written. The API supplies the signal and the evidence; your workflow keeps the judgment.
Score assignment submissions as they arrive and show the sentence evidence next to drafts, revision history and the institution's own policy.
Moodle plugin or direct REST integration
Check delivered articles, product descriptions and translations before they reach the client, and route unusual cases to a human editor.
Flag deliveries above a threshold for review
Add an authorship signal to contributor intake so editors read the flagged passages first instead of rereading every submission.
Highlight passages inside the CMS
Run every deliverable through one QA step before it is published, and keep the processed word count for each client report.
Batch-check drafts from the server
Review essays, cover letters and written assessments at scale, with the score opening a conversation rather than closing one.
Sort applications by review priority
Triage reviews, comments and generated spam at volume, then send the uncertain middle to moderators together with the highlighted sentences.
Moderation queue with sentence context
How it works
The integration is one HTTPS request. The full reference, including authentication, errors and retries, lives in the API documentation.
Prepare an API key in the dashboard and store it in a server-side secret. The subscription supplies the word balance; the key only identifies your account.
Send UTF-8 text with the detector version to api.detecting-ai.com. Usage is counted from the input words, and an Idempotency-Key makes retries safe.
Map ai_percentage to a verdict band and use the chunk offsets to highlight sentences in your own interface. Keep a person on consequential decisions.
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"
}'{
"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
}
}Authentication, error codes, safe retries and the MCP server are documented on one page.
Read the full API referenceBuilt for production
The contract is small on purpose. The details below are the ones that matter once the integration runs inside a real review queue.
Send an Idempotency-Key with every request. An exact replay within 24 hours returns the stored result without running the detector or charging the words again.
Usage is counted from whitespace-separated input words, up to 160,000 characters per request. Every response reports the words processed.
Pin v3 in the request body so results stay reproducible as the detector improves. v1 and v2 remain available for existing integrations.
Call the API from your backend, an edge function or a worker. Keys are shown once, can be replaced without interrupting the active key, and never need to reach a browser.
Detection engine
Detecting AI pairs a feature-based classifier with a fine-tuned transformer and calibrates the two into one score. The engine has been tested on more than a billion human-written and AI-generated samples, and it is retested as new models ship.
Read the methodologyEligible sentences are scored independently and labeled, so the document signal is explainable passage by passage.
How much AI text gets caught and how often human writing is wrongly flagged are both tracked, which keeps the false positive rate under 1%.
Short, translated, heavily edited or formulaic text carries more uncertainty. The evidence is returned so a person can check the call.
Three ways to integrate
One subscription and one word balance, reachable from your backend, from an AI assistant or from an automation tool.
A JSON endpoint for any backend, edge function or batch job. Pin the detector version and store the processed word count.
Open the API docsGive Claude, ChatGPT, Codex or any MCP client the detect_ai_text tool so an assistant can check text mid-conversation.
See the MCP serverAdd a detection step to a no-code workflow and pass the result to a human review step when the decision matters.
View the Zapier appPricing
Start with the detector alone or combine all three APIs under one key. Checkout rechecks the live price and allowance before payment opens.
$15per month
100,000 detector words
$35per month
100,000 words for each included API
An API key is free to create. Requests need an active subscription and remaining words.
API FAQ
Straight answers about accuracy, output, pricing and limits, so the first request behaves the way you expect.
An AI detector API is a web service that analyzes text for patterns associated with AI writing and returns the result as data instead of a web page. The Detecting AI endpoint accepts a JSON body with the text and a detector version, then responds with a document-level ai_percentage, sentence-level chunks with labels and confidence scores, and the number of words processed.
Detecting AI's detection models detect AI-generated text with 99% accuracy across diverse datasets and keep the false positive rate under 1%. Long, unedited samples are the easiest case. Short, heavily edited or translated passages carry more uncertainty, which is why every response includes the sentences behind the score.
It is designed to review text from the GPT family including ChatGPT and GPT-5, Claude, Gemini and mixed human-edited drafts. It does not attribute text to one specific generator with certainty.
The AI Detector API plan costs $15 per month and includes 100,000 detector words. The $35 API Bundle adds the AI Humanizer and Plagiarism Checker APIs with 100,000 words for each. Checkout verifies the live price and allowance before opening payment.
Creating an API key is free, but requests need an active subscription and remaining word balance. To evaluate detection quality before subscribing, use the free AI detector on detecting-ai.com, which shows the same kind of sentence-level evidence.
Yes. Detector v3 returns a chunk for each analyzed sentence with startChar and endChar offsets, an AI or Human label and a confidence score from 0 to 1. Scores above 0.5 receive the AI label. ai_percentage is the percentage of input characters covered by AI-labeled sentences, which differs from the averaged document score shown by the website detector.
No. A private API key must never be shipped in browser code, a mobile binary or a public repository. Send requests from your server, an edge function or a worker and return only the result your interface needs.
No. AI detection is a probabilistic review signal, not proof of authorship or misconduct. Use the score and the highlighted sentences to focus a review, then consider drafts, sources, writing history and context before any consequential decision.
Response time depends on text length. One measured sample on 2026-10-08, a 305-word English text on the public web detector including browser overhead, completed in 2.75 seconds. That is a single observation, not a guarantee, so measure with your own representative documents and keep the Idempotency-Key so a timed-out request can be retried without a second charge.
No. The API is hosted at api.detecting-ai.com and there is no self-hosted package, container or model download. Your server sends text over HTTPS and receives JSON; nothing needs to be installed beyond an HTTP client.
Yes. The same subscription powers the detect_ai_text tool on the remote MCP server for Claude, ChatGPT, Codex and other MCP clients, and the Detecting AI app on Zapier. MCP and Zapier usage draws from the same detector word balance as the REST API.
Start building
Create a key, send one representative sample with Detector v3 and inspect the full JSON before designing the workflow around it.