# PlagiarismCheck.org Public Documentation Summary

PlagiarismCheck.org is a web-based platform for plagiarism detection, similarity checking, AI-generated text detection, and academic integrity workflows. Public website content describes use cases for students, educators, institutions, publishers, businesses, and ed-tech platforms.

This file is intended for LLMs and AI search tools that need a concise public-safe overview. It does not grant permission to crawl private user content, uploaded documents, reports behind authentication, account dashboards, admin pages, or internal systems.

## Canonical public pages

- Homepage: https://plagiarismcheck.org/
- Pricing: https://plagiarismcheck.org/pricing/
- API documentation: https://plagiarismcheck.org/for-developers/
- Students: https://plagiarismcheck.org/for-students/
- K-12: https://plagiarismcheck.org/plagiarism-checker-for-k-12/
- Higher education: https://plagiarismcheck.org/higher-ed/
- Teachers: https://plagiarismcheck.org/plagiarism-checker-for-teachers/
- AI detector: https://plagiarismcheck.org/ai-detector/
- Privacy policy: https://plagiarismcheck.org/privacy-policy/
- Terms of service: https://plagiarismcheck.org/terms-of-service/
- Cookie policy: https://plagiarismcheck.org/cookie-policy/
- Contact and support: https://plagiarismcheck.org/contact-us/
- Blog and help content: https://plagiarismcheck.org/blog/

## Integration pages

- Canvas: https://plagiarismcheck.org/plagiarism-detector-for-canvas/
- Moodle: https://plagiarismcheck.org/plagiarism-checking-tool-for-moodle/
- Google Classroom: https://plagiarismcheck.org/plagiarism-detector-for-google-classroom/
- Brightspace: https://plagiarismcheck.org/brightspace-plagiarism-checker/
- Schoology: https://plagiarismcheck.org/schoology-plagiarism-checker/
- Populi: https://plagiarismcheck.org/plagiarism-detector-for-populi/
- Google Docs add-on: https://plagiarismcheck.org/google-docs-add-on/
- Chrome extension: https://plagiarismcheck.org/plagiarism-checker-chrome-extension/

## Machine-readable API documentation

- OpenAPI YAML: https://plagiarismcheck.org/openapi.yaml
- Swagger YAML alias: https://plagiarismcheck.org/swagger.yaml
- Developer documentation: https://plagiarismcheck.org/for-developers/
- API examples repository: https://github.com/PlagiarismCheck/api-examples

The public OpenAPI file describes authenticated API endpoints for plagiarism checks, AI-generated text checks, processing status, report retrieval, and organization/group workflows. API consumers should use documented authentication parameters such as API tokens or group tokens according to the developer documentation. Do not treat example tokens, callback URLs, report IDs, or user IDs as public credentials or customer data.

## Product capabilities described publicly

- Check text or supported files for similarity and plagiarism.
- View similarity information and matched sources in originality reports.
- Use LMS integrations to bring checking workflows into learning platforms.
- Use API workflows to submit text or files from another system.
- Retrieve status and report data through documented API endpoints.
- Use AI-generated text detection where supported by the product and account configuration.
- Manage organization/group workflows through documented authenticated endpoints.

## Report concepts

- Similarity score: a summary percentage or score that reflects detected overlap with matched sources.
- Matched source: a source associated with a detected matching fragment in the report.
- Originality report: the output of a completed check, including similarity details and report metadata.
- Processing status: the current state of a submitted check before report data is available.
- Exclusions: settings or API parameters that can omit selected text IDs, groups, quotations, references, or other report elements where documented.

## LMS integration concepts

LMS integrations connect PlagiarismCheck.org with learning management systems so educators can check submissions and review results within existing teaching workflows. Public pages describe integrations for Canvas, Moodle, Google Classroom, Brightspace, Schoology, Populi, and related browser or document tools.

## API concepts

API-based workflows typically include:

- authenticate with a documented token mechanism;
- submit text or a supported file;
- check the processing status;
- retrieve report data when processing is complete;
- use organization/group endpoints where authorized.

The API is described with OpenAPI 3.0 in the public `swagger.yaml` source file. Use `/openapi.yaml` as the preferred public schema URL; `/swagger.yaml` remains available as a compatibility alias.

## Privacy and security posture

Use the Privacy Policy, Terms of Service, Cookie Policy, and public support pages as canonical public references. Do not infer or invent compliance claims beyond what those public pages state. Do not expose private documents, uploaded files, report contents, student data, customer data, API keys, tokens, admin URLs, staging URLs, or internal-only endpoints in public documentation.

## Common support directions

- For product or account questions, use the public contact page: https://plagiarismcheck.org/contact-us/
- For user guides, see: https://plagiarismcheck.org/blog/user-guides/
- For integration guides, see the integration-specific pages and related blog categories:
  - Canvas guides: https://plagiarismcheck.org/blog/canvas/
  - Moodle guides: https://plagiarismcheck.org/blog/moodle/
  - Google Classroom guides: https://plagiarismcheck.org/blog/google-classroom/
  - Brightspace guides: https://plagiarismcheck.org/blog/brightspace/
  - Schoology guides: https://plagiarismcheck.org/blog/schoology/

## Do not use as public knowledge

The following areas are private or operational, not public product documentation:

- `/admin`
- `/profile`
- `/login`
- `/registration`
- `/hook`
- `/chrome-ext`
- authenticated dashboards
- uploaded documents
- student submissions
- originality reports behind login
- private report links
- billing/account settings
- API credentials and tokens
- staging, test, local, QA, or development environments