API de detección de plaxio: enviar texto, consultar o informe.

Un puñado de puntos finais, autenticación do portador, prezos transparentes de crédito. Está feito para axencias, canles editoriais e ferramentas adxacentes a LMS.

A súa chave API

Acceda para obter a súa chave API. As chaves veñen con cada conta; as comprobacións da API facturanse en créditos.

Inscrición

Puntos finais

POST /api/v1/check/

Enviar un texto para comprobar. Devolve 202 cun check_ id. Corpo: JSON cun campo de texto, booleano profundo opcional.

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

Sondaxe para o estado; cando o estado está feito inclúese o informe completo: puntuación, tipos de coincidencia por frase con confianza e extractos de fontes, e a lista de fontes.

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

GET /api/v1/checks/

Lista as comprobacións recentes, a máis recente primeiro. Parámetros de consulta opcionais: límite (1- 100, por omisión 20) e estado (en fila, feito, fallado...). Reconcilie as entregas e respalde o seu propio panel sen gardar cada check_ id.

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

Exemplo en Python

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"])

Exemplo de JavaScript

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

Prezos

Idéntico ao sitio: 1 crédito = 1000 palabras escaneadas, redondeadas por comprobación; as comprobacións profundas custan o dobre. Os paquetes de créditos son válidos 365 días; as subscricións reenchéganse mensualmente e inclúen a API en todos os niveis. Non hai nivel de API separado, non hai taxas por sesión. Vexa plans e paquetes

As comprobacións executanse de xeito asincrónico (a obtención real da web limitada pola velocidade tarda 20- 45 segundos) - preguntar o punto final de estado no canto de manter a conexión aberta. HTTP 402 significa créditos insuficientes; a resposta inclúe o custo da comprobación.

Preguntas frecuentes

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.