canonical: https://jentic.com/apis/educhecker.io/educhecker # EduChecker The EduChecker API detects diploma and academic-credential fraud using machine-learning models. Agents create a check on an uploaded document, poll its status, and retrieve a heatmap that highlights suspected tampering, or run a quick AI authenticity check without persisting the document. Institution-based verification requests can be submitted against a country's issuing bodies, and results exported once complete. Authentication uses a bearer token, and the API also covers billing, credits, accounts, and notifications around the verification workflow. ## For AI agents Run ML-based diploma fraud detection: create a check on a document, read its status and tampering heatmap, or run a quick AI authenticity check. Covers 94 operations across checks, verification requests, and billing. ## Scope Does not handle background checks, employment history, or identity-document issuance. Use for diploma and academic-credential fraud detection only. ## Capabilities - Create a check that runs ML fraud detection on an uploaded diploma - Retrieve a check's status and a heatmap highlighting suspected tampering - Run a quick AI authenticity check without persisting the document - Submit institution-based verification requests against a country's issuing bodies - Export a check's data and retrieve the original document file - Retry, unlock, or permanently delete a check ## Use cases ### AI Agent Credential Verification Let an AI agent screen submitted diplomas for fraud as part of a hiring or admissions workflow: it creates a check on the uploaded document, polls the status until the ML models finish, and retrieves the heatmap that marks suspected tampering. Through Jentic the agent discovers the right EduChecker operation by intent and calls it with the check id, so verification runs without a developer wiring the create-and-poll flow by hand. Example prompt: Create a check for an uploaded diploma, poll its status until complete, then retrieve the fraud-detection heatmap ### Quick Authenticity Screening High-volume reviewers want a fast first pass before committing to a full persisted check. The quick AI check operation screens a diploma image for signs of tampering and returns a result without storing the document. An agent uses it to triage obvious fakes and only escalates borderline cases to a full check. Example prompt: Run a quick AI check on a diploma image to screen for tampering before creating a persisted check ### Institution-Based Verification Some credentials need confirmation directly from the issuing institution rather than ML alone. The API lists the institutions and verification channels available for a country, submits a verification request against the issuing body, and tracks the request to completion. This routes a credential to an authoritative source when document analysis is not enough. Example prompt: List the institutions for a country, submit a verification request against the issuing institution, then poll the request status ### Bulk Check Management Teams processing many credentials manage checks in batches and keep records only as long as needed. The API lists a user's checks, exports data for completed ones, and bulk-deletes checks that are no longer required. An agent uses this to reconcile a backlog and enforce a retention policy. Example prompt: List a user's checks, export the data for completed ones, then bulk-delete the checks that are no longer needed ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/api/checks/` | Create a diploma check | | GET | `/api/checks/{check_id}` | Get a check's status | | GET | `/api/checks/{check_id}/heatmap` | Get a check's tampering heatmap | | POST | `/api/ai/quick` | Run a quick AI authenticity check | | POST | `/api/verification/requests` | Create an institution verification request | | GET | `/api/verification/institutions` | List institutions for verification | | GET | `/api/checks/{check_id}/document` | Get the original document file | | GET | `/api/checks/{check_id}/export` | Export a check's data | ## Key resources - **Checks** — Create ML fraud-detection checks, poll status, retrieve heatmaps and documents, and retry, unlock, export, or delete checks - **Quick AI** — Run a quick authenticity check on a document without persisting it - **Verification requests** — Submit and track institution-based verification requests across countries, institutions, and channels - **Billing** — Manage credits, orders, subscriptions, and payment methods for running checks ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 53 / 100 - Developer Experience & Jentic Compatibility: 61 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 86 / 100 - Security: 60 / 100 - AI Discoverability: 71 / 100 - **View full report:** https://jentic.com/apis/educhecker.io/educhecker/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring EduChecker by hand means handling its bearer-token auth, the create-check-then-poll-status verification flow, and its billing and credit model before a check runs. Through Jentic you install once, import EduChecker from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** EduChecker puts the check id in the URL path (`/api/checks/{check_id}`), so a rule can pin your agent to specific checks and the operations you pick. You choose the operations it may call, so creating checks and reading their status can be allowed while destructive ones like permanently deleting a check or bulk-deleting checks are not included unless you add them. - **Credential handling:** Your EduChecker 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 'verify a diploma' or 'run a fraud check', and Jentic returns the matching EduChecker operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Veriff API** — Identity and document verification across broader ID types - **Persona API** — Configurable identity verification and document checks - **ComplyAdvantage API** — AML and sanctions screening to run alongside credential checks ## FAQ ### What authentication does the EduChecker API use? The EduChecker API authenticates with a bearer token per its OpenAPI spec, obtained by registering and logging in through its auth operations, including Google sign-in. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context. ### Can I detect diploma fraud with the EduChecker API? Yes. The create-check operation runs ML fraud detection on an uploaded diploma, and you poll the check status and retrieve a heatmap that highlights suspected tampering. A quick AI check operation screens a document for authenticity without persisting it. ### What are the rate limits for the EduChecker API? The OpenAPI spec does not specify rate limits; see https://educhecker.io for current limits. Checks are also governed by your credit and subscription balance, which you can read with the credits and usage operations. ### Is there an EduChecker MCP server? You don't need an MCP server to give your agent the EduChecker API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls operations like creating a check or reading its heatmap. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context. ### Can I limit what my agent is allowed to do with the EduChecker API? Yes. Write a rule that allows only creating checks and reading their status and heatmaps, so the agent can submit documents and read results but cannot permanently delete checks or bulk-delete them. Because EduChecker addresses each check by id in the URL path, a rule can also pin the agent to specific checks, and every call is logged. ### How do I verify a diploma with the EduChecker API through Jentic? Search Jentic for 'verify a diploma for fraud' to find the create-check operation, upload the document, poll the check status, then read the fraud-detection heatmap. To run it on your own infrastructure, install Jentic One from its GitHub repo.