Use case · publishers, WordPress and CMS

Plagiarism and AI detection API for publishers and CMS workflows

Check guest posts, freelance drafts and agency copy before they go live. Call the API from WordPress or your CMS backend, and keep each matching source and flagged sentence with the draft for your editors.

  • 2,000 free API words, no card
  • Free sandbox keys
  • REST + JSON
Integration pattern

Check at review, not at publish

There is no official plugin: you add the check to your own CMS code with a few REST calls.

  1. A draft is ready for review

    When a writer submits a draft (for example, status “pending review”), your server picks it up.

  2. Send the text

    Strip the HTML and POST the plain text to /scans with plagiarism, AI detection or both. Save the scan ID with the draft.

  3. Poll in the background

    A scheduled job polls GET /scans/{id} until it is completed, usually in 30–90 seconds, and saves the result with the draft.

  4. The editor decides

    Show the score, each matching source and the flagged sentences next to the draft. The editor approves, edits or asks the writer.

WordPress example

A sketch for your own plugin

Standard WordPress functions only: a hook on status change, wp_remote_request and WP-Cron for polling. Shortened; add your own error handling and editor UI.

Submit on “pending review”, poll with WP-Cron, save to post meta
<?php
// Sketch for your own WordPress plugin. There is no official plugin.
// Store the key in wp-config.php: define('PCP_API_KEY', 'pcp_test_…');
const PCP_API = 'https://app.plagiarismcheckerplus.com/api/public/v1';

function pcp_request($method, $path, $body = null) {
    $args = [
        'method'  => $method,
        'timeout' => 20,
        'headers' => [
            'Authorization' => 'Bearer ' . PCP_API_KEY,
            'Content-Type'  => 'application/json',
        ],
    ];
    if ($body !== null) $args['body'] = wp_json_encode($body);
    $res = wp_remote_request(PCP_API . $path, $args);
    return is_wp_error($res) ? null : json_decode(wp_remote_retrieve_body($res), true);
}

// 1. When a post moves to "pending", submit its text.
add_action('transition_post_status', function ($new, $old, $post) {
    if ($new !== 'pending' || $old === 'pending') return;
    $text = wp_strip_all_tags($post->post_content);
    if (str_word_count($text) < 50) return; // AI detection needs 50 words
    $scan = pcp_request('POST', '/scans', [
        'text'  => $text,
        'tools' => ['plagiarism', 'ai_detect'],
        'name'  => 'post-' . $post->ID,
    ]);
    if (!empty($scan['id'])) {
        update_post_meta($post->ID, '_pcp_scan_id', $scan['id']);
        wp_schedule_single_event(time() + 60, 'pcp_poll_scan', [$post->ID]);
    }
}, 10, 3);

// 2. Poll later (WP-Cron) and keep the result with the post.
add_action('pcp_poll_scan', function ($post_id) {
    $id   = get_post_meta($post_id, '_pcp_scan_id', true);
    $scan = $id ? pcp_request('GET', '/scans/' . rawurlencode($id)) : null;
    if (!$scan) return;
    if (in_array($scan['status'], ['pending', 'processing'], true)) {
        wp_schedule_single_event(time() + 60, 'pcp_poll_scan', [$post_id]);
        return;
    }
    update_post_meta($post_id, '_pcp_result', $scan); // show it in an editor meta box
});

Not on WordPress? The same flow works from any backend; see the curl, Node.js and Python examples on the plagiarism checker API page, or the open-source PHP client on the developer hub.

In practice

What to handle in a publishing workflow

Both checks in one request

Send "tools": ["plagiarism", "ai_detect"] and one scan returns matching sources and flagged sentences. Each tool uses the full word count.

Send plain text

Strip HTML, shortcodes and embeds first. Plagiarism needs 30 words and AI detection 50; shorter text returns 400 text_too_short and costs nothing.

Re-check after big edits

Each check uses words, so check when a draft is submitted for review, and again only after substantial changes, not on every autosave.

Rate limits

60 requests a minute per key on paid plans, 10 on the free trial. On 429, wait for Retry-After. Use a separate key per site, up to 10.

Build on a test key

A pcp_test_ key returns sample results at no cost, in the same shape as a real scan, so you can build the editor view first.

Keep the key server-side

Call the API from PHP or your backend, never from the block editor’s JavaScript or a public page.
No detector is perfect
A plagiarism score shows matching text, not intent: quotes, attributions and common phrases match too. An AI score is a likelihood, not proof. Give editors the evidence and let them decide.
FAQ

Plagiarism API for publishers: questions

Our REST API works from WordPress, but there is no official Plagiarism Checker Plus WordPress plugin. A small plugin of your own can send a post’s text to the API when it is submitted for review, poll for the result with WP-Cron, and show it in the editor. The sketch on this page shows the pattern.

Build it on a free key

2,000 free API words and free test keys, no card, then pay as you go from $4.50 (50,000 words), or choose an API plan from $25 a month (API pricing). Checking by hand instead? See the plagiarism checker for content writers, the Google Docs add-on or the Chrome extension.

WordPress is a trademark of the WordPress Foundation, named only to describe a custom integration; we offer no WordPress plugin. Use of the API is subject to our Terms of Service and Privacy Policy.