Plagiarisme - opsporing API: stuur teks neer, sê die verslag.

'n Handvol punte, draer' nuth, deursigtige kredietprysing. Gebou vir agentskappe, redaksionele pypleidings en LMS-dalade gereedskap.

Jou API-sleutel

Teken in om jou API-sleutel te kry. Sleutels kom met elke rekening; API-kontroles word in krediete aangeteken.

Meld op

Einde punt:

POST /api/v1/check/

Dien 'n teks vir tjek. Gee terug 202 met' n kontrole_id. Liggaam: JSON met 'n teks veld, opsionele goedebig.

curl -X POST https://plagiarism.free/api/v1/check/ \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text": "The text you want to check..."}'

GET /api/v1/check/<check_id>/

Pos vir status; wanneer status is klaar die volledige raporteer is ingesluit: telling, per-enteniteit ooreenstem tipes met vertroue en bron uittreksels, en die bronlys.

curl https://plagiarism.free/api/v1/check/CHECK_ID/ \
  -H "Authorization: Bearer YOUR_KEY"

GET /api/v1/checks/

Lys jou onlangse tjeks, nuutste eerste. Opsionele navraag params: beperk (1-100, verstek 20) en status (gekies, gedoen, gevaal...). Reconcile onderdanigheids en terug jou eie paneelbord sonder om elke kontrole_id te stoor.

curl "https://plagiarism.free/api/v1/checks/?limit=20&status=done" \
  -H "Authorization: Bearer YOUR_KEY"

Python-voorbeeld

import time
import requests

API = "https://plagiarism.free/api/v1/check/"
HEADERS = {"Authorization": "Bearer YOUR_KEY"}

r = requests.post(API, json={"text": open("essay.txt").read()}, headers=HEADERS)
check_id = r.json()["check_id"]

while True:
    report = requests.get(f"{API}{check_id}/", headers=HEADERS).json()
    if report["status"] in ("done", "failed"):
        break
    time.sleep(3)

print(report["score_pct"], "% matched")
for source in report["sources"]:
    print(source["pct_of_document"], source["url"])

JavaScript voorbeeld

const API = "https://plagiarism.free/api/v1/check/";
const headers = { "Authorization": "Bearer YOUR_KEY", "Content-Type": "application/json" };

const { check_id } = await fetch(API, {
  method: "POST", headers, body: JSON.stringify({ text })
}).then(r => r.json());

let report;
do {
  await new Promise(res => setTimeout(res, 3000));
  report = await fetch(`${API}${check_id}/`, { headers }).then(r => r.json());
} while (!["done", "failed"].includes(report.status));

Comment

Identies na die terrein: 1 krediet = 1000 woorde gecardineer, gerond per tjek; diep tjeks kos dubbel. Krediet pakkies is geldige 365 dae; intekeninge hervulling maandelikse en sluit die API op elke vlak in. Geen aparte API-vlak, geen per-eetgelde nie. Sien planne en pakkies

Tjeks loop asynchronous (ware, tempo-limited web onttrekal neem 20-45 sekondes) - stem eerder die statuspunt uit as om die verbinding oop te hou. HTTP 402 beteken onvoldoende krediete; die reaksie sluit in wat die tjek sou kos.

Dikwels gevra vrae

Two endpoints. POST /api/v1/check/ with your text returns a check_id; GET /api/v1/check/check_id/ returns status while the check runs and the full report JSON (score, matched sentences, sources) when done. Auth is a Bearer key from your account page. Code samples in curl, Python and JavaScript are below.

The same transparent unit as the site: 1 credit per 1,000 words scanned, rounded up per check. Credit packs start at $4.99 for 30 credits and are valid a full year; the $7.99/month Starter plan includes 60 credits and API access. No per-seat fees, no separate API pricing tier.

A check takes roughly 20-45 seconds because it performs real, rate-limited web retrieval and page comparison - the API is asynchronous for that reason. Submissions queue fairly; paid checks get priority. Poll the status endpoint every few seconds rather than holding the connection open.

Everything the web report shows: overall matched percentage, per-sentence match type (exact / near / none) with confidence, the matched source excerpt for each flagged sentence, and the source list with URLs and per-source match percentages. Enough to render your own report UI or gate a workflow.

Yes - that is what it is for: LMS-adjacent tools, editorial workflows, agency content pipelines. Volume is metered purely by credits, and the per-check word cap is 25000 words. If you need sustained high volume, contact us and we will provision for it rather than let queues degrade.