canonical: https://jentic.com/apis/plagiarismcheck.org/plagiarismcheck

# PlagiarismCheck API

PlagiarismCheck.org API for plagiarism detection, AI content detection (TraceGPT), and multi-user organization checks. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically submit text for plagiarism checking, check text status. Covers 9 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Submit text for plagiarism checking
- Check text status
- Get plagiarism report
- Organization text check
- Delete organization report

## Use cases

### Developer Tools Operations

Use the PlagiarismCheck API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including submit text for plagiarism checking, check text status, get plagiarism report.

Example prompt: Call POST `/api/v1/text` to submit text for plagiarism checking

### Automated AI Detection Management

Automate ai detection operations by combining multiple PlagiarismCheck API endpoints. Agents can check text status and then get plagiarism report in a single workflow.

Example prompt: Call GET `/api/v1/text/{id}` to check text status, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call PlagiarismCheck API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'submit text for plagiarism checking', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v1/text` | Submit text for plagiarism checking |
| GET | `/api/v1/text/{id}` | Check text status |
| GET | `/api/v1/text/report/{id}` | Get plagiarism report |
| POST | `/api/org/text/check` | Organization text check |
| POST | `/api/org/text/status/{id}` | Organization text status |
| POST | `/api/org/text/report/{id}` | Organization text report |
| POST | `/api/org/text/delete/{id}` | Delete organization report |
| POST | `/api/v1/chat-gpt` | Submit text for AI detection |

## Key resources

- **AI Detection** — Operations related to AI Detection
- **Organization** — Operations related to Organization
- **Plagiarism Check** — Operations related to Plagiarism Check

## Why Jentic

- **Setup:** Wiring PlagiarismCheck by hand means learning its X-API-TOKEN header auth and building the submit-and-poll plumbing across its personal and organization text-check endpoints yourself. Through Jentic you install once, import PlagiarismCheck from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** PlagiarismCheck puts the submission id in the URL path (`/api/v1/text/{id}`, `/api/org/text/report/{id}`), so a rule can pin your agent to one text submission: it can check status and fetch the report for that submission and nothing else. You choose the operations it may call, so destructive ones like deleting a submission are not included unless you add them.
- **Credential handling:** Your PlagiarismCheck token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'submit text for plagiarism checking' or 'get a plagiarism report', and Jentic returns the matching PlagiarismCheck operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the PlagiarismCheck API use?

The PlagiarismCheck API uses an API key passed in the `X-API-TOKEN` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I submit text for plagiarism checking with the PlagiarismCheck API?

Yes. Use the POST `/api/v1/text` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the PlagiarismCheck API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I submit text for plagiarism checking through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'submit text for plagiarism checking'. Jentic returns the matching PlagiarismCheck API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the PlagiarismCheck API have?

The PlagiarismCheck API exposes 9 endpoints covering ai detection, organization, plagiarism check operations.

### Can I limit what my agent is allowed to do with the PlagiarismCheck API?

Yes. Because you run Jentic One yourself and write the rules, you decide exactly which PlagiarismCheck operations the agent may call and which credentials it may use. Since the API carries the submission id in the URL path, such as GET `/api/v1/text/{id}` and POST `/api/org/text/report/{id}`, you can pin the agent to a single submission so it only checks status and fetches that report. Destructive operations like POST `/api/org/text/delete/{id}` stay off limits unless you explicitly allow them.