Plagioa detektatzeko APIa: testua bidali, txostena galdekatu.

Amaierako puntu ugari, erabiltzailearen autentifikazioa, kreditu-prezio gardenak. Agentzientzat, editore-kanaletarako eta LMS-ren inguruko tresnetarako eraikia.

Zure API gakoa

Saioa hasi API gakoa lortzeko. Gakoak kontu guztietan daude; API egiaztapenak kredituetan fakturatzen dira.

Izena eman

Amaierako puntuak

POST /api/v1/check/

Bidali testu bat egiaztatzeko. 202 itzultzen du check_id batekin. Gorputza: JSON testu-eremu batekin, boolear sakoneko aukerakoa.

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>/

Estatistika-metodoen bidez, datuen sailkapena egiten da: datu-multzoa, datu-multzo

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

GET /api/v1/checks/

Zerrendatu azken egiaztapenak, berrienak lehenik. Aukerazko kontsulta-parametroak: muga (1-100, lehenetsia 20) eta egoera (ilaran, eginda, huts eginda...). Konponketa-bidalketak eta zure dashboard-aren babeskopia check_id guztiak gorde gabe.

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

Python adibidea

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 adibidea

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));

Prezioa

Gunearen berdina: kreditu 1 = 1.000 hitz eskaneatu, egiaztapen bakoitzeko gora biribilduta; egiaztapen sakonetarako kostua bikoitza da. Kreditu-paketek 365 egun balio dute; harpidetzak hilean behin berritzen dira eta API maila guztietan barne hartzen dute. Ez dago API maila bereizirik, ez dago eserleku bakoitzeko kosturik. Ikusi planak eta paketeak

Egiaztapenak asinkrono exekutatzen dira (web-erabiltzaileek 20-45 segundo behar dituzte web-erabiltzaileen datu-basea eskuratzeko) - egoeraren amaierako puntua galdetu konexioa irekita mantentzearen ordez. HTTP 402-k kreditu nahikoak ez daudela esan nahi du; erantzunak egiaztapenaren kostua barne hartzen du.

Maiz egiten diren galderak

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.